#microformats 2019-12-17

2019-12-17 UTC
GWG joined the channel
#
gRegorLove [tantek], I have some time to discuss mf2p this evening
#
[tantek] gRegorLove great! Can you review the brainstormed list of potential labels listed under "Why:" here: https://indieweb.org/Falcon#one-off_tag-of_post and see if they map at all / easily / obviously / not at all to your reading of the mf2 change control process: http://microformats.org/wiki/microformats2-parsing#change_control
jgmac1106 and [jgmac1106] joined the channel
#
gRegorLove Re-opened the PHP 5.6 issue and assigned it to the next milestone https://github.com/microformats/php-mf2/issues/104#issuecomment-566339152
#
Loqi [gRegorLove] Re-opening. WordPress 5.2 now requires PHP 5.6.20 ([announced 2019-04-01](https://wordpress.org/news/2019/04/minimum-php-version-update/)). We're pretty sure this was the only reason we kept PHP 5.4 support for so long, so will probably update minimu...
#
GWG That's a lot of labels
#
[tantek] brainstorming results in lots of ideas
#
gRegorLove That list looks pretty solid. Reviewing the h-entry change control to see if anything else jumps out.
#
gRegorLove For vocab, maybe also add tags to indicate current status: proposed, draft, stable
jgmac1106, gRegorLove, tesst and freeBSD joined the channel
#
[tantek] in reviewing the brainstormed labels, I realize what I did which is to identify pre-conditions, rather than state
#
[tantek] perhaps we need both?
#
[tantek] or is there a way to indicate that an issue needs to satisfy a series of criteria via checkboxes in order to advance?
#
[tantek] though I suppose that would be even harder to decentralize than GitHub's checkboxes in issues feature
#
[tantek] so perhaps better to stick with a set of labels/tags can be added/removed to indicate state / preconditions needing to be satisfied
#
gRegorLove Yeah I'm not sure how checkboxes would work. I haven't been POSSEing github issues yet
#
[tantek] then we avoid checkboxes for now
#
[tantek] updated labels with definitions: https://indieweb.org/Falcon#one-off_tag-of_post
nsbh^, KartikPrabhu, JonathanNeal_, indy_, mblaney, asymptotically, jgmac1106, [jgmac1106], JLynchDiscord[m], [KevinMarks], [LewisCowles], [tantek], [tonz], TallTed, chrisaldrich, [schmarty], [snarfed], gRegorLove, Stef, [manton] and [grantcodes] joined the channel; JellieDiscord[m] and mblaney left the channel
#
gRegorLove [tantek], there's a few "needs..." labels on https://github.com/microformats/microformats2-parsing/labels already but I checked and they haven't been used previously. Want me to update the labels based on your list?
omz13 joined the channel
#
[tantek] I was hoping to discuss "my list" first 🙂
mblaney joined the channel
#
[tantek] I did edit them a bunch (slightly) last night to hopefully improve them
#
[tantek] And it's likely further improvements are possible
#
[tantek] meta goal is for each label to simultaneously capture *both* an aspect of current state, *and* the next thing that is needed on that aspect.
KartikPrabhu and [KevinMarks] joined the channel
#
gRegorLove [tantek], "Needs proposal review
#
gRegorLove : has proposal but needs feedback and positive reviews" I think "has tests" is implied there, should probably add it explicitly though
#
gRegorLove unless I'm reading too much into the ordering of the labels
#
[tantek] yes it's not a strict linearization
#
[tantek] this is what I meant by *aspect of the current state*
#
[tantek] maybe a diagram is needed
#
gRegorLove That might help. Reading through it, it *seems* to cover everything, but I could easily be overlooking things