#social 2017-03-22

2017-03-22 UTC
timbl and tantek joined the channel
#
@t
#100DoPP d61: The @SocialWebWG published LDN PR today: https://www.w3.org/TR/2017/PR-ldn-20170321/ + two more PRs from the WG coming soon! (ttk.me t4nS3)
(twitter.com/_/status/844435796182663168)
ben_thatmust, ben_thatmustbeme and timbl joined the channel
ben_thatmustbeme and tantek joined the channel
#
tantek
good morning #social
#
sandro
#social waves good .... afternoon
#
tantek
is looking at the updated https://micropub.net/implementation-reports/clients/ thanks to sandro
#
tantek
aaronpk, 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?
#
tantek
aaronpk, impl report request 2: could you hyperlink the vocabs and extensions listed (i.e. in column B)
#
tantek
column B )
#
tantek
also, 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)
#
aaronpk
i 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
#
aaronpk
h-entry is the only required one
#
tantek
how about h-event? is it normative optional or non-normative?
#
aaronpk
h-event is listed in "informative references" because it is referenced here https://www.w3.org/TR/micropub/#vocabulary
#
tantek
looks
#
tantek
aaronpk, 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?
#
tantek
I 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)
#
aaronpk
none of the clients reported that they create h-card posts
#
tantek
got it
#
tantek
same with h-adr then?
#
aaronpk
correct
#
aaronpk
some of them use h-card and h-adr as values of properties of an h-entry, but that's different
#
tantek
if multiple impls do that, that may be worth documenting
#
tantek
(not required, just a suggestion)
#
aaronpk
yes, but it doesn't seem very relevant to the transition request
#
tantek
right
#
tantek
can be done async with that
#
tantek
aaronpk btw nice work on the wiki page for the PR transition
#
tantek
aaronpk, 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?
#
aaronpk
yeah, i'm doing that now
#
tantek
ok cool
#
tantek
Assuming it passes, that should resolve the (1) Impls for "uses multipart only as a fallback" at least
timbl joined the channel
#
tantek
Since the vocabularies beyond h-entry are all non-normative, perhaps they deserve their own heading
#
aaronpk
that seems reasnoable
#
tantek
like "Additionally Implemented Vocabularies"
#
tantek
since you're including them when implementers report them
#
tantek
that better reflects the reason why they are in the report at all
#
tantek
And then I think "extensions" being beyond the spec is implicit by the name
#
tantek
so that's ok as is
#
aaronpk
yeah, it's informative, not really part of the transition request, i just wanted to see it there
#
tantek
however anything beyond (or outside) the spec could be hyperlinked to its own definitions/spec(s)
#
tantek
(both the additional vocabs and the extensions)
#
ben_thatmustbeme
on 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
#
tantek
ben_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
#
tantek
e.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.
#
ben_thatmustbeme
it would definitely involve that
#
aaronpk
my server supports h-review and h-event, i could try that
#
ben_thatmustbeme
the mp-slug i could probably easily convert to, i use just 'slug' right now, realistically it should be mp-slug
ben_thatmust joined the channel
#
aaronpk
alright, I just finished manually reviewing shpub!
#
tantek
this looks much better
#
tantek
hmm what happened to our /topic
#
aaronpk
irc server restarted
#
tantek
checks last week's minutes
#
tantek
notices rhiaro only added the fragid for one resolution :P
#
aaronpk
I add them when I need them
#
tantek
just added the rest of them that are all linked from the bottom
#
tantek
yup that worked
#
tantek
looks 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
#
tantek
and I don't know of any other problem reports
#
tantek
aaronpk: any new github issues filed? just checking
ben_thatmustbeme joined the channel
#
tantek
assuming no new github issues on Micropub - IMO it looks ready to transition PR per the groups decision.
#
tantek
sandro, rhiaro, evanpro any further thoughts?
#
aaronpk
no new issues on micropub
#
aaronpk
i 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"
#
tantek
do we have a staged PR draft with the right date and everything?
#
aaronpk
I guess I can probably safely stage one for tuesday, since we can't publish tomorrow
#
aaronpk
k it's ready
#
tantek
why not today?
#
aaronpk
publication dates are tuesdays and thursday
#
tantek
I had the feeling Sandro was all ready to try to take all three to PR as of yesterday
#
tantek
why can't we publish tomorrow then?
#
aaronpk
i think the cutoff is the day before
#
aaronpk
but the team is in europe, so it's already past the end of the day on wednesday
#
tantek
I'm guessing sandro may have already preflighted this?
#
aaronpk
i was not making that assumption
#
tantek
is often an optimist :P
#
aaronpk
also it's 4pm in boston now
#
aaronpk
but anyway, it's trivial for me to change the date, so just let me know
#
tantek
if 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
#
aaronpk
heh might as well
#
tantek
better to plan for not having to do something in the shorter timeframe option
#
tantek
because in the longer timeframe option, you have more time to make a change
#
tantek
generally a good philosophy about defaults
#
aaronpk
added a link on the PR page, so hopefully sandro will see it there
#
aaronpk
since he gets a 3 hour head start on me in the morning
csarven and rhiaro joined the channel
#
tantek
sandro, rhiaro - can you confirm/(or not) that Micropub has satisfied the conditions for PR?
timbl, ben_thatmust and ben_thatmustbeme joined the channel