m&mI know there were items added to the council agenda, but I couldn't be present, and I haven't noticed minutes yet
stpeterhmm
stpeteryeah
stpeteranyway, to the PRs?
m&mPR 40 is waiting on authors
m&mPR 41 is waiting on council, AFAIK
stpeterI have some Yokohama prep to do too - not sure why, but I volunteered to help finish off the trickle-ICE spec (cf. XEP-0176) so I need to create a presentation for that
stpeterand I have a few specs in AUTH48 ;-)
m&mremote presentation? (-:
m&mI think PR 82 is waiting on the submitter, but I'll ping the authors to be sure
m&mwait, no, it's waiting on authors
m&mPR 83 is waiting on … somebody (-:
m&mI think Sam and Matt Wild have the ideas in their head, and haven't yet put them to digital pen
stpeternod
stpeterI still haven't gotten to the XEP-0198 stuff as you can see :(
m&myeah
m&mit happens
m&mPR 95 — I'm not sure what the action here is
m&mis it to council?
stpeterI'm trying to finish this AUTH48 stuff and also update 2 Internet-Drafts for Monday....
stpeterlooks
stpeterI think the action there is to ask sco0ter to remove the status 174 stuff and then we can merge the PR
stpeterbecause all the other fixes were fine
stpeterand then a point release IMHO
m&mok
stpeterI can reply in that issue
stpeterdone
m&mthanks
m&mPR 97 is another XEP-0198 item
stpeteryep
m&mPR 99 — I might just accept this as-is … it would be nicer if I could see it run cross-platform, but that's more effort than I'm willing to put into it
m&mthere are conflicts that need to be resolved, though
stpeternod
m&mPR 100 went to council, no?
stpeterPR 100 - see http://logs.xmpp.org/council/2015-10-21/#15:07:32
stpeterso basically it needs more list discussion
m&myep, see that
stpeterit = XEP-0138 and the impact of attacks on application-layer compression in XMPP
m&mright
stpeter(not just this PR)
m&mok, so we'll need to get that going at some point
m&mwe == (XEP Editor, Kev)
m&msomeone in that set (-:
stpeterwe had a thread earlier this month about deprecating stream compression but it fizzled out
stpeterI will reply to the last message from Thijs
m&myeah, I vaguely remember
m&mPR 104 is still rippling through the list
m&mNot sure if we should "call it" and let the council formally weigh in
m&mI have a sense meaningful discussion is no longer happening
stpeternod
stpeterI do think some guidance from the Council would be good there
m&mbetter to wait for next council though
stpetertrue
stpeterwell, maybe
stpeterdoesn't necessarily matter, I guess :-)
m&mI'd rather not be in the middle of a vote when a new council is elected … even if it's really ends up as the same council (-:
stpetergood point
stpeterPR 106 - I have not looked at that yet
m&mI think we're waiting for someone to take it to the list
stpetersays "Needs Author" too ;-)
m&mvery true (-:
m&mthat's kind of my default labels on Draft and Final docs
m&mif something isn't clearly just editorial
stpeteryeah
stpetergood plan
m&mProtoXEP!
m&mPR 111 I can get processed today
m&mSame with PR 112
stpeterok super
m&mAnd PR 113 is a simple editorial
m&mI'll get those last three processed, and publish XEP-0320 as 1.9
stpeterre #112 I've had some chats with Lance / @legastero about encrypted file transfer and I know someone else who's put a fair amount of thought into it, so I look forward to list discussion
m&mer 1.0
m&m(-:
stpeter;-)
SamWhitedRE 83: I'm going to just close it since it was deemed not the correct behavior. I really do need to sit down and do a new update.
m&mah, ok
m&mthanks Sam
stpeterhey Sam, OK
m&mI think that's it
stpeteranything needing attention in the issues? https://github.com/xsf/xeps/issues
stpeterI'm on the hook for some PRs there
m&mat this point, all the actions there are for someone to update or write a doc
stpeteryes
m&mnon-trivial updates at that
stpetersome of 'em, yeah
stpeterI'll deal with active PRs first, methinks
m&mright
stpeterso we're done in half an hour!
stpetergood job, team!
m&mamazing (-:
SamWhitedRebased 99 on master
stpetergold star for the day!
stpeterI have yet to grok rebasing in fulness - I must dedicate some time to learning git more fully
m&mthanks Sam
SamWhitedGit is actually an incredibly simple system, which makes it nice to learn, but also means that it's way easier to learn on a whiteboard than at a computer.
SamWhitedWhat happened to the attachto XEP I submitted? Looks like the council voted to accept as Experimental last wednesday. Did that fall through the cracks?
m&min so much as Kev hasn't pushed out minutes, and I could not attend the last Council meeting
SamWhitedAh, no minutes. That'll do it.
m&mwell, there's minutes *now" *(-:
m&mwe'll get that published as 0.1 presently
SamWhitedSame with entity versioning actually, that was a while back. I think one or two people were to vote "on list" but it's probably been longer than the two weeks or whatever it is. I should go check on that.
m&moh, wait … can't yet … waiting on Dave
KevSorry, just saw a highlight. What's up?
m&mI have to poke Council again about entityversioning
m&mI was just waiting on minutes
m&mso issue resolved
KevAh. Perfect timing, then.
SamWhitedOh yah, there they are... good timing.
m&mwe do have some protoXEPs that might have fallen through the cracks … will gather up the list and let you know, Kev
SamWhitedMaybe council should file an issue after they have a vote so we can track the actual task of doing whatever the thing is alongside PR's and what not.
SamWhitedVote in the MUC or on-list or in some non-third-party place, but track all work on GitHub.
m&mthat's a good idea, but something for the Editor team to do
m&mtechnically the Editor is responsible for tracking votes
SamWhitedmakes sense
SamWhitedI'll start just doing that if I'm watching a council meeting and a vote happens. See if the workflow feels good.
KevI suggest that Editors think about what they'd like, and talk to the new Council Chair about it when the guard changes.
stpeterrightio
stpeterI have, in the past for another board I was running, used GitHub for creating meeting agendas but not yet for tracking votes - I somewhat like the idea of having everything in one place (although the XEPs repo might not be that place, at least for Council business - setting up a separate Council repo could work, though) ... but, as Kev says, that's something for the next Council to ponder
KevIf it was me, I'd be more inclined to use Trello for this, but whatever, it won't be me :)
SamWhitedI was thinking more tracking of the actual work. So council would vote in the normal way, but then file an issue to tell the editors "merge and mark this XEP as experimental" or whatever the task is.
KevI think that's traditionally been the Editor's job.
SamWhitedYah, less benefit if the editors are doing it (because then if minutes are late or something there's a delay), but it doesn't really matter. Mainly just having a tracking issue which, if the editor who was going to do something goes on vacation, can be looked at by others so things don't fall through the cracks.