#sknebeljust installed a mediawiki and dumped the data in
#aaronpkyeah and that worked surprisingly well. We're going to have to do basically that for the real upgrade, but your mirror is a good test of whether the current content might be tied to plugins or version specific stuff
#gRegorLoveOne thing I look forward to with Vector is sub-headings that are easier to differentiate from the text, haha. I get lost on that admin todo page sometimes.
[tantek], [schmarty] and [eddie] joined the channel
#[tantek]It's pretty important we keep the history
#[tantek]of wiki pages in particular, and users that edited them etc. would be great to figure out which pages remain that were edited before 2007-12 by someone who has not explicitly added the public domain / CC0 decree to their user page
#Loqi[[tantek]] GWG, sknebel, aaronpk, part of the point of the explicit change control in parsing spec, and at least h-entry (more as we get consensus) is to enable adding/promoting/removing properties asynchronously, in such a way that you can cite evidence for ea...
#aaronpkwe're not like a company where people work full time and can schedule quarterly meetings, so in practice, things only happen when someone takes the initiative
#aaronpkthat just so happens to often be at a time when a bunch of us are together in person, since it's easy to have microformats be top of mind in those settings
#aaronpkif you want things to happen in between in-person events, then someone needs to take the initiative of leading that asynchronous discussion and coming to a resolution
[kevinmarks786] and billbennettnz joined the channel
#[tantek]GWG, most of those in-person discussions at IWS re: microformats and resolving issues pre-date the current Change Control processes and thus were more necessary at the time
#[tantek]what's the best way to indicate the "state" of an issue?
#[tantek]I was going to use labels, but that seems hacky (others do it though)