Social Interest Group Teleconference -- 27 May 2015

<trackbot> Date: 27 May 2015

<hhalpin> The teleconstarts in 6 minutes, correct?

<AnnB> yes

<hhalpin> ok, let's hope people remember there's been a time change!

<AnnB> what's up with zakim

<AnnB> aaargh

<hhalpin> Weird, well trackbot figured it out

<AnnB> but we still need zakim, right

<hhalpin> Zakim has been rather flaky, which is why we're going to migrate to WebEx

<hhalpin> I'll ping systems team

<AnnB> yes please

<hhalpin> Worse case, we use an ad-hoc Zakim code

<AnnB> no

<hhalpin> Let me see if Zakim works at all

<hhalpin> Not a good sign!

<elf-pavlik> https://www.w3.org/Guide/1998/08/teleconference-calendar.html#s_6438

<hhalpin> Yes, that's what's weird - it's clearly setup correctly internally

<AnnB> i was able to dial in

<AnnB> on regular num

<hhalpin> Ah, good AnnB

<hhalpin> It may just be that Zakim is having some odd bug connecting IRC to the telecon, but the telecon time is scheduled

<hhalpin> I've just reported it to Systems Team, I highly doubt this is effecting just us

<hhalpin> Anyways, time for the WebEx transition :)

<AnnB> hhalpin, will you please get the info we need for WebEx so everyone can be informed on what they are supposed to do

<hhalpin> FYI, I did re-approve Lloyd and Larry's IE requests for the IE

<AnnB> thanks

<hhalpin> Yes, but we'll do that in June.

<hhalpin> We'll have one month to work out the transition with Zakim as a backup before its discontinued by MIT

<AnnB> I'm suggesting it will be helpful to publish it in advance, so people have time to figure it out

<hhalpin> Groups are just beginning the transition so I'm letting other WGs go through the bugs first :)

<hhalpin> Will do as soon as possible in June.

<elf-pavlik> hi jasnell

<hhalpin> So quick notice folks - W3C systems *is* having some problems right now, so Zakim will not work today via IRC.

<AnnB> also hhalpin is present

<AnnB> and Ed Krebs

<AnnB> hhalpin explains about the transition to WebEx for meeting audio, instead of Zakim

<elf-pavlik> jasnell, can we add sioc: (similar as we have foaf:) to AS2.0 spec? http://www.w3.org/TR/activitystreams-core/#compact-iris

<AnnB> (discussion about what parts of WebEx we will use or not)

<hhalpin> It's a global problem, there is some larger issue with systems. In fact, wikis may be down as well today off and on!

