2013-10-11 UTC
shaners joined the channel
# 00:38 Loqi shaners: bret left you a message on 10/9 at 8:39pm: Let me try to nail down the day I need to work at school this coming weekend, and we can plan an event to hack a bit. I'll let you know via IRC or something
jfranusic and tpinto joined the channel
spinnerin, bnvk, tpinto, lukebrooker, shaners, jernst, acegiak, rknLA, hidgw and caseorganic joined the channel
caseorganic, JasonO, tpinto, acegiak, eschnou, cweiske, LauraJ, julien51, josephboyle, pfefferle, andreypopp, melvster, bnvk, abrereton, friedcell, vrypan and barnabywalters joined the channel
bnvk and scor joined the channel
# 11:53 pfefferle fyi i am currently working on an IndieWeb Verison of Jetpack that shows all IndieWeb plugins for WordPress and how to install them.
# 12:00 pfefferle barnabywalters have you planned to implement some kind of an "complete check"
# 12:06 barnabywalters so it’s easiest to build it piece by piece, see which parts are slow, then hook them together in whatever way seems sensible
# 12:07 pfefferle and it would be way easier to link to, via plugins or browser extensions.
# 12:07 barnabywalters also, not everyone has everything on their index page, so some crawling/autodiscovery would be required
# 12:09 barnabywalters I can speak just enough french to have broken conversations with hurdy gurdy makers, not quite enough to understand blog posts yet :)
# 12:32 pfefferle i want to markup a list of plugins (with github url, wordpress plugin-directory url, description, …) and i am searching for a format. do you think i should prefer something like opml or use something proprietary?
# 12:35 pfefferle i want to provide a list of plugins using github, so people could easyly add their plugins… and this list should be the basis of the indieweb plugin… so the user don't have to update the plugin everytime a new plugin is added...
# 12:36 pfefferle it would be nice to use a simple format to make it easy extensible for other users
# 12:38 barnabywalters then, it allows you to enhance that by automatically installing all the plugins
# 12:40 pfefferle indeed, but than we have to discuss a markup (poshformat) and implement a parser...
# 12:41 barnabywalters the parser’s already built, and the fact that the list already exists gives us plenty of raw material to work with
# 12:42 barnabywalters that’s one of the nice things about mf2 generic parsing — it makes very quick prototyping possible :)
# 12:43 barnabywalters pfefferle: what information do you need to have in order to install the plugins?
# 12:46 barnabywalters but mf2 has built-in listing abilities, and this use case isn’t really an outline
LauraJ joined the channel
friedcell joined the channel
# 13:44 barnabywalters if not, baker is a both testament to his skill and proof that our “document everything” approach works
andreypopp, LauraJ, eschnou, josephboyle and caseorganic joined the channel
benprew, icco, caseorganic, jschweinsberg, npdoty, squeakytoy, jfranusic, jfranusi_, caseorga_, andreypopp, julien51 and spinnerin joined the channel
andreypopp, tpinto, spinnerin, caseorganic, jernst, ShishKabab, bnvk and tantek joined the channel
caseorganic, julien51, eschnou, jfranusic, caseorga_, andreypopp, barnabywalters, josephboyle, poppy, scor, abrereton, npdoty, melvster, poppy1 and npdoty_ joined the channel