#tantekaaronpk, I noticed you tested shpub yourself for the (un)deletes as urlencoded tests - would you consider running the entire test suite on shpub and updating its results accordingly, and applying that ^4 footnote to the entire column?
#tantekaaronpk, impl report request 2: could you hyperlink the vocabs and extensions listed (i.e. in column B)
#tantekalso, IIRC h-event and h-review are both optional and *informative* (non-normative) right?
#tantek(because if they were *normative* optional features, then we would want to drop them for only having 1 confirmed implementation, which I believe we were doing / did for optional AS2 features)
#aaronpki wasn't sure what term to use there, but h-review isn't even mentioned in the spec, it's just something I did as a natural extension
#tantekaaronpk, that makes sense. However upon looking at that section, I'm surprised h-review (as you say not mentioned in the spec) is in the impl report (with only one impl, which is fine for non-normative), but h-card and h-cite are not. Did those not have any impls? Or just an oversight in the impl report?
#tantekI guess I'd expect things mentioned in the spec to show up in the impl report one way or another (i.e. if non-normative optional vocabs/extensions are mentioned in the spec, presumably that means that there was some evidence of their use in the wild to merit mentioning, thus merits mentioning in an impl report)
#tantekaaronpk btw nice work on the wiki page for the PR transition
#tantekaaronpk, since we're still waiting on a fully tested impl report for shpub, and it looks like you tested it at least on a few things yourself (^4), would you be able to run the complete client test suite on shpub and submit that with that same ^4 caveat on the entire result?
#aaronpkyeah, it's informative, not really part of the transition request, i just wanted to see it there
#tantekhowever anything beyond (or outside) the spec could be hyperlinked to its own definitions/spec(s)
#tantek(both the additional vocabs and the extensions)
#ben_thatmustbemeon a note of all the extensions and additional vocabularies, my client (InkStone) can do any of them through user config settings as they can configure all of that
#tantekben_thatmustbeme: that's good to know, but perhaps would be better done with actual posts rather than just config+test for the sake of testing
#tanteke.g. if you posted an h-event or h-review, my guess is that getting the (your?) server to support that may involve more work than some client user config. just a guess.
#tanteklooks like with that updated implementation report we have passed the conditions the group resolved on to take Micropub to PR with (implied 2+) implementations passing the test suite, and in particular client test suite impl reports from editor, shpub, and micropublish
#tantekand I don't know of any other problem reports
#tantekaaronpk: any new github issues filed? just checking
ben_thatmustbeme joined the channel
#tantekassuming no new github issues on Micropub - IMO it looks ready to transition PR per the groups decision.
#tanteksandro, rhiaro, evanpro any further thoughts?
#aaronpki believe we've hit the threshold we resolved at the last meeting
#aaronpk"Request Micropub -> PR when new complete test suite is reported passed by impls from editor, shpub, micropublish, and no one else reports problems"
#tantekdo we have a staged PR draft with the right date and everything?
#aaronpkI guess I can probably safely stage one for tuesday, since we can't publish tomorrow
#aaronpkbut anyway, it's trivial for me to change the date, so just let me know
#tantekif you set it up for tomorrow, then assuming the european team is ready to run with it, they can just do it tomorrow morning when they wake up without any interaction