18:00:35 RRSAgent has joined #social 18:00:35 logging to http://www.w3.org/2016/01/12-social-irc 18:00:37 RRSAgent, make logs public 18:00:37 Zakim has joined #social 18:00:39 Zakim, this will be SOCL 18:00:39 I do not see a conference matching that name scheduled within the next hour, trackbot 18:00:40 Meeting: Social Web Working Group Teleconference 18:00:40 Date: 12 January 2016 18:00:44 present+ 18:00:46 present+ 18:00:48 present+ 18:01:10 present+ 18:01:29 present+ Rob_Sanderson 18:01:43 be on in a second, phone is crashing ;x 18:01:45 present+ jasnell 18:01:49 present+ 18:02:03 Can we get a scribe for today? 18:02:13 scribe: sandro 18:02:33 i can scribe too, just had to make sure i had a good keyboard 18:02:43 present+ 18:02:50 present+ 18:04:23 https://www.w3.org/wiki/Socialwg/2015-01-05-minutes 18:04:33 I just created them sorry! I swear I remember doing it last week.. 18:04:44 So nobody will have reviewed them yet.. 18:04:52 yeah. I remember you posting them to the mailing list D: 18:04:59 yay welcome frank! 18:05:00 did they go to a different URL? 18:05:01 :D 18:05:02 wilkie: I can't even find my email! 18:05:07 I was looking for evidence 18:05:07 present+ cwebber2 18:05:13 present+ 18:05:31 I remember editing the attendee list 18:05:33 lol I see what happened 18:05:35 because it's always wrong 18:05:40 you did post them last week 18:05:43 did I use the wrong date? 18:05:44 rhiaro: https://www.w3.org/wiki/Socialwg/2016-01-05-minutes 18:05:45 https://www.w3.org/wiki/Special:Contributions/Rhiaro 18:05:45 present+ 18:05:47 hahaha 18:05:52 nope, but the new page links to 2015 18:05:54 2015 != 2016 18:05:58 derp 18:05:58 Welcome to Frank Karlitschek, new Invited Expert from ownCloud project 18:06:06 dates are HARD 18:06:22 fixed that oops 18:06:24 eprodrom: we use IRC for voting, out-of-bank discussion 18:06:38 okay, retract my previous statement, minutes were there all along 18:06:39 jaywink has joined #social 18:06:44 PROPOSED: Approve minutes of Jan 5 2016 18:06:48 +1 18:06:51 +1 18:06:52 +1 18:06:52 +1 18:06:53 +1 18:06:55 +1 18:07:03 +1 18:07:08 +1 18:07:16 RESOLVED: Approve minutes of Jan 5 2016 18:07:42 topic: upcoming F2F meetings 18:07:56 Frank has joined #social 18:07:56 eprodrom: March, hosting at MIT 18:07:59 https://www.w3.org/wiki/Socialwg/2016-03-16 18:08:01 PLEASE RSVP 18:08:06 welcome Frank ! 18:08:53 that was probably me, it looks like I never successfully muted (using someone else's phone, not sure why I failboated so bad) 18:09:01 also I accidentally hung up, I'm doing awesome 18:09:31 sorry me, first time :) 18:10:03 Rhiaro made 2 edits to [[Socialwg/2015-01-05-minutes]] https://www.w3.org/wiki/index.php?diff=87517&oldid=0 18:10:04 Sandro made 1 edit to [[Socialwg/2016-01-12]] https://www.w3.org/wiki/index.php?diff=87515&oldid=87513 18:10:05 Sandro made 1 edit to [[Socialwg/AS2 CR]] https://www.w3.org/wiki/index.php?diff=87518&oldid=87448 18:10:05 o/ jaywink 18:10:06 Aaronpk made 1 edit to [[Socialwg/2016-01-12]] https://www.w3.org/wiki/index.php?diff=87516&oldid=87515 18:10:11 topic: June F2F in Portland 18:10:33 aaronpk: Okay to host at ESRI Portland office 18:10:44 aaronpk: maybe I should create a doodle poll 18:11:06 Karli has joined #social 18:11:33 present+ jaywink 18:11:49 us++ 18:11:50 aaronpk: I will 18:11:53 us has 1 karma 18:12:02 eprodrom: any obvious conflicts 18:12:08 topic: New Invited Experts 18:12:19 hello frank! 18:12:23 Frank Karlitschek 18:12:42 Frank: Happy to be here, I consider this super important, to bring real standards to this space 18:13:03 .. I've been doing open source for ~20 years, board member of KDE project, and most well known as founder and leader of ownCloud 18:13:28 ... it's free software alternative to things like gdrive, icloud, etc. FRee and open source, with federation 18:14:12 ... original vision was sharing files, but now we do more in the social area. with ownCloud9 we'll have comments, etc, around shared files. Blurring the line between cloud storage and social networks 18:14:25 ... we really want to do this in an open, standard, right way! 18:14:43 ... hopefully we can help with making test implementations, etc 18:14:51 eprodrom: Thank you, welcome 18:15:16 topic: webmention draft 18:15:33 aaronpk: It was published! 18:15:39 https://www.w3.org/TR/webmention/ 18:16:01 the_frey has joined #social 18:16:13 eprodrom: Any changes in this version 18:16:31 aaronpk: no, you can look at gh commits, but really just formatting and references 18:16:56 eprodrom: issues continue to be tracked on github 18:17:06 https://www.w3.org/TR/social-web-protocols/ 18:17:10 yay 18:17:12 :D 18:17:13 No new updates 18:17:24 sandro: social-web-protocols was also published at the same time 18:17:29 eprodrom: great! 18:17:59 q+ 18:18:23 q? 18:18:25 aaronpk: There are some issues -- it would be good to keep talking about them on github 18:18:38 ack sandro 18:19:31 I'll add it to the Annotation WG agenda for tomorrow 18:19:55 sandro: This is a great time to tell folks about it, if you can think of anyone who should know 18:20:31 might be good to try to inform projects like wordpress, etc things 18:20:38 sandro: Sometimes it makes sense to really push the word out 18:20:45 +1 ben_thatmustbeme 18:20:59 ben_thatmustbeme, can you do that? 18:21:09 topic: ActivityPump 18:21:33 i'll try to reach out to them 18:21:44 tsyesika: Expecting a vote today on whether ap would go to FPWD 18:21:48 we thought today was where we approved the standards for fpwd 18:21:49 there is already a plugin for it, but its certainly a different thing to get them looking at it directly 18:21:51 not publish 18:21:55 :X 18:22:31 https://www.w3.org/wiki/Socialwg/2015-12-15-minutes <- 18:22:43 Request raise FPWD-blocking issues on ActivityPump and micropub by 12 Jan 2016 18:23:06 eprodrom: My fault for not putting this on the agenda, but yes, we agreed on this 18:23:48 tsyesika: I think we're ready to go ahead, yes 18:24:30 https://github.com/w3c-social/activitypump 18:24:32 http://w3c-social.github.io/activitypump/ 18:24:49 my phone keeps dropping off : 18:25:08 q? 18:25:12 q+ 18:25:21 ack cwebber2_remote 18:25:33 AUGH 18:25:35 phone dropped again 18:25:37 I'll say it here. 18:25:55 I think we're ready for FPWD. I was under the impression that we were voting today on both AP and micropub 18:25:57 apparently I was wrong 18:26:05 so we were supposed to publish by today? 18:26:37 eprodrom: I don't think you were wrong, they just didn't make it to the agenda 18:26:56 if that's true, I think we should publish, I was under the impression we scheduled things so that AP and micropub would be published at the same time 18:27:00 and the vote would happen today 18:27:07 hence my confusion things are up already 18:27:17 so does there need to be a vote even? we can do one 18:27:28 or should we just move on to process? 18:27:34 and get it published and up? 18:27:58 sandro: I no longer see a need to publish these at the same time, since there's no front-page news, etc 18:28:13 ok 18:28:21 PROPOSED: Publish FPWD of ActivityPump 18:28:24 +1 18:28:25 +1 18:28:26 +1 18:28:26 +1 18:28:27 +1 18:28:30 +1 18:28:34 +1 18:28:34 +1 18:28:42 +1 18:28:43 +1 18:29:18 RESOLVED: Publish FPWD of ActivityPump 18:30:36 w3.org/TR/activtypump 18:30:39 w3.org/TR/activitypump 18:31:47 activity api 18:31:49 sandro: this is a good time to settle the name, but it doesn't have to be final really 18:31:59 I think activitypump is fine personally... 18:32:19 activitypub! 18:32:21 eprodrom: as the person who introduced the term "pump", I kind of lean toward something more like "activity api" 18:32:21 I don't have another name really ready 18:32:25 rhiaro: haha! 18:32:35 lol 18:33:09 eprodrom: I'm fine with activitypump 18:33:17 the_frey has joined #social 18:33:39 topic: micropub fpwd 18:34:23 aaronpk: I haven't cleaned it up yet, so I'd like to not vote this week, but I'll try for next week 18:35:09 rhiaro: I like it 18:35:22 topic: AS2 Exit Criteria 18:35:24 rhiaro: activitypub would be fine by me 18:35:28 I can scribe 18:35:31 i can 18:35:32 assuming my phone doesn't cut out 18:35:40 scribe: cwebber2_remote 18:35:48 scribenick: cwebber2_remote 18:35:57 sandro: procedurally when we go to CR we need to spell out for the director and the public what's our exit criteria 18:36:20 and the procedure is usually 2 interoperable implementaitons 18:36:27 (i'm +1 on ActivityPub as well but don't have a strong opinion either way) 18:36:34 https://www.w3.org/wiki/Socialwg/AS2_CR#Exit_Criteria 18:36:35 sandro: we could go for a more strict version, 2 real versions 18:36:43 sandro: people suggested I write that down so I did 18:37:10 sandro: there are two proposals on this page, that 2 activitystreams must be used by at least 2 systems 18:37:11 (Can we go back to the name after current discussion? +1 on ActivityPub as well) 18:37:18 q+ 18:37:31 sandro: so tantek especially asked can we have a stricter verison 18:38:03 sandro: the stricter version is have 2 versions with produced and consumed by qualified implementations, and we have to have a report by a developer, they have to make it available so we can see that it does what it does 18:38:11 sandro: and they have to have a reason for that feaure 18:38:39 q+ to -1 asking for rationale for every feature 18:38:49 sandro: I was thinking this way in response to the criticism that some people will look at this work and say "nobody is using this" and this gives us for solid proof to show it's used 18:38:58 sandro: that's me laying out the space, I don't have a strong opionion 18:39:25 sandro: for example, paging is one feature, so at some point someone has to cluster what the features are 18:39:31 sandro: what granularity? 18:39:40 q? 18:39:45 q+ james 18:39:51 jasnell: I can't queue up on irc so I'll queue up here 18:39:54 ack Arnaud 18:40:05 Arnaud: I appreciat ethe intent but I think it's going too far 18:40:16 Arnaud: I've never seen this requirement before 18:40:33 Arnaud: and it prevents someone from doing an implementation in a product they can't show you 18:40:36 Arnaud: (this requirement to have access) 18:40:48 Arnaud: it's great if someone can give you access, and maybe we should ask that, and if so it's great, b ut not sure it should be a must 18:41:06 +1 to Arnaud 18:41:15 Arnaud: as for features, the burden you're putting on people may disincentivize people adding them 18:41:28 Arnaud: it seemas backward, we preusmably put things in the spec because we must have a reason to do it 18:41:32 Arnaud: it seems odd to me 18:41:49 sandro: the quick answer, i think there's a space between we thought it would be useful and it actualy is useful 18:42:13 q- 18:42:15 Arnaud: maybe there's a middle ground we can find there, indicate which things you found useful, without people documenting why they use it 18:42:25 ack azaroth 18:42:30 (Arnaud covered my point very well already) 18:42:38 eprodrom: I do want to move us along, so I guess azaroth next? oh okay 18:42:43 yw :) 18:42:45 eprodrom: do you want to reiterate here? 18:43:12 azaroth: really just to +1 Arnaud, having people write the documentation for use cases, considering the extent of the spec, would be very time consuming 18:43:32 azaroth: even just "please write an email and say what and why you're using" would be sufficient to capture the intent 18:43:42 ack james 18:43:51 azaroth: It would be a big barrier to force people to describe all their motivations. No need to get all processy. Just ask for an email about what they're using 18:44:22 jasnell: one thing we chose not to do at the beginning was to document those things, now we're doing a reverse process figuring out use cases, but I think at this point it might be worth documenting what the key use cases are 18:44:51 jasnell: I can take a first stab at giving a formal list on core use cases based on current spec 18:44:55 ... and we can go from there 18:45:10 eprodrom: that sounds reasonable, I think that the motivation here is to show widespread use of those use cases 18:45:10 q+ 18:45:25 ack sandro 18:45:31 ... I think we have the use cases from first principles that shows they're worth having 18:46:02 argh, lost my connection 18:46:11 sandro: so I haven't heard anyone say no to the high bar, so I suggest maybe what we do is have the exit criteria be the minimum one (every feature of AS2 used) but then we show what every feature is used in implementation 18:46:19 sandro: maybe we talk a bit and try to find out what has more data 18:46:28 sandro: in light of those implmentations 18:46:52 sandro: so I'll say, james, does what I'm saying make sense, would you be interested in updating your future use cases documentation with things to be implemented(?) 18:47:01 eprodrom: yep hi I'm sorry 18:47:07 jasnell: I'm driving on mute (???) 18:47:25 sandro: if you're interested and see the value in gathering the use cases, should we do an implementation report 18:47:35 sandro: see what use cases we think they're doing 18:47:47 sandro: because I think we need to have an implementation report 18:48:05 sandro: so if we can make use cases and get the implementation report... does that make sense and sound compelling? 18:48:33 jasnell: yeah, I'm chalenging how we reconcile that because I'm not sure what list we have of what we're reconciling against 18:48:54 sandro: so I'm suggesting we go with the minimum version, and we have the second part to do our own good effort 18:48:59 eprodrom: that makes a lot of sense 18:49:05 eprodrom: and makes our process a lot more defensible 18:49:35 eprodrom: there were some parts of this that were a little bit more controvercial, as in terms of things that are accessible vs private vs commercial not-easy-to-access 18:49:43 ... but I guess we'll deal with that on a case-by-case basis? 18:49:52 sandro: yes we'll report based on what we can learn from them 18:50:10 eprodrom: yes as a decision making point, can we deal with this as a proposal to use the exit criteria as defined in proposal 1? 18:50:11 define "system"? 18:50:14 sandro: yes I'll define it 18:50:26 PROPOSED: Our CR-Exit for AS2 will be: Each feature of AS2 must be used by at least two systems 18:50:32 q+ 18:50:51 PROPOSED: Our CR-Exit for AS2 will be: Each feature of AS2 must be used by at least two independent implementations 18:51:16 q- 18:51:16 +1 18:51:19 +1 18:51:20 +1 18:51:21 +1 18:51:25 +1 18:51:26 +1 18:51:27 +1 18:51:29 +1 18:51:36 +1 18:51:41 +1 18:51:55 RESOLVED: Our CR-Exit for AS2 will be: Each feature of AS2 must be used by at least two independent implementations 18:53:01 sandro: next on AS2 is test suite / validator stuff, probably 18:53:18 topic: Action Items 18:53:48 q+ for later to drop a link to the Doodle poll for the June meeting 18:54:05 eprodrom: I got some action items done, ACTION-80 and ACTION-85 18:54:12 q? 18:54:16 ack aaron 18:54:16 aaronpk, you wanted to discuss later to drop a link to the Doodle poll for the June meeting 18:55:18 action-84? 18:55:18 action-84 -- Sandro Hawke to Bring issue to i18n -- due 2015-12-09 -- OPEN 18:55:18 http://www.w3.org/Social/track/actions/84 18:55:29 q+ 18:55:33 not clear, will figure out. 18:55:44 q+ 18:55:48 ack cwebber2_remote 18:55:50 topic: AOB 18:55:54 +1 to ActivityPub 18:55:58 and my phone droped again 18:56:11 I'm convinced by Amy's rationale :) 18:56:15 but I'll say +1 activitypub :) 18:56:17 I think it's fine 18:56:18 I am for it too 18:56:19 :) 18:56:24 \o/ 18:56:24 if that matters :P 18:56:28 I like both activitypub and activitypump 18:56:31 present+ tantek 18:56:34 PROPOSED: change name of ActivityPump to ActivityPub 18:56:36 today is not a good day for me to be on this call :) 18:56:40 phones hate me 18:56:42 +1 18:56:44 +1 18:56:45 +1 18:56:46 +1 18:56:48 +1 18:56:49 +0 18:56:51 +0 18:56:57 +0 18:57:04 +0 18:57:04 -0 (I like the pump metaphor) 18:57:09 +0 (fine with both - though pub's have good beer!) 18:57:17 q? 18:57:41 tantek: Why change name at last minute? 18:57:55 eprodrom: It's just it's caried from pump.io without being that related 18:58:00 Note: I'm also +1 on activitypump :) 18:58:13 I always liked activitypump, but rhiaro makes a good case 18:58:24 and eprodrom doesn't seem excited about the name 18:58:42 sandro: I was asking if we wanted a hyphen! 18:58:44 one question is, does aaronpk feel like it dilutes "micropub" as a name? 18:59:06 tantek: so you're saying "pump" isn't warranted since it's that like "pump.io" 18:59:27 eprodrom: Yeah, pump.io folks wont recognize it in activity pump 18:59:31 q? 18:59:38 ack aaronpk 18:59:42 +1 (that motivates the change for me) 19:00:12 RESOLVED: change name of ActivityPump to ActivityPub 19:00:12 great, ship it 19:00:16 unexpected agenda item: rename activitypump! 19:00:30 activitypub 19:00:45 agenda? 19:00:48 I have to leave now 19:00:48 ok then 19:00:54 sounds like call is over anyway 19:00:57 good call! 19:01:02 I have to leave soon too - AB meeting 19:01:05 link to doodle poll for the pdx meeting: http://doodle.com/poll/5a8nfcfkqiwxwhpv 19:01:08 just to have that in hte minutes 19:01:12 yay 19:01:21 trackbot, end meeting 19:01:21 Zakim, list attendees 19:01:21 As of this point the attendees have been aaronpk, ben_thatmustbeme, eprodrom, sandro, Rob_Sanderson, jasnell, wilkie, Arnaud, rhiaro, cwebber2, tsyesika, jaywink, tantek 19:01:26 thanks all! nice first phone meeting :) hangouts works fine 19:01:29 RRSAgent, please draft minutes 19:01:29 I have made the request to generate http://www.w3.org/2016/01/12-social-minutes.html trackbot 19:01:30 RRSAgent, bye 19:01:30 I see no action items