#social 2015-12-03

2015-12-03 UTC
#
aaronpk
eprodrom: if we were going to do September TPAC, March MIT, could we do another in between?
#
aaronpk
aaronpk: Portland!
#
aaronpk
rhiaro: December would be like a party since we finished everything right?
#
aaronpk
eprodrom: most of us probably need around 8 weeks of planning time
#
aaronpk
... can we pick a time now for March?
#
aaronpk
cwebber2: could we do it right before libre planet?
#
aaronpk
eprodrom: march wed-thu 16-17?
#
aaronpk
tantek: then have friday the 18th off
#
tantek
sandro perhaps we could do an IWC MIT before/after as well?
#
eprodrom
reserve 16-17 March 2016 F2F at MIT
#
aaronpk
tantek: if we like the idea of portland in june we can capture that as a general range and figure out details later
#
aaronpk
... open source bridge is June 21-24 in Porltand
#
aaronpk
... I don't be able to do the week before that
#
aaronpk
eprodrom: rough plan is March 16-17 at MIT and then late June in Portland, September in Lisbon, then December in San Francisco
#
aaronpk
... next steps?
#
aaronpk
sandro: how about we set up the page and start having people RSVP
#
aaronpk
TOPIC: clarify Github workflow
#
aaronpk
sandro: my sense is we had a culture clash between open source workflow vs w3c culture
#
aaronpk
... where someone makes a comment and we're obligated to formally address the comment
#
aaronpk
... we don't have to necessarily make them happy, but we have to do our best to make sure they're aware we handled it fairly
#
aaronpk
... at a transition meeting we have to report how we handled those
#
aaronpk
... each one should end with a sense of closure
#
aaronpk
... so it's fine to close issues with a polite my sense is we reached a resolution here, if you don't agree, comment this way,
#
Zakim
sees rhiaro on the speaker queue
#
aaronpk
... we need to not stomp on people on github
#
Zakim
sees rhiaro on the speaker queue
#
aaronpk
eprodrom: we spoke yesterday about process a little about AS2, and we discussed editors have discretion to deal with issues, and if there is not a willingness to defer to the editor then we'd take it to a group proposal and resolution
#
aaronpk
sandro: so if that is communicated clearly to the commenter then that's fine
#
aaronpk
... the edfitor should post "i feel like this issues is closed, if you don't agree, say so and i will escalate it to hte working group"
#
tantek
s/edfitor/editor
#
aaronpk
eprodrom: we don't need fto vote on every issue, we've had some small issues fixing spelling mistakes etc
#
aaronpk
sandro: i've had luck where if you ask the person are you satisfied with my handling of the issue that makes people happy
#
aaronpk
... i'd be inclined to not mark it as closed
#
Zakim
sees rhiaro, kevinmarks_ on the speaker queue
#
aaronpk
... what i feel would be the best is ask people do you feel satisfied with how this was handled, and if so can you close it by this date
#
aaronpk
rhiaro: ask them toclose it by a certain date
#
eprodrom
q?
#
Zakim
sees rhiaro, kevinmarks_ on the speaker queue
#
aaronpk
... so i queued to say we probably all agree, but we should write it down so that we can refer people to this later
#
eprodrom
ack rhiaro
#
Zakim
sees kevinmarks_ on the speaker queue
#
aaronpk
.. so that people who want to complain for the sake of complaing we can say you're wrong
#
eprodrom
ack kevinmarks_
#
Zakim
sees no one on the speaker queue
#
aaronpk
kevinmarks_: if we're going to discuss the process, it would be good to constrain each issue to a single issue
#
rhiaro
q+ to say Cooperating in creating new individual issues if multiple crop up in a single thread, and staying on topic. If a new thought occurs to you whilst writing a reply... you are empowered to stop typing, and open a new issue instead.
#
Zakim
sees rhiaro on the speaker queue
#
aaronpk
... lets make sure to mention this in the process so we have a place to refer to that
#
aaronpk
sandro: one bit of advice we could say is if you think this might be a different issue, err on the side of more separate issues
#
eprodrom
q?
#
Zakim
sees rhiaro on the speaker queue
#
aaronpk
rhiaro: so i wrote this on the agenda
#
Zakim
sees rhiaro on the speaker queue
#
eprodrom
ack rhiaro
#
Zakim
rhiaro, you wanted to say Cooperating in creating new individual issues if multiple crop up in a single thread, and staying on topic. If a new thought occurs to you whilst writing
#
Zakim
... a reply... you are empowered to stop typing, and open a new issue instead.
#
Zakim
sees no one on the speaker queue
#
Zakim
sees Arnaud on the speaker queue
#
tantek
q+ to request: put burden/responsibility on those posting multi-issues to split them out to separate issues if they think the additional issues are worth being discussed.
#
Zakim
sees Arnaud, tantek on the speaker queue
#
aaronpk
eprodrom: the only thing i disagree with is that i would like editors to be able to close minor issues
#
aaronpk
... would you mind copying this to a wiki page?
#
aaronpk
... throw that on a page and then we can have a quick proposal to accept that page
#
Zakim
sees Arnaud, tantek on the speaker queue
#
eprodrom
q?
#
Zakim
sees Arnaud, tantek on the speaker queue
#
eprodrom
ack Arnaud
#
Zakim
sees tantek on the speaker queue
#
aaronpk
Arnaud: in my opinion it's the lack of proces that leads to this kind of thing, the idea that the ?? should be at risk by playing with access rights is really wrong
#
eprodrom
q?
#
Zakim
sees tantek on the speaker queue
#
aaronpk
sandro: i'd be inclined to leave the access control out of the proposal
#
aaronpk
tantek: there was an explicit request to clarify that
#
Arnaud
s/?? should be at risk/problem should be addressed/
#
aaronpk
rhiaro: part of the problem was that who had the owner of the org was weird
#
eprodrom
q?
#
Zakim
sees tantek on the speaker queue
#
aaronpk
sandro: if you see a violation of these then email chairs
#
eprodrom
ack tantek
#
Zakim
tantek, you wanted to request: put burden/responsibility on those posting multi-issues to split them out to separate issues if they think the additional issues are worth being
#
Zakim
... discussed.
#
Zakim
sees no one on the speaker queue
#
aaronpk
tantek: when some of these multi-issue threads start happening, when the editor responds to the original issue, i'd like to make it explicitly clear that if there are tangential issues it's the burden/responsibility of the person who raised them to make them new issues
#
aaronpk
sandro: we talked also about labels in the titles like "blocking"
#
aaronpk
tantek: how about we not solve that until it's a problem
#
bengo
q+ to talk about charter deliverables vs work items labels e.g. overloaded "Social API" and lack of "Federation Protocol" repo
#
Zakim
sees bengo on the speaker queue
#
Zakim
sees bengo on the speaker queue
#
eprodrom
ack bengo
#
Zakim
bengo, you wanted to talk about charter deliverables vs work items labels e.g. overloaded "Social API" and lack of "Federation Protocol" repo
#
Zakim
sees no one on the speaker queue
#
cwebber2
I added an item to the wiki as a possible thing to discuss, if we have extra time
#
aaronpk
bengo: I started an issue that got out of hand on webmention, but because some of the work items are related to the same thing but happening independently, it's tempting to jump in on a broader issue. especially as federation will start to be talked about, would it be beneficial to have topical repos separate from an individual spec so that there's a place for this converation
#
aaronpk
... at the very least i feel like there may be benefit to having a repo for federation protocol separate from actiivtypump so that there's a separate place
#
aaronpk
sandro: how about the social web protocols document
#
aaronpk
cwebber2: we also have the mailing list and telcons
#
aaronpk
tantek: irc is a good place to start
#
aaronpk
tantek: the issue ben is bringing up is that the github repos allow anyone on github to file an issue/comment, and if you're not a WG member or participant we say you cant' participate in the telcons and meetings, so there's a little asymmetry going on there. we should address what's the policy for if you're not a member of the WG
#
wseltzer
q+
#
Zakim
sees wseltzer on the speaker queue
#
aaronpk
... if you're not a member then you're not obligated to the processes
#
aaronpk
sandro: i think we treat that as public comments
#
aaronpk
there are communication venues we have that don't require you're a WG member
#
wseltzer
q-
#
Zakim
sees no one on the speaker queue
#
aaronpk
rhiaro: how do we treat issues that are raised ont he public mailing list
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
aaronpk
cwebber2: sometimes an editor wants to do things in a specific place and then someone says i raised it in this other venu and you didn't respond
#
aaronpk
... i think we should cater to the editor's preferred communication medium
#
aaronpk
tantek: that's been accepted with a bunch of prior practice at w3c
#
aaronpk
.. the spec has a "here's where you go to discuss it" section
#
aaronpk
... some peopel say github, some say email
#
aaronpk
... and we promise to respond to comments here
#
aaronpk
... if you send feedback elsewhere we don't guarantee a response
#
eprodrom
PROPOSED: Accept https://www.w3.org/wiki/Socialwg/github as the github procedure for the Social WG
#
aaronpk
sandro: can we just please have it all on github instead of per document?
#
aaronpk
tantek: that seems to be the emerging trend
#
eprodrom
+1
#
bengo
+1
#
aaronpk
sandro: on the first bullet i think editors should have the ability to close issues
#
aaronpk
tantek: one of the antipatterns we saw was that an editor closed an issue because the original topic was adddressed and then someone else reopened it because an unrelated topic in the thread was not addressed, do we have enough language here to address that?
#
azaroth
+1
#
eprodrom
RESOLVED: Accept https://www.w3.org/wiki/Socialwg/github as the github procedure for the Social WG
#
aaronpk
Arnaud: this is something the whole WG should be made aware of, so we should make a point of going over this on the next telcon or something to make sure everyone is aware
#
aaronpk
here is the specific version at the point of this resolution: https://www.w3.org/wiki/index.php?title=Socialwg/github&oldid=87079
#
aaronpk
sandro: i'll send an email right now
#
aaronpk
eprodrom: okay that leaves us with about 30 minutes
eprodrom_ joined the channel
#
aaronpk
... how much bandwidth do we have for additional issues on other docs?
#
aaronpk
cwebber2: i also added a new item to the agenda
#
aaronpk
cwebber2: we'd like to add myself as a co-editor of activitypump
#
aaronpk
tantek: sounds good to me
#
aaronpk
RESOLVED: add cwebber as co-editor of activity pump
#
aaronpk
TOPIC: post type discovery
#
aaronpk
tantek: i feel pretty good about the state of the algorithm, it's been pretty stable for a while
#
aaronpk
... what i want to do is to make a call similar to the social web protocols document, if people know of any issues that would be a FPWD blocker, to file them by the next telcon
#
aaronpk
... with the intent that I will try to address those issues so that we can take it to FPWD, perhaps even to take both the protocols documetn and this at the same time
#
aaronpk
... i want to bring this up. it's come up several times as a piece that's useful for building things
#
aaronpk
sandro: i'm still confused about its role
#
aaronpk
rhiaro: it's useful to go for something where type is implied through properties (microformats) to something with specific types (activitystreams)
#
aaronpk
... so it's obviously useful, but is it like WG useful or just useful?
#
aaronpk
tantek: James said it's useful even outside of microforamts, because the type property in AS is optional, so if you want to build a system that is dependent on type, you could use it to fill in that type
#
aaronpk
rhiaro: but AS doesn't have implied types
#
aaronpk
tantek: AS still has photos and such
#
aaronpk
q+ to discuss relation with webmention
#
Zakim
sees aaronpk on the speaker queue
#
aaronpk
rhiaro: okay i just thought there weren't enough semantically relevant properties
#
bengo
q+
#
Zakim
sees aaronpk, bengo on the speaker queue
#
aaronpk
tantek: type is optional, i don't know why, but it is. the purpose is to use this to determine type.
#
aaronpk
bengo: i think James said this sort of thing is useful, but the way it's written right now is too specific, i'l file an issue
#
aaronpk
rhiaro: maybe if we cangeneralize it that might help
#
aaronpk
tantek: feel free to open a vague issue and i'll see what i can do
#
Zakim
sees aaronpk, bengo, Arnaud on the speaker queue
#
bengo
q-
#
Zakim
sees aaronpk, Arnaud on the speaker queue
#
aaronpk
tantek: there are at least 2 implementations
#
Zakim
sees aaronpk on the speaker queue
#
aaronpk
... kyle impleemnted it for his reader
#
eprodrom
q?
#
Zakim
sees aaronpk on the speaker queue
#
Zakim
sees aaronpk on the speaker queue
#
eprodrom
ack aaronpk
#
Zakim
aaronpk, you wanted to discuss relation with webmention
#
aaronpk
... he used his implementation to present posts differently
#
Zakim
sees no one on the speaker queue
#
eprodrom
scribenick: eprodrom
#
eprodrom
aaronpk: PTD is also useful for Webmention
#
eprodrom
aaronpk: I would like to reference it. When you receive a post, you can identify it.
#
eprodrom
tantek: potential future dependency
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
aaronpk
scribenick: aaronpk
#
tantek
PROPOSED: make any FPWD- issues on Post Type Discovery visible by next telecon 12/8
#
eprodrom
+1
#
azaroth
+1
#
rhiaro
wow, thanks bengo, you're the fastest issue raiser in the west
#
bengo
0
#
sandro
-0 not comfortable with how it fits in, but not interested in raising an issue
#
eprodrom
RESOLVED: make any FPWD- issues on Post Type Discovery visible by next telecon 12/8
#
aaronpk
eprodrom: i think that takes care of PTD
#
aaronpk
... that wraps us up except for closing additional issues
#
tantek
sandro I filed https://github.com/w3c-social/post-type-discovery/issues/4 for you - I hope that captures your question.
#
aaronpk
... i for one would rather spend the next 10 minutes using my brain or somehow trying to revive it so i'm not sure trying to dig into additional issues is the best use of the next 10 minutes
#
aaronpk
... so i'd like to adjourn and see you in march
#
aaronpk
*applause*
#
eprodrom
trackbot, close meeting
#
trackbot
Sorry, eprodrom, I don't understand 'trackbot, close meeting'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
#
eprodrom
trackbot, end meeting
#
trackbot
is ending a teleconference.
#
trackbot
Zakim, list attendees
#
Zakim
As of this point the attendees have been Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme, cwebber,
#
Zakim
... tantek, hhalpin, james, tsyesika, wseltzer, akuckartz, shepazu, Rob_Sanderson, Shane_, rene, cwebber2, Benjamin_Young, bengo
#
trackbot
RRSAgent, please draft minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2015/12/02-social-minutes.html trackbot
#
trackbot
RRSAgent, bye
#
RRSAgent
ACTION: aaronpk publish new editor's draft of webmention before next telcon [1]
#
RRSAgent
ACTION: eprodrom to Continue developing federation aspects of existing candidate specs (ActivityPump, SoLiD, Micropub/IndieWeb building blocks) and in parallel Evan will curate requirements from user stories and other federation protocol efforts, with documented reasons for non-requirements [2]
#
RRSAgent
ACTION: Sandro to bring issue to i18n [3]
bengo, kevinmarks2, kevinmarks, kevinmarks_ and tantek joined the channel
bengo joined the channel
kevinmarks, kevinmarks2 and Arnaud joined the channel
tilgovi, bblfish, kevinmarks2, jaywink, tantek, kevinmarks, kevinmarks_, the_frey and shevski joined the channel
#
ben_thatmustbeme
!tell sandro you probably want to update https://www.w3.org/wiki/Socialwg#Harry
#
Loqi
Ok, I'll tell them that when I see them next
bblfish_, elf-pavlik, tommorris_, shevski, tantek, kevinmarks2, kevinmarks, KevinMarks, jasnell, the_frey, shepazu and bengo joined the channel
#
sandro
thanks, ben_thatmustbeme
#
Loqi
sandro: ben_thatmustbeme left you a message 4 hours, 53 minutes ago: you probably want to update https://www.w3.org/wiki/Socialwg#Harry http://socialwg.indiewebcamp.com/irc/social/2015-12-03/line/1449145553318
KevinMarks joined the channel
bengo, tantek, the_frey, tilgovi, jaywink and shevski joined the channel
#
jasnell
All... the Editor's Drafts have been updated based on the conversations from the F2F. The intent is to publish a new Working Draft this week
#
jasnell
(by Friday)
#
jasnell
Please take a look at the current drafts and get feedback submitted as Github issues
#
tantek
jasnell++ great work
#
Loqi
jasnell has 38 karma
#
jasnell
At the f2f, it was decided to allow for two weeks of comments to get issues addressed before going to CR
#
jasnell
(in January)
#
jasnell
tantek: I added a privacy considerations section. I took a few liberties with it to make it a strong default position. please take a look and provide feedback
#
tantek
jasnell - will do
#
tantek
did you see the TAG Security & Privacy questionaire ?
#
tantek
yes that's it! consider perhaps including answers to those, e.g. I did that with the CSS3-UI CR: http://www.w3.org/TR/2015/CR-css-ui-3-20150707/#security-privacy-considerations
#
jasnell
I hadn't seen that previously but will go through it
#
tantek
Right now the AB etc are evaluating the questionnaire and looking for feedback for spec inclusion
#
tantek
so I of course decided to dogfood it and apply it to specs I was editing
#
tantek
to hopefully get some experience and help make it a real thing
#
jasnell
ok. the language I added basically says, (a) Yes, AS2 can contain private data, (b) implementations should openly document what private data they use and why and who they share that with, (c) implementations should limit what data they include in AS2 unless the user consents, (d) implementations should limit what data they store/share unless the user consents. But also indicate that "consent" can be implied if the use is publicly documented and
#
jasnell
obvious
#
jasnell
I could potentially include something in there about encryption but there are no really special ways to encrypt JSON other than the usual mechanisms
#
tantek
right - ok to say that e.g. AS2 does not specify anything about encryption.
#
jasnell
oh, I also went ahead and modified the date-time thing to make seconds optional
#
jasnell
ISO8601 allows for it, RFC3339 attempts to give a stricter profile. Allowing those to be optional shouldn't break anyone tho
#
ben_thatmustbeme
jasnell++ fast turn around on all of that
#
Loqi
jasnell has 39 karma
#
ben_thatmustbeme
don't you sleep ? :P
#
jasnell
once in a while
#
wilkie
maybe we'll need to action jasnell to take a nap
#
wilkie
I'm very glad zakim didn't actually parse that out
#
jasnell
I'm still sitting upright and have plenty of coffee, so I'm good for now
#
wilkie
I survived my redeye, and it is true to its name. though it was worth it and was nice seeing everybody.
#
wilkie
thanks again to everyone and tantek for hosting
the_frey and bengo joined the channel
#
tantek
you're welcome wilkie! glad you could make it.
bengo, the_frey, bblfish and shevski joined the channel