#microformats 2021-05-21

2021-05-21 UTC
digiSal, mauz555, gRegorLove, [tw2113_Slack_], hendursaga, [KevinMarks], [chee], barnabywalters, sparseMatrix, [schmarty], [manton], TallTed, [chrisaldrich], jamietanna, [snarfed], gRegorLove_, [tantek] and aaronpk joined the channel
#
gRegorLove barnabywalters, I think the two change control processes to be familiar with are: https://microformats.org/wiki/h-entry#change_control and https://microformats.org/wiki/microformats2-parsing#change_control linked in there as well.
#
barnabywalters gRegorLove++ thanks! I reviewed the second already, looking over the first now
#
Loqi gRegorLove has 5 karma in this channel over the last year (26 in all channels)
#
gRegorLove Haven't read up yet, but I suspect a lot of that mf2 session was about the former; moving properties from proposed to draft to stable, etc.
#
barnabywalters cool, that all seems pretty straightforward
#
barnabywalters https://microformats.org/wiki/issues seems to be entirely out of date, both in the issues raised there, and the pages it links to
#
barnabywalters might be worth cleaning up and updating with links to current vocab-specific issues and change control policies
#
[tantek] gRegorLove++
#
Loqi gRegorLove has 6 karma in this channel over the last year (27 in all channels)
#
[tantek] yeah we need to do some wiki gardening on /issues
#
barnabywalters (that was the first place I looked when looking for the obvious process documentation)
#
gRegorLove Yeah, I think we've migrated all new issues to github.com/microformats
#
[tantek] tbh we should have a chat about the broader cultural issue as to *why* we lost momentum on /issues
#
barnabywalters so /issues would probably make a good index/jumping off point of all the places where mf issues are stored and discussed
#
[tantek] for a lot of us it was being burned out from troll-fatigue
#
[tantek] and this overlaps with the discussion of updating Wikipedia to be primarily about mf2 rather than classic microformats
#
[tantek] I'd suggest that as a pop-up topic first, that's more important than solving specific technical issues IMO
#
[tantek] this hasn't (yet) happened to the IndieWeb community (fortunately), but partly that's because a few of us (myself included) saw what happened in microformats and vowed to absolutely not allow that to even start happening in IndieWeb
#
barnabywalters [tantek]: I don’t want to pre-empt that, but would you object to me moving the 10yo resolved issues on /issues to /microformats issues resolved, and updating the links on /issues for better discoverability
#
[tantek] I suppose that's more #indieweb-meta so I'll continue that thread there
#
barnabywalters e.g. to the more current mf2 parsing and vocab specific issues, and change control processes
#
[tantek] I would object because the answers (even the first one there about naming) would be very different today!
#
[tantek] so archiving them in that state would serve to miscommunicate the current state of understanding
#
barnabywalters so what needs to be done for the ACCEPTED PROPOSED RESOLUTION to become a proposed resolution?
#
[tantek] I'd be ok with explicitly marking their proposed resolutions as possibly out of date, and worthy of reconsidering or re-opening
#
barnabywalters specifically I’m talking about these two https://microformats.org/wiki/issues#Issues, raised in 2006 and 2010, both of which seem to have been resolved with the advent of mf2?
#
barnabywalters although the second one still applies to the value-class pattern
#
barnabywalters as class="value" is the only remaining non-prefixed classname in use in mf2
#
gRegorLove I took a crack at updated u-photo definition: https://github.com/microformats/h-entry/issues/24
#
Loqi [dshanske] #24 Update the Definition of Draft Property u-photo
#
[tantek] barnabywalters, "ACCEPTED PROPOSED RESOLUTION" doesn't even necessarily make sense in the current process contexts
#
[tantek] to be clear, I'm likely today to have a very different opinion/answer then I had back in the day on those issues
#
barnabywalters [tantek]: agreed, and “accepted proposed” is confusing anyway IMO — is it accepted, or proposed?
#
[tantek] disagreeing with my past welf 🙂
#
[tantek] lol
#
barnabywalters heh I know that feeling all too wel
#
barnabywalters I recently read through a years worth of IRC logs from 2012 to find data for /timeline
#
barnabywalters anyway, from my point of view, almost none of the content on /issues is relevant to current mf2 issues. the two semi?-resolved issues which are there are perhaps interesting from a historical perspective, but have effectively been made redundant by mf2
#
barnabywalters hence my suggestion to move them elsewhere and update /issues to reflect the current state of mf issue tracking and resolution
#
gRegorLove I think putting an archived notice at the top with links to github would be good
#
gRegorLove The mf2 specs should link directly to github, with separate link to previous issues. h-entry has that for example "Resolved issues before 2012-246"
[tw2113_Slack_], [tantek]1, jamietanna and [chrisaldrich] joined the channel
#
[tantek]1 because /issues *needs* a rewrite to keep it from being misleading, I'd rather keep it ugly than pretend it's an ok past thing that's just archived
#
[tantek]1 barnabywalters, plenty of the implied process stuff besides those two issues needs to be rewritten too. The Template stuff, the links to "other" issues pages etc.
#
[tantek]1 it's really a pretty bad mess 😞 (apologies)
#
barnabywalters yeah that’s what I’m suggesting
#
GWG So, lots of possible gardening opportunities
[chrisaldrich] and sparseMatrix joined the channel
#
@sheikharif14_12 ↩️ Why hentry tag is used. And what is microformats (twitter.com/_/status/1395883747157831684)
KartikPrabhu joined the channel