#social 2017-03-14

2017-03-14 UTC
ben_thatmust, timbl and fabrixxm joined the channel
#
rhiaro
Good evening everyone from sunny* Bali
#
rhiaro
* it would be sunny if it weren't nighttime
#
aaronpk
waves from rainy portland
#
rhiaro
I have sand in my bed and am covered in mosquito bites, but at least it's not snowing
bengo and eprodrom joined the channel
#
wilkie
hello all!
#
wilkie
hello from snowy pittsburgh
julien joined the channel
#
bengo
hi!
#
eprodrom
Wooooow we have a lot to get through today
tantek joined the channel
#
csarven
I can't even hear crickets
#
eprodrom
trackbot, start meeting
#
trackbot
is preparing a teleconference.
RRSAgent joined the channel
#
trackbot
RRSAgent, make logs public
Zakim joined the channel
#
RRSAgent
I have made the request, trackbot
#
aaronpk
present+
#
trackbot
Zakim, this will be SOCL
#
Zakim
ok, trackbot
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 14 March 2017
#
eprodrom
We need a scribe?
#
julien
present+
#
eprodrom
present+
#
csarven
present+
#
tantek
present+
#
tantek
checks logs
#
ben_thatmust
present+
cwebber joined the channel
#
tantek
mutes himself
#
bengo
present+
#
tantek
hears a rapid noise pulse
#
tantek
Zakim, pick a victim
#
Zakim
Not knowing who is chairing or who scribed recently, I propose ben_thatmust
#
ben_thatmust
i scribed last week
#
aaronpk
lol Zakim
#
tantek
Zakim, pick a victim
#
Zakim
Not knowing who is chairing or who scribed recently, I propose csarven
#
ben_thatmustbeme
s/week/meeting
#
ben_thatmustbeme
i'll scribe again if needed
#
cwebber
present+
#
sandro
present+
#
eprodrom
scribenick; csarven
#
eprodrom
scribenick: csarven
#
wilkie
present+
#
csarven
I don't remember commands.. so I just type stuff right?
#
rhiaro
scribe: csarven
#
rhiaro
present+
#
ben_thatmustbeme
csarven correct, just start with personsname: or later lines just start with ... if its a continuation
#
ben_thatmustbeme
only commands you may need past that is TOPIC:<some topic>
#
csarven
eprodrom: First item is review our minutes
#
csarven
eprodrom: Please quickly review
#
eprodrom
+1
#
eprodrom
PROPOSAL: accept https://www.w3.org/wiki/Socialwg/2017-02-28-minutes as minutes for 2017-02-28 telecon
#
eprodrom
+1
#
bengo
+1
#
cwebber
+1
#
tantek
wonders if kevinmarks is now able to make the telcon
#
eprodrom
RESOLVED: accept https://www.w3.org/wiki/Socialwg/2017-02-28-minutes as minutes for 2017-02-28 telecon
#
csarven
eprodrom: First agenda item: discuss monthly call
#
csarven
... possibilities.. March 28 and another on APril 11
#
sandro
+1 biweekly
#
csarven
... uhhmm it feels like we have a lot of stuff..
#
aaronpk
+1 for every two weeks
#
cwebber
+1 on biweekly
#
tantek
+1 for 2017-03-28 and 2017-04-11, to be evaluated at 2017-04-11
#
julien
+1 for biweekly
#
eprodrom
PROPOSED: schedule telecons for 2017-03-28 and 2017-04-11
#
csarven
... if we are okay I'd like to propose schedule telcon for ...
#
julien
+1
#
rhiaro
+1 but not sure if I'll be available on 28th
#
eprodrom
+1
#
tantek
(I'm not sure we're going to be as busy after the next two telcons including this one)
#
csarven
I can't make it
#
tantek
(we can re-evaluate on 2017-04-11 accordingly)
#
csarven
Probably in flight at that time.
#
eprodrom
RESOLVED: schedule telecons for 2017-03-28 and 2017-04-11
#
tantek
csarven both telcons?
#
csarven
ops .. sorry the first .
#
cwebber
I can't make the 28th
#
csarven
+1 to 2017-04-11
#
cwebber
well maybe I can
#
cwebber
but it will be hard
#
cwebber
how about, I will *try to* make the 28th :)
#
tantek
(honestly I'm hoping we make good progress with Websub on the 28th)
#
csarven
eprodrom: If you have strong opinions about the agenda please say ahead of time.
#
csarven
... if you prefer that we continue with the meetings w/o you being there, that's okay too.
#
rhiaro
and rhiaro
#
rhiaro
but I don't object :)
#
csarven
No strong objections. Please go ahead
#
cwebber
no objections
#
tantek
Zakim, who is here?
#
Zakim
Present: aaronpk, julien, eprodrom, csarven, tantek, ben_thatmust, bengo, cwebber, sandro, wilkie, rhiaro
#
Zakim
On IRC I see cwebber, Zakim, RRSAgent, tantek, julien, eprodrom, bengo, timbl, fabrixxm, ben_thatmustbeme, bigbluehat, csarven, rhiaro, sandro, pdurbin, bitbear, dwhly, geppy, jet,
#
Zakim
... Loqi, strugee, wseltzer, aaronpk, raucao, lambadalambda, wilkie, trackbot, KjetilK, mattl
#
tantek
that's a good set of folks for our telcon!
#
tantek
it's getting a bit late to announce an official f2f for April frankly
KevinMarks joined the channel
#
tantek
per W3C rules of advance announcement
#
csarven
sandro: Assumed that we won't do the F2F based on last meeting
#
rhiaro
Maybe we just have a post-WG party in June
#
csarven
eprodrom: How about a new doodle for May?
#
csarven
sandro: :)
#
csarven
sandro: Hopefully by May we are past the point of meetings.. nothing substantive.
#
csarven
eprodrom: Okie dokie
#
tantek
possibly WG->CG transition?
#
csarven
sandro: We could do over the phone
#
csarven
tantek: One thing to use the meeting for that could be productive... the wrap up the stuff and the official kickoff for the CG
#
csarven
tantek: ... here are some stuff for the CG. Get people excited.. INvited folks beyond the WG. thinking out loud
#
csarven
tantek: ... to keep the moment going especially we close the WG
#
csarven
eprodrom: Open to it.. I have two questions.
#
csarven
eprodrom: what do nwe need to make it worthwhile.
#
csarven
eprodrom: can we ge tit for April or May?
#
csarven
tantek: May is logical time to do that.
#
eprodrom
# of people necessary
#
rhiaro
I can make it if it's in Europe between the 18th and 27th of May
#
csarven
tantek: As sandro said.. probably not much/likely to do at that point.
#
csarven
tantek: It'll be good to have an answer to where things can go
#
csarven
tantek: Especially for those that haven't been engaged with the WG
#
csarven
sandro: Can we move this discussion to the CG?
#
csarven
eprodrom: Do we have a wrap-up for us to do?
#
tantek
ok with that
#
csarven
sandro: I don' thtink we need that IRL wrap-up
#
csarven
eprodrom: I love voting
#
tantek
ok with what sandro was saying
#
eprodrom
PROPOSED: No further F2Fs for WG; any future F2Fs under umbrella of CG
#
tantek
+1 I'm swayed by sandro's reasoning
#
bengo
+1
#
csarven
eprodrom: Let's take this off our agenda and move it to CG's
#
cwebber
+1
#
eprodrom
+1
#
KevinMarks
I should be able to make this better, but currently not good broadband for calling in
#
tantek
note to CG co-chairs, you can also plan to ask for f2f time during TPAC
#
eprodrom
RESOLVED: No further F2Fs for WG; any future F2Fs under umbrella of CG
#
csarven
eprodrom: 20mins for admin \o/
#
csarven
eprodrom: Topic LDN
#
KevinMarks
(I'm in sunny Yorkshire)
#
ben_thatmustbeme
scribenick: ben_thatmustbeme
#
tantek
thanks ben_thatmustbeme
#
rhiaro
listed all relevant links on agenda for LDN: https://www.w3.org/wiki/Socialwg/2017-03-14#Topics
#
ben_thatmustbeme
csarven: we're at a point where we only have editorial changes, we have a summary link for all 3 new reports we've collected, there are at least 2+ implmeentations per type of implementation
#
sandro
cwebber, aaronpk, TPAC is near SFO, Nov 6-10
#
eprodrom
Yeah, wow!
#
ben_thatmustbeme
csarven: (reviews stats for inside / outside of WG implementations, scribe missed the exact numbers)
#
Zakim
sees sandro on the speaker queue
#
Zakim
sees sandro, tantek on the speaker queue
#
ben_thatmustbeme
csarven: we have a few more implementation reports in the works
#
ben_thatmustbeme
sandro: looking at the implementation matrix looks great
#
ben_thatmustbeme
... there are 3 tests that do not appear widely implemented, are those optional?
#
ben_thatmustbeme
... PRCU, GLCG, and GNL
#
rhiaro
but yeah they're all optional
#
rhiaro
all MUSTs are all green
#
ben_thatmustbeme
csarven: when its marked as inapplicable, there is no information for it, we are updating as we find out. if its inapplicable, they are not expected to implment that
#
tantek
q+ to ask two questions 1. how can we tell from the test tables which feature columns are optional, and 2. how can we tell from the test tables which implementation rows are editor, wg, outside wg?
#
Zakim
sees sandro, tantek on the speaker queue
#
ben_thatmustbeme
sandro: so that sideways L symbol means this is the kind of implementation that isn't expected to do that, is that correct?
#
tantek
ack sandro
#
Zakim
sees tantek on the speaker queue
#
ben_thatmustbeme
csarven: they may be processing it, but are not giving that information back out
#
ben_thatmustbeme
sandro: not sure i understand
#
rhiaro
Note that using the test suite to send a report sends an LDN, and the report summary is an LDN consumer
#
ben_thatmustbeme
tantek: in general this looks really good, aside from the axis flip which confused me too, is there some way we can indicate which features are optional vs MUST?
#
ben_thatmustbeme
... the second question, is it possible to indicate in the rows which were written by editor(s), inside the WG, and outside the WG
#
ben_thatmustbeme
... i found that really useful to show how much support we have outside the WG
#
ben_thatmustbeme
... it makes LDN look even stronger
#
ben_thatmustbeme
... that way as we take it to PR, etc, it will be benefiticial
#
ben_thatmustbeme
csarven: we can certainly group them, and mention it in the reports themselves
#
ben_thatmustbeme
csarven: regarding the axis flip this is the "correct" way to show the data
#
rhiaro
things we should probably not debate axes right now
#
ben_thatmustbeme
... thats convention
#
ben_thatmustbeme
tantek: to be clear, i wasn't asking for the axis to be flipped, its just different from the way i saw on others
#
ben_thatmustbeme
... your reasoning makes sense
#
eprodrom
q+
#
Zakim
sees tantek, eprodrom on the speaker queue
#
eprodrom
ack tantek
#
Zakim
tantek, you wanted to ask two questions 1. how can we tell from the test tables which feature columns are optional, and 2. how can we tell from the test tables which implementation
#
Zakim
... rows are editor, wg, outside wg?
#
Zakim
sees eprodrom on the speaker queue
#
tantek
ack tantek
#
Zakim
sees eprodrom on the speaker queue
#
ben_thatmustbeme
csarven: for marking optional vs required, we could do that, part of the test was to catch the most common things people are doing. as there are no fails right now. I could mark the things that are optional on the columns possibly
#
Zakim
sees eprodrom, rhiaro on the speaker queue
#
ben_thatmustbeme
tantek: that would be great
#
ben_thatmustbeme
csarven: minor note, the reports are submitted as an LDN, when the reports are created, its sent to the summary as an LDN,
#
tantek
clever :)
#
ben_thatmustbeme
csarven: so the summary itself is a conforming LDN
#
ben_thatmustbeme
... and there is rdfa on these too which, maybe someone will use in the future
#
ben_thatmustbeme
... i think that we are fairly stable with the reports and the spec
#
Zakim
sees eprodrom, rhiaro on the speaker queue
#
eprodrom
ack eprodrom
#
Zakim
sees rhiaro on the speaker queue
#
ben_thatmustbeme
eprodrom: i have a question, about activitypub and LDN. one of the goals of having LDN in this group was to have the distribution mechanism for AP. I don't know that any of these are also AP implementations. I'm sort of concerned about going to PR without having an AP implementation using it. I know thats unfortunate coupling, but i wanted to ask cwebber about that
#
rhiaro
I believe bengo's is AP or nearly AP too
#
tantek
I for one don't want to block LDN PR on asking for more AP implementation
#
ben_thatmustbeme
cwebber: i'm pretty sure that rhiaro was able to make her implementation use them. I could probably make my implementation do that. We specify it in the spec of how they are similar, but we don't demonstrate that outside of amy's impl.
#
ben_thatmustbeme
eprodrom: certainly .....
#
csarven
bengo's is AP as well
#
bengo
true story
#
ben_thatmustbeme
rhiaro: my implementation is AP and LDN compatible, its slightly broken currently, and i think bendo is using both as well
#
ben_thatmustbeme
s/bendo/bengo/
#
tantek
The strong interop documented by the tables demonstrates there's sufficient critical mass / implementation testing of the spec IMO
#
eprodrom
ack eprodrom
#
Zakim
sees rhiaro on the speaker queue
#
tantek
ack rhiaro
#
Zakim
sees no one on the speaker queue
#
eprodrom
ack rhiaro
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
eprodrom: if thats the case then i feel comfortable, then i want to go forward with it, but go forward with eyes open that we have light implementation of the two of them together. But i think it will be benefitial to AP to have a distribution mechanism at PR
#
Zakim
sees csarven on the speaker queue
#
sandro
rhiaro: Anything that's in gray is because it's an optional feature. Failed mandatory would be red.
#
sandro
excellent
#
ben_thatmustbeme
rhiaro: i just wanted to discuss required vs optional. There would be red boxes if there were any failed required results. the grey boxes are failed by optional
#
ben_thatmustbeme
tantek: thats not the exact meaning i've seen in other groups.
#
ben_thatmustbeme
rhiaro: they are MUST IF's so each of those
#
csarven
to talk about EARL outcome values
#
ben_thatmustbeme
tantek: if i were looking at this naively, which i somewhat am, i would assume that inapplicable means that those don't apply to those classes of implementations, not optional
#
sandro
Just move all those columns to the right hand side, under a super-heading "OPTIONAL"
#
ben_thatmustbeme
csarven: we borrowed the test outcomes from the w3c's EARL, which used those values
#
tantek
I don't doubt that the db schema behind this has been reasoned out, I'm talking purely about the presentation
#
tantek
If it was enough to confuse me and sandro, then it will likely confuse various AC reps ;)
#
Zakim
sees csarven, sandro on the speaker queue
#
ben_thatmustbeme
... the outher thing is that the reports that made it through are the ones that are passing. I know that many of them did have failing during some of these, but they submitted the reports once they were cleared up
#
rhiaro
q+ to see if we add MUST, SHOULD, MAY to the top of the columns that would make it obvious?
#
Zakim
sees csarven, sandro, rhiaro on the speaker queue
#
ben_thatmustbeme
tantek: there is no question of that, this is about presentation, we trust what you did, but its about making it more presentable to those outside the group
#
tantek
rhiaro, yes, and I for one trust you and csarven to figure out such details
#
ben_thatmustbeme
csarven: we'll clear it up
#
tantek
thank you csarven
#
Zakim
sees csarven, sandro on the speaker queue
#
Zakim
sees csarven on the speaker queue
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
eprodrom: i want to make sure that given that you have limited time, we get any process stuff done
#
ben_thatmustbeme
... okay i just cleared the queue, good for me :)
#
Zakim
sees rhiaro on the speaker queue
#
ben_thatmustbeme
rhiaro: before we go to PR, we'd like to publish an updated CR with editorial changes
#
ben_thatmustbeme
tantek: we don't need to do an updated CR for changes that are clearly editorial
#
tantek
I for one am +1 on taking to PR pending editorial edits and presentational update to the implementation report
#
eprodrom
PROPOSED: request transition of LDN to PR
#
ben_thatmustbeme
eprodrom: okay, if we don't need to do that then i'm going to make the proposal for transition without qualification ...
#
tantek
+1 with editorial edits as requested by editors and presentational update to the implementation report to clarify MUST vs optional features, and clustering of implementations as editor, wg, outside wg.
#
ben_thatmustbeme
sandro: i'm looking at the closed issues, and I am seeing a number that are still 'waiting for commentor' and i want to make sure that those are changed to 'timeout' and we have made a good effort to contact them
#
eprodrom
PROPOSED: request transition of LDN to PR with editorial updates
#
ben_thatmustbeme
... oh the latest one is sept 2nd, so we can definitely count those as timeout
#
cwebber
+1
#
tantek
+1 with presentational update to the implementation report to clarify MUST vs optional features, and clustering of implementations as editor, wg, outside wg.
#
bengo
+1
#
eprodrom
+1
#
ben_thatmustbeme
sandro: those changes being the acknowledgement sections
#
ben_thatmustbeme
eprodrom: correct
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
ben_thatmustbeme
eprodrom: if you have a -1 to throw in, do it now
#
eprodrom
RESOLVED: request transition of LDN to PR with editorial updates
#
ben_thatmustbeme
... or say you need more time
#
sandro
congratulations, csarven and rhiaro !
#
csarven
puts his party shoes on
#
tantek
congrats csarven and rhiaro!
#
sandro
indeed!
#
aaronpk
we need a soundtrack when things like this are approved
#
tantek
also thanks sandro for requesting clarifications on waiting for commenter issues
#
rhiaro
..can I sleep now? Like for a year?
#
csarven
Thanks all!
#
ben_thatmustbeme
eprodrom: thank you sarven for hanging on some extra time
#
ben_thatmustbeme
... any extra discussion around LDN before we move on?
#
csarven
Still around.. just with added 3 year old background-stuff
#
ben_thatmustbeme
eprodrom: anything else we wanted to cover?
#
ben_thatmustbeme
sandro: i think we are good
#
ben_thatmustbeme
TOPIC: micropub
#
ben_thatmustbeme
eprodrom: we need to get some updates about the test suite
#
ben_thatmustbeme
tantek: last week we screwed up a little bit, we did not verify that we had complete client tests before we took it to PR
#
ben_thatmustbeme
... despite the vote for going to PR, we didn't meet our standards for PR
#
ben_thatmustbeme
aaronpk: since last call i worked really hard on adding client tests and now there are complete tests for client features on the site. and as you go through client tests on the site, it checks off the pieces in the report for you and gives you the text to insert into your report. this allows people to still submit manually if they want and the format didn't need to change at all
#
tantek
basically, do we now meet our standards for PR for micropub? and if so, we should re PROPOSED and re RESOLVED accordingly
#
ben_thatmustbeme
... i have seen people using it, but no one has submitted a report using the tests yet as most submitted them by hand before that
#
ben_thatmustbeme
sandro: have you been in contact with people to get a clue as to when they might do that?
#
ben_thatmustbeme
aaronpk: i have talked to a couple people but i havent' heard back yet on when
#
Zakim
sees rhiaro on the speaker queue
#
tantek
I think that was from before?
#
tantek
ack rhiaro
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
eprodrom: i guess i'm a little bit confused on where we are, we voted to go to PR, there was some concern about client tests, what actionable for the group now?
#
ben_thatmustbeme
eprodrom: do we need to reel back in our proposal?
#
ben_thatmustbeme
tantek: we did reel it back last week, since then we have fixed the missing implementation reports, i think what sandro was asking is do we have new reports since launching the client tests.
dmitriz joined the channel
#
ben_thatmustbeme
aaronpk: we have not, mine did not change with the new tests, so the report is still the same
#
ben_thatmustbeme
tantek: so have we heard of any changed reports since?
#
ben_thatmustbeme
sandro: looks like shpub and micropublish are the two most complete besides yours, if we reached out to them and asked, that would be a good confirmation to me
#
ben_thatmustbeme
tantek: we could go with a proposal conditional that their clients return the same results with the test, that way we can move on automatically, if not then we have to reaccess it
#
ben_thatmustbeme
... thoughts?
#
ben_thatmustbeme
eprodrom: i feel like if we are going to be meeting again in a few weeks, then the 28th would be a good time to go to PR
#
ben_thatmustbeme
tantek: ideally it should be simply a matter of a few days, not two weeks
#
eprodrom
PROPOSED: requesting advancement of Micropub to PR conditioned on ...
#
ben_thatmustbeme
eprodrom: it sounds like we have something along the (typing out proposal)
#
eprodrom
PROPOSED: requesting advancement of Micropub to PR conditioned on confirmation of client implementations
#
ben_thatmustbeme
sandro: i'm trying to figure out where the bar is here
#
ben_thatmustbeme
... the strictest would be throw out all the ..
#
ben_thatmustbeme
<ben_thatmustbeme> -1!
#
ben_thatmustbeme
sandro: i'm trying to figure out where else is rational to set the bar at
#
ben_thatmustbeme
tantek: it seems reasonable to me
#
ben_thatmustbeme
sandro: if you pitch it to them that it fills out everything for them
#
tantek
+1 with sandro's details of how to confirm client implementations
#
eprodrom
PROPOSED: requesting advancement of Micropub to PR conditioned on confirmation of client implementations
#
ben_thatmustbeme
ben_thatmustbeme: so are we throwing out all the implementation reports?
#
ben_thatmustbeme
sandro: i think we are going with just shpub and micropublish in addition to aaronpk's implementation, and if there are any other issues with the test suite
KevinMarks2 joined the channel
#
ben_thatmustbeme
... i picked those two because they cover most of it
fabrixxm joined the channel
#
ben_thatmustbeme
tantek: yes, i think those are good canaries
#
sandro
PROPOSED: Request Micropub -> PR when new complete test suite is reported passed by impls from editor, shpub, micropublish, and no one else reports problems
#
cwebber
+1
#
eprodrom
+1
#
sandro
(and reasonable effort is made to contact them)
#
ben_thatmustbeme
<ben_thatmustbeme> +1
#
ben_thatmustbeme
sandro: can we extend the meeting a bit?
#
rhiaro
is at 00:00
#
cwebber
I can give a 2 minute AP update
#
tantek
+1 ok with extending meeting 30 min (not expecting it to take that long)
#
ben_thatmustbeme
eprodrom: we have a lot to cover still
#
eprodrom
RESOLVED: Request Micropub -> PR when new complete test suite is reported passed by impls from editor, shpub, micropublish, and no one else reports problems
#
cwebber
I could do a meeting next week
#
tantek
congrats aaronpk on getting (re)resolved to take Micropub to PR!
#
cwebber
no objections
#
julien
For websub, I sent an email earlier today which we can maybe use as a basis for discussion over email? and I am ok to continue either way
#
eprodrom
15 minutes extension
#
julien
+1
#
sandro
eprodrom: meeting extended 15 min
#
ben_thatmustbeme
eprodrom: if there are no objections, i am going to unilaterally extend by 15 minutes
#
tantek
chair: tantek
#
ben_thatmustbeme
tantek: we resolved to take AS2 to PR 2 weeks ago, that was pending a draft update that would remove the set up features we did not have implmntations on, but they are all marked optional at risk
#
ben_thatmustbeme
eprodrom: that updated draft is not ready but i should have something by the end of the week
#
ben_thatmustbeme
... the normative change was to remove those at-risk features that were lacking implementations.
#
ben_thatmustbeme
.. the editorial was remove the 'at-risk' labels, and archive exit criteria and changelog
#
ben_thatmustbeme
... so next steps?
#
ben_thatmustbeme
tantek: we already resolved that, so we just need it to be updated, and that will get it to transition and published by next week
#
ben_thatmustbeme
sandro: it depends on a couple people, if you get it to me by thursday, we should be able to publish by tuesday
#
ben_thatmustbeme
tantek: if we get all our ducks in a row too, we could probably do LDN too
#
ben_thatmustbeme
tantek: so we are aiming for tuesday for all 3 of these PRs
#
ben_thatmustbeme
sandro: optimistically
#
rhiaro
the race is on
#
ben_thatmustbeme
tantek: and we are not going to be holding any up, get your work done or you miss the tuesday train
#
ben_thatmustbeme
tantek: i'm assuming we haven't seen any new AS2 issues come up
#
ben_thatmustbeme
eprodrom: yes, only editorial
#
tantek
chair: eprodrom
#
ben_thatmustbeme
tantek: its not a huge deal if one misses it, but it would be nice to get all our PRs together
#
cwebber
AP will be very short
#
ben_thatmustbeme
eprodrom: websub looks long, i wonder if we can postpone until next meeting?
#
julien
+1 (but read the mail I sent earlier today)
#
cwebber
that's fine
#
ben_thatmustbeme
TOPIC: activitypub
#
tantek
link to that email?
#
julien
+1 sandro!
#
ben_thatmustbeme
sandro: there was an email this morning that people should read and respond to
#
tantek
we really should put WebSub first (non-admin) then for the 2017-03-28
#
julien
looking forzward to see responses ;)
#
tantek
julien hoping you can make it on 2017-03-28!
#
ben_thatmustbeme
cwebber: in short, i did merge bengo's implementation report template, i went through it an everything looks good, there is one small unresolved thing at the bottom i need to take care of. I hoped to tget the test suite by this call, but It has not happened. I have been working on it, but it is very complex and i have been a bit burned out. We have an implementation report but i should probably advertise that a bit better
#
ben_thatmustbeme
tantek: can i get a quick few minutes on the CG issue
#
sandro
I also think it's dead
#
ben_thatmustbeme
tantek: i noticed that there was some spam coming in from W3C Social Business Community Group, it looks to be dead
#
ben_thatmustbeme
can we request w3c close it and direct people to the new CG
#
ben_thatmustbeme
eprodrom: sounds good, can you phrase it as a proposal?
#
tantek
PROPOSED: request that W3C Social Business Community Group be closed with a message inviting anyone there to join the W3C Social Web Community Group
#
eprodrom
+1
#
cwebber
+1
#
ben_thatmustbeme
<ben_thatmustbeme> there are tons of dead CGs so the more dead ones closed, the better
#
ben_thatmustbeme
sandro: i'll try to reach out to the chair too, but it sure looks like the group is dead
#
eprodrom
RESOLVED: request that W3C Social Business Community Group be closed with a message inviting anyone there to join the W3C Social Web Community Group
#
ben_thatmustbeme
tantek: and make it clear that if they do have stuff to work on they can do that in the social web CG
#
julien
Thanks!
#
eprodrom
trackbot, end meeting
#
trackbot
is ending a teleconference.
#
Zakim
As of this point the attendees have been aaronpk, julien, eprodrom, csarven, tantek, ben_thatmust, bengo, cwebber, sandro, wilkie, rhiaro, +
#
trackbot
Zakim, list attendees
#
trackbot
RRSAgent, please draft minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2017/03/14-social-minutes.html trackbot
#
trackbot
RRSAgent, bye
#
RRSAgent
I see no action items
#
wilkie
thanks all!
#
wilkie
csarven++
#
Loqi
csarven has 14 karma in this channel (29 overall)
#
wilkie
ben_thatmustbeme++
#
Loqi
ben_thatmustbeme has 64 karma in this channel (187 overall)
#
tantek
great progress today everyone! thank you all!
#
tantek
csarven++ for minuting
#
Loqi
csarven has 15 karma in this channel (30 overall)
#
tantek
ben_thatmustbeme++ for minuting
#
Loqi
slow down!
#
csarven
take it easy
#
csarven
Wait. how did I get up to 15 karma?
#
sandro
tantek, can your send me a copy of the email you got about socbizcg?
#
tantek
sandro looks like I got two
#
sandro
It actually IS CLOSED, you just cant tell.
#
tantek
looks for Archived-At: headers
#
sandro
Looks like a systems problem.
#
tantek
those are the two
#
rhiaro
We remove CR exit criteria for PR, right? Anything else?
#
csarven
All, do we only remove the "Exit Criteria" section (from current) for the PR version?
#
rhiaro
Do we keep the securiyt and privacy questionnaire?
#
csarven
^^ those two are not at all discussing elsewhere
#
csarven
+1 coordination
#
tantek
rhiaro: yes absolutely re: s & p
#
tantek
s & p are not for transitioning but for everyone who reads and implements a spec!
#
tantek
re: CR exit criteria - there's no consistency AFAIK
#
rhiaro
okay, I vaguely recalled something about it being removed but that's fine
#
tantek
e.g. Annotations moved their CR exit criteria to an Appendix
#
tantek
rhiaro: yes, some groups / drafts remove / drop CR exit criteria when going to PR
#
tantek
just noting what I've seen (which is inconsistency)
#
csarven
I do'nt mind keeping it. Good to show how the implementations were considered
#
rhiaro
What did Webmention do, aaronpk? We can at least be consistent within the group
#
tantek
so it's editorial and up to editors IMO
#
tantek
rhiaro: you should do editorial per what you think is right, not just out of group consistency
#
tantek
i.e. consistency may just be with an accident
#
tantek
not intention
#
tantek
and I lean towards csarven's reasoning
#
csarven
rhiaro: We can just rephrase the first sentence in EC
#
tantek
but that's just my opinion. not bearing on what you should / should not do.
#
aaronpk
the Micropub PR I staged changed the sentence to "This specification exited CR by there being..."
#
tantek
also a reasonable approach
#
aaronpk
but i think we removed the whole section from webmention
#
tantek
I'd rather see evolution / improvement than just consistency
KevinMarks joined the channel
#
tantek
wow that's fast
#
tantek
sees if there's anything to edit
#
tantek
fixes typo
#
tantek
typos*
#
tantek
ends up editing a lot of typos
#
tantek
done. +1 on those minutes from me.
#
tantek
ok, now to create stub pages for the next two telcons
#
tantek
PSA: Happy Gregorian Pi day everyone!
#
tantek
and next telcon, Europe will also be in DST
#
tantek
telcon pages are up for the next two telcons
#
tantek
and home page is updated too
jasnell joined the channel
#
tantek
hah! I just got removed from the Social Business Community Group by W3C Systems Team
#
tantek
I'm hoping that means *everyone* got removed since it's closed?
#
tantek
"you don't like getting spam? fine, you're kicked out ;) "
jasnell joined the channel
#
Loqi
Ok, I'll tell them that when I see them next
#
Zakim
excuses himself; his presence no longer seems to be needed
#
Loqi
good riddance
#
aaronpk
be nice Loqi
KevinMarks joined the channel
jasnell, KevinMarks, timbl, strugee and KevinMarks2 joined the channel