#microformats 2019-12-16

2019-12-16 UTC
KartikPrabhu, gRegorLove, [Rose], [jgmac1106], [tantek], chrisaldrich, [Michael_Beckwit, [fluffy], mattgorecki, [dmitshur], [tonz], [xavierroy], mblaney, asymptotically, vendan, strugee, tsrt^, jacky3, [LewisCowles], [snarfed], jgmac1106, [Sadik_Shahadu] and [benatwork] joined the channel
#
gRegorLove aaronpk, do you have some time this month to review php-mf2 PRs and merge in prep for a new release?
#
aaronpk yeah I should be able to
#
[tantek] are there php-mf2 flagged features that are waiting on mf2 issue resolutions?
jgmac1106 joined the channel
#
gRegorLove I'm not sure what you mean
#
gRegorLove Oh, microformats parsing issues?
#
[tantek] yes mf2 parsing spec issues
#
gRegorLove I don't think so. I'll have to review https://github.com/microformats/microformats2-parsing, haven't looked at it in a while.
#
Loqi [microformats] microformats2-parsing: For collecting and handling issues with the microformats2 parsing specification: http://microformats.org/wiki/microformats2-parsing
#
[tantek] e.g. that have a consensus resolution, but perhaps not (enough?) implementation experience
#
[tantek] I suppose this brings me back to needing labels on mf2 parsing issues to track their state
#
[tantek] which brings me back to https://indieweb.org/Falcon#one-off_tag-of_post
#
[tantek] gRegorLove, any insights, suggestions, that you have regarding how to "more efficiently" or "more collaboratively" or "more asynchronously" process and progress mf2 parsing issues are appreciated!
#
tantek edited /rfc-2445 (+229) "needs update to 5445, note validator" (view diff)
#
tantek edited /rfc-2445 (+133) "/* validator */ about, launched 2015" (view diff)
#
GWG_ gRegorLove: I have a few things on the mf2 list
#
gRegorLove GWG_: okay, can you add them to https://github.com/microformats/php-mf2/issues or let me know if they're existing issues?
#
GWG_ They are existing
#
GWG_ https://github.com/microformats/php-mf2/issues/211
#
Loqi [dshanske] #211 ParsefromID should include the element it is Parsing
#
GWG_ https://github.com/microformats/php-mf2/issues/206
#
Loqi [dshanske] #206 Add optional ID for h-* elements
#
GWG_ https://github.com/microformats/microformats2-parsing/issues/47
#
Loqi [dshanske] #47 Implied h-feed
#
GWG_ https://github.com/microformats/microformats2-parsing/issues/46
#
Loqi [dshanske] #46 URLs with fragments should only have the node identified by the fragment and its descendents parsed
#
GWG_ https://github.com/microformats/php-mf2/issues/133
#
Loqi [gRegorLove] #133 Consider adding a version check method
#
GWG_ Like to discuss this one
#
GWG_ https://github.com/microformats/php-mf2/issues/136
#
Loqi [dshanske] #136 Add Fallback for Systems without the MBString Extension
#
gRegorLove might be able to do 211 and 206. I'd like to get the existing PRs merged and see where we're at
#
GWG_ gRegorLove: I thought we had some of 206, but not a definitive conclusion on fragments
#
GWG_ By the way, if you are keeping PHP5.4 compatibility for WordPress...it moved to minimum 5.6
#
gRegorLove Nice. I'm in favor of bumping to 5.6 if there's no objections.
#
[tantek] GWG, gRegorLove I have some ideas on suggested labels for these issues to keep track of which ones are at what level of consideration
#
[tantek] do you have time to discuss that?
[jgmac1106] joined the channel
#
aaronpk pretty sure the only reason we were keeping 5.4 compat is for wordpress
#
gRegorLove I don't at the moment, but happy to read back tonight/tomorrow
#
[tantek] or should I file a meta issue? (would rather not, as it's not a process change per se, it's more logistics to help implement existing process more smoothly)
#
GWG_ So, with WordPress at minimum 5.6, I would say you are safe to follow
#
GWG_ [tantek]: You have my full attention, other than my dinner
#
gRegorLove chat works for me
[dougbeal] and jgmac1106 joined the channel