15:01:32 RRSAgent has joined #social 15:01:32 logging to http://www.w3.org/2017/03/14-social-irc 15:01:34 RRSAgent, make logs public 15:01:34 Zakim has joined #social 15:01:36 present+ 15:01:36 Zakim, this will be SOCL 15:01:36 ok, trackbot 15:01:37 Meeting: Social Web Working Group Teleconference 15:01:37 Date: 14 March 2017 15:02:01 We need a scribe? 15:02:13 present+ 15:02:14 present+ 15:02:16 present+ 15:02:18 present+ 15:02:25 present+ 15:02:33 cwebber has joined #social 15:02:37 present+ 15:03:14 last week's minutes btw: https://www.w3.org/wiki/Socialwg/2017-02-28-minutes 15:03:19 Zakim, pick a victim 15:03:20 Not knowing who is chairing or who scribed recently, I propose ben_thatmust 15:03:30 i scribed last week 15:03:37 lol Zakim 15:03:39 Zakim, pick a victim 15:03:39 Not knowing who is chairing or who scribed recently, I propose csarven 15:03:40 s/week/meeting 15:03:55 i'll scribe again if needed 15:04:08 present+ 15:04:22 present+ 15:04:27 scribenick; csarven 15:04:35 scribenick: csarven 15:04:40 present+ 15:04:40 I don't remember commands.. so I just type stuff right? 15:04:44 scribe: csarven 15:05:04 present+ 15:06:34 eprodrom: First item is review our minutes 15:06:36 https://www.w3.org/wiki/Socialwg/2017-02-28-minutes 15:06:49 eprodrom: Please quickly review 15:06:50 +1 15:07:06 PROPOSAL: accept https://www.w3.org/wiki/Socialwg/2017-02-28-minutes as minutes for 2017-02-28 telecon 15:07:08 +1 15:07:17 +1 15:07:21 +1 15:07:27 +1 15:07:28 +1 15:07:41 +1 15:07:47 +1 15:07:51 +1 15:07:59 RESOLVED: accept https://www.w3.org/wiki/Socialwg/2017-02-28-minutes as minutes for 2017-02-28 telecon 15:08:29 eprodrom: First agenda item: discuss monthly call 15:08:36 ... possibilities.. March 28 and another on APril 11 15:08:47 +1 biweekly 15:08:47 ... uhhmm it feels like we have a lot of stuff.. 15:08:48 +1 for every two weeks 15:08:55 +1 on biweekly 15:09:15 +1 for 2017-03-28 and 2017-04-11, to be evaluated at 2017-04-11 15:09:20 +1 for biweekly 15:09:25 PROPOSED: schedule telecons for 2017-03-28 and 2017-04-11 15:09:28 ... if we are okay I'd like to propose schedule telcon for ... 15:09:30 +1 15:09:32 +1 15:09:34 +1 15:09:36 +1 15:09:36 +1 but not sure if I'll be available on 28th 15:09:39 +1 15:09:40 +1 15:09:45 (I'm not sure we're going to be as busy after the next two telcons including this one) 15:09:46 I can't make it 15:09:59 (we can re-evaluate on 2017-04-11 accordingly) 15:10:06 Probably in flight at that time. 15:10:08 0 15:10:11 RESOLVED: schedule telecons for 2017-03-28 and 2017-04-11 15:10:17 csarven both telcons? 15:10:23 ops .. sorry the first . 15:10:25 I can't make the 28th 15:10:38 +1 to 2017-04-11 15:10:39 well maybe I can 15:10:41 but it will be hard 15:11:04 how about, I will *try to* make the 28th :) 15:11:16 (honestly I'm hoping we make good progress with Websub on the 28th) 15:11:16 eprodrom: If you have strong opinions about the agenda please say ahead of time. 15:11:48 ... if you prefer that we continue with the meetings w/o you being there, that's okay too. 15:11:51 and rhiaro 15:11:56 but I don't object :) 15:11:57 No strong objections. Please go ahead 15:11:58 no objections 15:12:07 Zakim, who is here? 15:12:07 Present: aaronpk, julien, eprodrom, csarven, tantek, ben_thatmust, bengo, cwebber, sandro, wilkie, rhiaro 15:12:10 On IRC I see cwebber, Zakim, RRSAgent, tantek, julien, eprodrom, bengo, timbl, fabrixxm, ben_thatmustbeme, bigbluehat, csarven, rhiaro, sandro, pdurbin, bitbear, dwhly, geppy, jet, 15:12:10 ... Loqi, strugee, wseltzer, aaronpk, raucao, lambadalambda, wilkie, trackbot, KjetilK, mattl 15:12:15 fabrixxm has left #social 15:13:11 KevinMarks has joined #social 15:13:16 http://doodle.com/poll/fuqbfsg5kr96pxsy 15:13:17 sandro: Assumed that we won't do the F2F based on last meeting 15:13:38 Maybe we just have a post-WG party in June 15:13:48 eprodrom: How about a new doodle for May? 15:13:53 sandro: :) 15:14:04 sandro: Hopefully by May we are past the point of meetings.. nothing substantive. 15:14:11 eprodrom: Okie dokie 15:14:27 possibly WG->CG transition? 15:14:51 sandro: We could do over the phone 15:15:16 tantek: One thing to use the meeting for that could be productive... the wrap up the stuff and the official kickoff for the CG 15:15:36 tantek: ... here are some stuff for the CG. Get people excited.. INvited folks beyond the WG. thinking out loud 15:15:49 tantek: ... to keep the moment going especially we close the WG 15:15:53 eprodrom: Open to it.. I have two questions. 15:16:00 eprodrom: what do nwe need to make it worthwhile. 15:16:06 eprodrom: can we ge tit for April or May? 15:16:14 tantek: May is logical time to do that. 15:16:15 # of people necessary 15:16:24 I can make it if it's in Europe between the 18th and 27th of May 15:16:31 tantek: As sandro said.. probably not much/likely to do at that point. 15:16:43 tantek: It'll be good to have an answer to where things can go 15:17:03 tantek: Especially for those that haven't been engaged with the WG 15:17:15 sandro: Can we move this discussion to the CG? 15:17:20 eprodrom: Do we have a wrap-up for us to do? 15:17:31 ok with that 15:17:33 sandro: I don' thtink we need that IRL wrap-up 15:17:36 eprodrom: I love voting 15:17:40 ok with what sandro was saying 15:18:00 PROPOSED: No further F2Fs for WG; any future F2Fs under umbrella of CG 15:18:08 +1 15:18:12 +1 I'm swayed by sandro's reasoning 15:18:14 +1 15:18:18 eprodrom: Let's take this off our agenda and move it to CG's 15:18:21 +1 15:18:25 +1 15:18:26 +1 15:18:26 +1 15:18:30 +1 15:18:31 +1 15:18:48 I should be able to make this better, but currently not good broadband for calling in 15:18:49 note to CG co-chairs, you can also plan to ask for f2f time during TPAC 15:18:57 RESOLVED: No further F2Fs for WG; any future F2Fs under umbrella of CG 15:19:11 yea 15:19:22 eprodrom: 20mins for admin \o/ 15:19:30 eprodrom: Topic LDN 15:19:32 (I'm in sunny Yorkshire) 15:19:40 scribenick: ben_thatmustbeme 15:19:47 thanks ben_thatmustbeme 15:20:03 https://linkedresearch.org/ldn/tests/summary 15:20:05 listed all relevant links on agenda for LDN: https://www.w3.org/wiki/Socialwg/2017-03-14#Topics 15:20:46 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 15:21:02 cwebber, aaronpk, TPAC is near SFO, Nov 6-10 15:21:14 https://linkedresearch.org/ldn/tests/summary looks really good! 15:21:27 Yeah, wow! 15:21:36 csarven: (reviews stats for inside / outside of WG implementations, scribe missed the exact numbers) 15:21:45 q+ 15:21:59 q+ 15:22:02 csarven: we have a few more implementation reports in the works 15:22:18 sandro: looking at the implementation matrix looks great 15:22:38 ... there are 3 tests that do not appear widely implemented, are those optional? 15:23:00 ... PRCU, GLCG, and GNL 15:23:26 but yeah they're all optional 15:23:31 all MUSTs are all green 15:23:50 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 15:24:29 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? 15:24:34 sandro: so that sideways L symbol means this is the kind of implementation that isn't expected to do that, is that correct? 15:24:35 ack sandro 15:24:56 csarven: they may be processing it, but are not giving that information back out 15:25:00 sandro: not sure i understand 15:25:05 Note that using the test suite to send a report sends an LDN, and the report summary is an LDN consumer 15:25:34 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? 15:26:11 ... the second question, is it possible to indicate in the rows which were written by editor(s), inside the WG, and outside the WG 15:26:28 ... i found that really useful to show how much support we have outside the WG 15:26:36 ... it makes LDN look even stronger 15:27:08 ... that way as we take it to PR, etc, it will be benefiticial 15:27:25 csarven: we can certainly group them, and mention it in the reports themselves 15:27:48 csarven: regarding the axis flip this is the "correct" way to show the data 15:27:55 ... thats convention 15:28:19 tantek: to be clear, i wasn't asking for the axis to be flipped, its just different from the way i saw on others 15:28:26 ... your reasoning makes sense 15:28:29 q+ 15:28:34 ack tantek 15:28:34 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 15:28:37 ... rows are editor, wg, outside wg? 15:28:50 ack tantek 15:29:35 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 15:29:40 q+ 15:29:41 tantek: that would be great 15:30:17 csarven: minor note, the reports are submitted as an LDN, when the reports are created, its sent to the summary as an LDN, 15:30:36 csarven: so the summary itself is a conforming LDN 15:31:00 ... and there is rdfa on these too which, maybe someone will use in the future 15:31:15 ... i think that we are fairly stable with the reports and the spec 15:31:16 q? 15:31:26 ack eprodrom 15:32:34 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 15:33:26 I believe bengo's is AP or nearly AP too 15:33:30 I for one don't want to block LDN PR on asking for more AP implementation 15:33:32 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. 15:33:41 eprodrom: certainly ..... 15:33:59 bengo's is AP as well 15:34:03 true story 15:34:06 rhiaro: my implementation is AP and LDN compatible, its slightly broken currently, and i think bendo is using both as well 15:34:11 s/bendo/bengo/ 15:34:15 The strong interop documented by the tables demonstrates there's sufficient critical mass / implementation testing of the spec IMO 15:35:06 ack eprodrom 15:35:10 ack rhiaro 15:35:11 ack rhiaro 15:35:15 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 15:35:49 q+ 15:35:52 rhiaro: Anything that's in gray is because it's an optional feature. Failed mandatory would be red. 15:35:55 excellent 15:36:01 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 15:36:25 tantek: thats not the exact meaning i've seen in other groups. 15:36:40 rhiaro: they are MUST IF's so each of those 15:37:27 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 15:37:42 Just move all those columns to the right hand side, under a super-heading "OPTIONAL" 15:37:43 https://www.w3.org/TR/EARL10-Schema/ 15:37:55 csarven: we borrowed the test outcomes from the w3c's EARL, which used those values 15:38:17 I don't doubt that the db schema behind this has been reasoned out, I'm talking purely about the presentation 15:38:31 If it was enough to confuse me and sandro, then it will likely confuse various AC reps ;) 15:38:40 q+ 15:39:02 ... 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 15:39:04 q+ to see if we add MUST, SHOULD, MAY to the top of the columns that would make it obvious? 15:39:34 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 15:39:39 rhiaro, yes, and I for one trust you and csarven to figure out such details 15:39:40 csarven: we'll clear it up 15:39:47 thank you csarven 15:39:47 q- 15:40:00 q- 15:40:03 q- 15:40:04 eprodrom: i want to make sure that given that you have limited time, we get any process stuff done 15:40:19 ... okay i just cleared the queue, good for me :) 15:40:20 q+ 15:40:49 rhiaro: before we go to PR, we'd like to publish an updated CR with editorial changes 15:41:02 tantek: we don't need to do an updated CR for changes that are clearly editorial 15:41:08 I for one am +1 on taking to PR pending editorial edits and presentational update to the implementation report 15:41:12 PROPOSED: request transition of LDN to PR 15:41:36 eprodrom: okay, if we don't need to do that then i'm going to make the proposal for transition without qualification ... 15:42:19 +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. 15:42:20 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 15:42:27 PROPOSED: request transition of LDN to PR with editorial updates 15:42:38 +1 15:42:39 ... oh the latest one is sept 2nd, so we can definitely count those as timeout 15:42:42 +1 15:42:43 +1 with presentational update to the implementation report to clarify MUST vs optional features, and clustering of implementations as editor, wg, outside wg. 15:42:43 +1 15:42:44 +1 15:42:48 +1 15:42:49 +1 15:42:51 +1 15:42:55 sandro: those changes being the acknowledgement sections 15:42:58 eprodrom: correct 15:43:04 +1 15:43:08 +1 15:43:28 eprodrom: if you have a -1 to throw in, do it now 15:43:32 RESOLVED: request transition of LDN to PR with editorial updates 15:43:34 ... or say you need more time 15:43:37 congratulations, csarven and rhiaro ! 15:43:45 congrats csarven and rhiaro! 15:43:59 we need a soundtrack when things like this are approved 15:44:02 also thanks sandro for requesting clarifications on waiting for commenter issues 15:44:13 Thanks all! 15:44:15 eprodrom: thank you sarven for hanging on some extra time 15:44:26 ... any extra discussion around LDN before we move on? 15:44:26 Still around.. just with added 3 year old background-stuff 15:44:43 eprodrom: anything else we wanted to cover? 15:44:47 sandro: i think we are good 15:45:00 TOPIC: micropub 15:45:10 eprodrom: we need to get some updates about the test suite 15:45:35 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 15:45:52 ... despite the vote for going to PR, we didn't meet our standards for PR 15:47:08 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 15:47:24 basically, do we now meet our standards for PR for micropub? and if so, we should re PROPOSED and re RESOLVED accordingly 15:47:30 ... 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 15:47:48 sandro: have you been in contact with people to get a clue as to when they might do that? 15:48:10 aaronpk: i have talked to a couple people but i havent' heard back yet on when 15:48:35 q? 15:48:42 I think that was from before? 15:48:44 ack rhiaro 15:48:49 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? 15:49:15 eprodrom: do we need to reel back in our proposal? 15:50:03 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. 15:50:14 dmitriz has joined #social 15:50:24 aaronpk: we have not, mine did not change with the new tests, so the report is still the same 15:50:35 tantek: so have we heard of any changed reports since? 15:50:39 aaronpk: no 15:51:11 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 15:52:00 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 15:52:04 ... thoughts? 15:52:33 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 15:53:17 tantek: ideally it should be simply a matter of a few days, not two weeks 15:53:42 PROPOSED: requesting advancement of Micropub to PR conditioned on ... 15:53:45 eprodrom: it sounds like we have something along the (typing out proposal) 15:54:07 PROPOSED: requesting advancement of Micropub to PR conditioned on confirmation of client implementations 15:54:25 sandro: i'm trying to figure out where the bar is here 15:54:36 ... the strictest would be throw out all the .. 15:54:41 -1! 15:55:06 sandro: i'm trying to figure out where else is rational to set the bar at 15:55:37 tantek: it seems reasonable to me 15:55:51 sandro: if you pitch it to them that it fills out everything for them 15:56:14 +1 with sandro's details of how to confirm client implementations 15:57:46 PROPOSED: requesting advancement of Micropub to PR conditioned on confirmation of client implementations 15:57:46 ben_thatmustbeme: so are we throwing out all the implementation reports? 15:58:27 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 15:58:35 KevinMarks2 has joined #social 15:58:37 ... i picked those two because they cover most of it 15:58:45 fabrixxm has joined #social 15:58:48 tantek: yes, i think those are good canaries 15:59:12 PROPOSED: Request Micropub -> PR when new complete test suite is reported passed by impls from editor, shpub, micropublish, and no one else reports problems 15:59:19 +1 15:59:21 +1 15:59:23 +1 15:59:28 +1 15:59:32 +1 15:59:34 +1 15:59:39 (and reasonable effort is made to contact them) 15:59:57 +1 16:00:05 +1 16:00:17 sandro: can we extend the meeting a bit? 16:00:31 I can give a 2 minute AP update 16:00:33 +1 ok with extending meeting 30 min (not expecting it to take that long) 16:00:45 eprodrom: we have a lot to cover still 16:00:45 RESOLVED: Request Micropub -> PR when new complete test suite is reported passed by impls from editor, shpub, micropublish, and no one else reports problems 16:01:00 I could do a meeting next week 16:01:05 congrats aaronpk on getting (re)resolved to take Micropub to PR! 16:01:08 heh 16:01:23 no objections 16:01:28 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 16:01:35 15 minutes extension 16:01:48 +1 16:01:54 eprodrom: meeting extended 15 min 16:01:56 eprodrom: if there are no objections, i am going to unilaterally extend by 15 minutes 16:01:59 chair: tantek 16:02:43 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 16:02:59 eprodrom: that updated draft is not ready but i should have something by the end of the week 16:03:19 ... the normative change was to remove those at-risk features that were lacking implementations. 16:04:01 .. the editorial was remove the 'at-risk' labels, and archive exit criteria and changelog 16:04:06 ... so next steps? 16:04:46 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 16:05:15 sandro: it depends on a couple people, if you get it to me by thursday, we should be able to publish by tuesday 16:05:36 tantek: if we get all our ducks in a row too, we could probably do LDN too 16:06:02 tantek: so we are aiming for tuesday for all 3 of these PRs 16:06:06 ++ 16:06:10 sandro: optimistically 16:06:18 the race is on 16:06:30 tantek: and we are not going to be holding any up, get your work done or you miss the tuesday train 16:06:41 tantek: i'm assuming we haven't seen any new AS2 issues come up 16:06:46 eprodrom: yes, only editorial 16:07:16 chair: eprodrom 16:07:24 tantek: its not a huge deal if one misses it, but it would be nice to get all our PRs together 16:07:46 AP will be very short 16:07:53 eprodrom: websub looks long, i wonder if we can postpone until next meeting? 16:07:54 +1 (but read the mail I sent earlier today) 16:08:21 that's fine 16:08:37 TOPIC: activitypub 16:08:48 link to that email? 16:09:01 https://lists.w3.org/Archives/Public/public-socialweb/2017Mar/0016.html 16:09:01 +1 sandro! 16:09:02 sandro: there was an email this morning that people should read and respond to 16:09:07 we really should put WebSub first (non-admin) then for the 2017-03-28 16:09:10 looking forzward to see responses ;) 16:09:35 julien hoping you can make it on 2017-03-28! 16:10:36 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 16:11:05 tantek: can i get a quick few minutes on the CG issue 16:11:21 I also think it's dead 16:11:47 tantek: i noticed that there was some spam coming in from W3C Social Business Community Group, it looks to be dead 16:12:01 can we request w3c close it and direct people to the new CG 16:12:15 eprodrom: sounds good, can you phrase it as a proposal? 16:12:24 PROPOSED: request that W3C Social Business Community Group be closed with a message inviting anyone there to join the W3C Social Web Community Group 16:12:34 +1 16:12:44 +1 16:12:48 +1 16:12:54 +1 16:12:59 +1 16:13:09 there are tons of dead CGs so the more dead ones closed, the better 16:13:19 +1 16:13:26 sandro: i'll try to reach out to the chair too, but it sure looks like the group is dead 16:13:28 RESOLVED: request that W3C Social Business Community Group be closed with a message inviting anyone there to join the W3C Social Web Community Group 16:13:43 tantek: and make it clear that if they do have stuff to work on they can do that in the social web CG 16:13:47 Thanks! 16:14:03 trackbot, end meeting 16:14:03 Zakim, list attendees 16:14:03 As of this point the attendees have been aaronpk, julien, eprodrom, csarven, tantek, ben_thatmust, bengo, cwebber, sandro, wilkie, rhiaro, + 16:14:11 RRSAgent, please draft minutes 16:14:11 I have made the request to generate http://www.w3.org/2017/03/14-social-minutes.html trackbot 16:14:12 RRSAgent, bye 16:14:12 I see no action items 16:14:15 thanks all!