<hhalpin> ACTION: hhalpin to send out Webex instructions [recorded in http://www.w3.org/2015/05/27-socialig-minutes.html#action01]

<trackbot> Created ACTION-7 - Send out webex instructions [on Harry Halpin - due 2015-06-03].

EdK will scribe

<elf-pavlik> scribenick: EdK

<AnnB> agenda: https://www.w3.org/wiki/Socialig/2015-05-27

Ann: last few weeks sketchy for attendance, agenda. See agenda in link above.

<hhalpin> Yes, minutes are being taken etc.

Last full meeting April 15. Call for minutes approval

<elf-pavlik> +1

<hhalpin> http://www.w3.org/2015/4/15-socialig-minutes.html

Minutes approved.

Several informal meetings. Minutes are available for the vocabulary session.

Not formal minutes, no need to approve.

Guangyuan sends regrets

<hhalpin> +1 the f2f meeting was very productive

Social WG Face2Face meetings - elf, Ann, Harry attended. Productive and valuable.

<hhalpin> ActivityPump

Reps from each technical community walked through code segments on how they'd solve problems, e.g. some for Indie Web, another for Pump.io community

Each critiqued their own (strengths, weaknesses), helped others understand about their own solutions.

Harry: thought meeting was productive, Europe attendees helpful, these folks don't get to some of the US sesssions.

<AnnB> F2F summary by Amy Guy (@rhiaro): http://rhiaro.co.uk/2015/05/socialwg3-summary

Activity streams 2.0 topics discussed.

Merging 2 streams was reviewed, as well as tracing conversations between large platforms like Twitter and Facebook (this part may have been at a lunchtime conversation

<AnnB> Harry: Claudio Venezia (Telecom Italia) informally talked about his use cases

Claudio had talked about hashtags and other tagging in video, social media. It would be helpful to capture some of those use cases.

Claudio hs having problems attending based on time, some discussion and negotiation will be needed to consider shifting. Doodle poll for IG moved this meeting back 1 hour, may need to do similar for WG

Next Face 2 Face on October in Japan along with Technical Plenary meeting, exact day to be announced.

Last week of October, which days for with WG's tba.

<elf-pavlik> https://github.com/w3c-social/social-interest/issues

Next topic, transfer Tracker to GitHub - any discussion?

<hhalpin> Is anyone against or for?

I'm Ok with GitHub, we're using it more and more here at Ford.

<johnbreslin> I'm

<johnbreslin> Good with GitHub

Ann: seems like a good solution. Question for Harry, any feedback from W3C?

Harry: Tracker was integrated with Zakim, but now that Zakim is depricating, then GitHub seems like a good solution.

Proposal to agree?

Question regarding deprecating irc IG channel and merging into WG channel. Ann's feeling is it could be distracting.

<hhalpin> I think basically groups can't meet at same time!

<AnnB> distracting to the socialwg

Ed had mentioned in previous discussion on 2 meetings that could happen at same time

<AnnB> EdK: do both the IG and the WG have the same intellectual property rights

<hhalpin> Nope, as long as we remember to say 'trackbot, end meeting'

John: in favor, will help keep the groups informed.

Ann: will make request to WG to share the same channel.

<hhalpin> The answer is that while scopes are different, there is an IE process for Social IG so I think it's OK from a legal angle.

Zakim aabb is EdK

Harry to double check IP protections are adequate.

<hhalpin> EdK, Zakim IRC is down

Should be OK, they've been careful, example is invited expert

Resolved: Moved tracking of work and issues to GitHub.

Agreement is to move to single irc pending approval by WG

Use Cases - haven't made much progress

Elf: focus should be on those proposed for "adoption"

<AnnB> https://github.com/w3c-social/social-ucr/issues

<elf-pavlik> and those which receive implementations proposals similar to ones presented during F2F3

Ann: thught fcus would be on those that were identified as needing clarity, where some disagreement may still be open

<johnbreslin> Sorry all I have to go collect kids. Talk soon

thanks John

<elf-pavlik> EdK: reminder of request from WG to help resolve User Stories with minor objections

<AnnB> user stories for API, by votes: https://www.w3.org/wiki/Socialwg/Social_API/Sorting_user_stories

Some of these got put into GitHub, still unclear on some of the nuances of teh new tool - such as notifications.

<elf-pavlik> PROPOSAL: invite authors of User Stories to provide concrete implementation details (similar to ones presented during F2F) which will provide strong ground for furture clarifications

<elf-pavlik> e.g. https://github.com/aaronpk/Micropub/tree/master/user-stories

<elf-pavlik> https://github.com/linkeddata/SoLiD/tree/master/UserStories

<elf-pavlik> https://github.com/w3c-social/activitypump/tree/master/userstories

<elf-pavlik> aaronpk, tsyesika and bblfish presented it

Above were examples done at the F2F

<elf-pavlik> having such implementation proposals can help a lot with prioritizing and clarifying objections

<elf-pavlik> we don't expect new API candidates besides three already represented

<elf-pavlik> we can *request* such implementation walk through

<elf-pavlik> Use Case TF meeting next week?

Harry: perhaps dedicate a meeting (next meeing) to work on use cases and specifically invite authors
... there is accepted use cases, those would be implemented. Those that have minor objections will not, but we can't get consenus on how to get them accepted unless they are all in the meeting

<elf-pavlik> before that use case authors *should* provide implementation proposals for review :) bblfish can do that for example

<elf-pavlik> AnnB, we can resolve this one just two of us :D https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Invite_friends_to_an_event

Some of the objections could be some minor language - eg video is posted at top, botttom - objection is use case shouldn't demand a specific location, these should be able to be wordsmithed in a way to gain consensus

<elf-pavlik> yes, only you gave 0

<elf-pavlik> PROPOSAL: let's start with "Entirely Positive or Positive Neutral" and leave "Minor Objections" for later

<elf-pavlik> https://www.w3.org/wiki/Socialwg/Social_API/Sorting_user_stories#Entirely_Positive_or_Positive_Neutral

<elf-pavlik> simpler to get the workflow and resolve some quickly

<elf-pavlik> no, it always stayed thare

EdK will try to help on minor objection use cases, but is primarily working on new use cases for federated social, which is work may get started this fall. The business need is huge and frankly businesses experiencing multiple platforms are best suited to identify the problems and use cases.

<elf-pavlik> +1 Use Case TF next week

may be able to try WEbex next week. Harry to send out info.

Meeting is adjourned.

Thanks all for attending!

<elf-pavlik> AnnB++ for making progress attitude!

<Loqi> AnnB has 25 karma

<elf-pavlik> hhalpin, Webx has SIP ?

<AnnB> hhalpin: yes, WebEx has SIP

<AnnB> ... also a Java client which enables dial-in

<elf-pavlik> hhalpin, please post instruction ASAP so we can prepare for next week TF meeting

<AnnB> trackbot, end meeting

- DRAFT -

Social Interest Group Teleconference

27 May 2015

Attendees

Contents

Summary of Action Items

Scribe.perl diagnostic output