See also: IRC log
<trackbot> Date: 05 May 2014
Notes that we could move the call to next week
virginie: looks like everything is happening on mailing list and bugzilla
I'm going to note that calls are useful mostly when they are controversial and we need to make a consensus decision
The two main feedbacks I saw were the further discussion of SAAG today
and the TAG feedback
markw: I agree, but most of the
changes are not breaking changes
... so we don't need to breaking changes
<scribe> scribe: hhalpin
hhalpin: We could do a more
WebApps-style
... more with ad-hoc calls, and we ask the mailing list when/if
they are necessary
virginie: I agree
<scribe> ACTION: hhalpin to email to mailing list over the Web Apps mailing list [recorded in http://www.w3.org/2014/05/05-crypto-minutes.html#action01]
<trackbot> Created ACTION-144 - Email to mailing list over the web apps mailing list [on Harry Halpin - due 2014-05-12].
virignie: two open parts of feedback, the feedback from IETF SAAG
markw: looking at the bugs that
have been raised
... no fundamental operations changes due to TAG
... just fixing mistakes and how its implemented
virginie: what do you think about last call for Key Discovery?
markw: I think those comments
from TAG apply to key discovery
... so then we'll take that to last call
virignie: dates from Sept 10-11th
location: Mountain View, Microsoft hosting
virginie: scope is under finalization
hhalpin: scope is still under
discussion, but I imagine things will be done by end of this
week
... and then we'll do an official announcement
... right now it's approved by W3C but not quite finalized
virginie: if anyone wants to join the program committee, can you say something?
<KarenLu> I have volunteered
excellent! I'll add you Karen
virginie: seems too early to talk
about TPAC
... any additional items to discuss?
... I'm concerned about ad-hoc calls
... but I'll see from mailing list
... but if you as participant wants to solve it with a live
discussion
PROPOSED RESOLUTION: Switch to working mode that features ad-hoc calls and a wait list
PROPOSED RESOUTION 1: Switch to working mode that keeps biweekly calls and a waiting period on the mailing list for objections to decisions
<terri> I'm sorry, I can't hear anything
PROPOSED RESOLUTION 2: Switch to a working mode that does only ad-hoc calls and a waiting period on the mailing list for objections to decisions
which one do people like?
biweekly vs. adhoc vs. keep things the same?
virginie: any preference?
notes that "keeping things the same" is (3)
<terri> 2
<virginie> 2
<drew> i'm ok with (2) but don't have a strong preference
yes, we can always change it
<KarenLu> 2
ok, then it looks like (2) wins
RESOLUTION: Switch to a working mode that does only ad-hoc calls and a waiting period on the mailing list for objections to decisions
<markw> ok with me
proposal for mailing list is for 10 day period
virginie: I'd like for people to
know we're relying on working group members to notify me when
they need a call
... this means we won't have a call in 2 weeks
... any other items to addressed?
Meeting adjourned
trackbot, end meeting
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: harry Found Scribe: hhalpin Default Present: +1.512.257.aaaa, drew, virginie, +1.617.253.aabb, jyates, markw, Karen, hhalpin, terri Present: +1.512.257.aaaa drew virginie +1.617.253.aabb jyates markw Karen hhalpin terri Found Date: 05 May 2014 Guessing minutes URL: http://www.w3.org/2014/05/05-crypto-minutes.html People with action items: hhalpin[End of scribe.perl diagnostic output]