#aaronpkeprodrom: 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
#aaronpksandro: 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"
#aaronpkkevinmarks_: if we're going to discuss the process, it would be good to constrain each issue to a single issue
#rhiaroq+ 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.
#Zakimrhiaro, 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.
#tantekq+ 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.
#aaronpkArnaud: 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
#Zakimtantek, 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
#aaronpktantek: 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
#aaronpksandro: we talked also about labels in the titles like "blocking"
#cwebber2I added an item to the wiki as a possible thing to discuss, if we have extra time
#aaronpkbengo: 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
#aaronpksandro: how about the social web protocols document
#aaronpkcwebber2: we also have the mailing list and telcons
#aaronpktantek: 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
#aaronpkcwebber2: 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
#aaronpktantek: 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
#aaronpktantek: 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?
#aaronpkArnaud: 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
#aaronpktantek: 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
#aaronpkrhiaro: 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?
#aaronpktantek: 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... 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
#ZakimAs of this point the attendees have been Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme, cwebber,
#RRSAgentACTION: 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]
#jasnelltantek: 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
#jasnellI hadn't seen that previously but will go through it
#tantekRight now the AB etc are evaluating the questionnaire and looking for feedback for spec inclusion
#tantekso I of course decided to dogfood it and apply it to specs I was editing
#tantekto hopefully get some experience and help make it a real thing
#jasnellok. 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
#jasnellI could potentially include something in there about encryption but there are no really special ways to encrypt JSON other than the usual mechanisms
#tantekright - ok to say that e.g. AS2 does not specify anything about encryption.
#jasnelloh, I also went ahead and modified the date-time thing to make seconds optional
#jasnellISO8601 allows for it, RFC3339 attempts to give a stricter profile. Allowing those to be optional shouldn't break anyone tho