13:56:57 RRSAgent has joined #w3process 13:56:57 logging to http://www.w3.org/2015/04/28-w3process-irc 13:56:59 RRSAgent, make logs public 13:56:59 Zakim has joined #w3process 13:57:01 Zakim, this will be Process 13:57:01 ok, trackbot; I see AB_(PROCESS)10:00AM scheduled to start in 3 minutes 13:57:02 Meeting: Revising W3C Process Community Group Teleconference 13:57:02 Date: 28 April 2015 13:58:18 AB_(PROCESS)10:00AM has now started 13:58:25 +SteveZ 13:58:48 zakim, code? 13:58:48 the conference code is 7762 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), chaals 13:59:29 +[IPcaller] 13:59:43 zakim, [i is me 13:59:43 +chaals; got it 14:00:48 agenda; https://lists.w3.org/Archives/Public/public-w3process/2015Apr/0131.html 14:01:17 rrsagent, agenda: https://lists.w3.org/Archives/Public/public-w3process/2015Apr/0131.html 14:01:17 I'm logging. I don't understand 'agenda: https://lists.w3.org/Archives/Public/public-w3process/2015Apr/0131.html', SteveZ. Try /msg RRSAgent help 14:01:51 s/agenda;/agenda:/ 14:01:52 +??P4 14:02:10 Chair: SteveZ 14:02:25 jeff has joined #w3process 14:02:39 +Jeff 14:03:10 Zakim, ??p4 is me 14:03:10 +timeless; got it 14:03:36 rrsagent, make minutes 14:03:36 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html SteveZ 14:03:54 RRSAgent, make logs world 14:03:59 RRSAgent, draft minutes 14:03:59 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:04:35 scribe: timeless 14:04:40 topic: review letter 14:04:49 jeff: in the draft ac memo that SteveZ sent 14:05:03 ... to a non public list 14:05:06 +[Microsoft] 14:05:17 ... no mention was made of a formal object 14:05:24 s/object/objection/ 14:05:43 SteveZ: i was unclear whether a formal objection was formally delivered, 14:05:56 Zakim, who is on the call? 14:05:56 On the phone I see SteveZ, chaals, timeless, Jeff, [Microsoft] 14:06:12 Zakim, [m is Mike_Champion 14:06:12 +Mike_Champion; got it 14:06:31 chaals: in all likelihood, there will be a formal objection when there is a formal review 14:06:50 jeff: the question is whether there should be a reference to it in the letter starting the final review 14:07:00 chaals: that seems like the logical thing to do 14:07:10 mike: i think it's useful information to the voters 14:07:26 SteveZ: i can point to the message that chaals sent indicating the objection 14:07:42 jeff: we need to have the url to the document in the memo to the AC 14:07:55 ... is the final one we're sending to the AC, the one we sent to the AB on the 24th of April? 14:08:08 SteveZ: last time we created a Proposed Process Document (possibly Ralph did it?) 14:08:14 ... it was located somewhere else 14:08:56 jeff: last time we said the editor was chaals and the previous editor was IanJ 14:09:03 ... do we leave it that way? 14:09:08 chaals: i think we leave it that way 14:09:21 ... the general convention is to give credit to people who in the past have been editing 14:09:46 SteveZ: the document that went out for review was in /TR/ space 14:09:55 chaals: if you want it in dated space, then you need a Staff member to do that 14:10:20 SteveZ: someone also has to create the WBS (survey) 14:10:25 glazou has joined #w3process 14:10:29 sorry for being late 14:10:45 ... last time the document had gone out for LC review, i didn't include that either, i can include it 14:10:52 jeff: i need to know what i'm doing, and what you're doing 14:10:59 ... i'm getting on a plane tomorrow morning 14:11:06 SteveZ: it seems like koalie sends it out 14:11:25 jeff: do we need to include the DoC pointer here? 14:11:30 SteveZ: i don't know 14:11:38 ... there wasn't one in the one that went out for 2014 14:11:54 jeff: fair enough 14:12:08 SteveZ: i'll update it w/ the two changes (ref to formal objection, + ref to LC review) 14:12:19 ... i'll send it to the TF first, so someone w/ a comment can send it quickly 14:12:35 ... creating a document in dated space, and sending an announcement are the things to do 14:12:41 jeff: i can take care of the Team things 14:12:49 ... you can tell me what you want to put in the actual memo 14:12:52 RRSAgent, draft minutes 14:12:52 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:13:20 SteveZ: the 2014 announcement had a pointer to the document, a statement about changes, a WBS, and a deadline 14:13:28 ... we should decide on the deadline... 14:13:32 ... 4 weeks, right? 14:13:42 chaals: this is a formal AC review, it gets 4 weeks 14:13:59 jeff: it would be worthwhile to state there will be an opportunity for questions/discussion at the AC meeting 14:14:24 SteveZ: i can do those things, and send it to you (+TF) 14:14:34 ... the only difference w/ what i sent to jeff, 14:14:50 ... i included a summary of the changes -- from chaals 's document 14:14:57 ... structural changes, major changes 14:15:03 jeff: did we fix the Errata thing? 14:15:06 SteveZ: yep 14:15:10 jeff: which change is that? 14:15:17 SteveZ: it's in chaals 's list 14:15:37 ... under editorial changes, clarify language of 7.7.1 to encourage groups to be responsive 14:15:55 jeff: didn't we also provide some mechanism so Errata didn't have to be on a separate page? 14:16:13 SteveZ: chaals listed it in his changes as an editorial change 14:16:22 jeff: i thought it was important 14:16:25 timeless: +1 14:16:38 jeff: it doesn't just clarify the language, it allows for a different approach 14:16:41 SteveZ: i'll fix that too 14:18:05 SteveZ: those are the major changes, i think that's all that we need to discuss on the document 14:18:27 RRSAgent, draft minutes 14:18:27 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:18:56 topic: Review Open Action Items 14:19:01 SteveZ: i don't think there are any actions to review 14:19:06 topic: Express thanks to all those that contributed to shaping Process 2015 14:19:12 SteveZ: so 14:19:24 TOPIC: 2. Express thanks 14:19:36 s/TOPIC: 2. Express thanks// 14:19:47 SteveZ+++ 14:19:50 Chaals+++ 14:20:02 Timeless+++ 14:20:02 SteveZ: i wanted to formally express my thanks for all of you who helped put the document together 14:20:08 Mike+++ 14:20:12 ... and i know that Josh wasn't at the AB meeting 14:20:12 Everyone else+++ 14:20:17 ... so i wanted to thank you as well 14:20:24 ... for helping make this possible 14:21:06 i|SteveZ: so|-> https://www.w3.org/2015/04/20-ab-minutes.html#item04 Thanks to Process TF for work on Process 2015| 14:21:14 topic: CGs 14:21:30 SteveZ: having CGs have a better documented role in creating Docs/Charters 14:21:45 ... what kinds of guarantees/rights do CG members have? 14:21:54 ... i think Mike said don't add any 14:22:06 ... we don't necessarily need to fix that now, but i think we should raise that to the AC audience 14:22:20 ... there was a separate discussion on the Process vs. the Guide 14:22:54 ... to me, the Process is as short as possible for Rules/Rights -- who participates, how, how work gets done, what's guaranteed to them 14:22:59 ... everything else can go in the Guide 14:23:08 ... i think there was agreement on the ML that 14:23:14 ... something like the Guide would be useful 14:23:29 ... ArtB suggested transferring the Guide to github 14:23:33 W3C's community's reaction to the discussion of the Guide --> http://w3cmemes.tumblr.com/image/117552201652 14:23:46 ... i proposed a Wiki because i like the way Wikipedia works 14:23:46 ,:-) 14:23:59 ... I guess github works similarly, that you can get notification on changes to a section 14:24:10 ... i'd be interested in whether people think it's practical/good 14:24:32 mike: it's kind of a necessity that whatever this is called, that it isn't maintained by the Team 14:24:37 ... it's a community effort 14:24:49 ... how this is developed should be a template for how things develop at W3C 14:25:00 ... it seems Github is the more powerful/futureproof way than Wiki 14:25:06 ... as for where it's administered from 14:25:13 ... if we're talking about a Template for the Future 14:25:24 ... covering CGs and getting Reviews before it goes off for Approval 14:25:30 ... more and more work is being done in Github 14:25:42 ... people contribute Pull Requests (PRs) with their suggestions 14:25:56 ... my hypothesis is that it will be more productive than doing things on MLs 14:26:03 ... and appointing an Editor to come up w/ words 14:26:18 ... i'd vote for... i don't care what CG is nominally administering it 14:26:30 q+ to talk about leadership 14:26:33 ... as long as it's crowd-sourced and the best ideas get traction 14:26:40 SteveZ: there are some complications 14:26:56 ... implementing some of these things requires the Systems Team and Communications provide some support 14:27:06 ... there's a need for process for some resources to be provided 14:27:23 mike: that's why i like the idea of non normative stuff being in the Process document 14:27:33 ... i respect your opinion that the process document being minimal 14:27:45 ... w/o some process for the Best Practices, it just becomes a collection of random thoughts 14:28:17 ... it seems to me that keeping this in the Process makes sense, but i could be convinced otherwise 14:28:30 jeff: i don't care where it lives, it makes sense to me that it be crowd-sourced 14:28:38 ... we should think about who the leader should be for this effort 14:28:50 ... i'd be happy if koalie could do it, i haven't asked her, but she could be busy 14:29:18 SteveZ: it's partly a W3M question about how they'd manage it 14:29:32 jeff: from Team, it'd go to the head of Comm, which is why I mentioned koalie 14:29:47 ... if we don't have the bandwidth, then we should step aside and let someone else take it over 14:30:10 SteveZ: i'm not proposing an idea, but perhaps things to talk about at the AC 14:30:16 ... we have a panel session 14:30:36 ... this is one of the pieces that came out of the recent after discussion 14:30:54 ... another was fixing the appeals process (probably less controversial) 14:31:07 ... then, the question about Member-Group participants 14:31:20 ... -- a separate for ones that are Org vs. Individual 14:31:39 ... allowing 4 individuals to participate freely is different than allowing for Orgs to participate freely 14:31:47 ... then, voting... 14:32:03 ... i was counting on Mike and Ramen to talk about CGs and Getting Started 14:32:08 ... for chaals to talk about Voting 14:32:21 jeff: Ramen has asked that he be replaced on the panel by cwilson 14:32:36 SteveZ: mike, you're on top of the CG thing 14:32:56 mike: to the extent that the Process document is a guide 14:33:14 ... i'd like it to talk about CGs about how they can contribute their work for standardization 14:33:26 ... along the lines of the Member contribution process 14:33:37 ... i'll provide some proposals for that 14:33:59 ... there's nothing that forbids CGs from sending a message to a WG to propose something for standardization by it 14:34:19 ... putting a defined contribution mechanism would allow us to not reinvent it each time some CG wants to do it 14:34:35 ... the Process document acknowledging the differences between CGs/WGs 14:34:48 SteveZ: Wayne had one on the relationships between CGs and WGs 14:34:59 ... i can represent it, and i know glazou had comments on it 14:35:08 mike: is wayne on the panel? 14:35:16 jeff: wayne did not want to be on the panel 14:35:27 mike: i largely agree w/ wayne, so i can represent his view 14:35:43 jeff: if there's anything w/ no strong advocate, we don't have to discuss it 14:35:54 ... it's a panel discussion, it's supposed to encourage discussion w/ the audience 14:36:00 q+ 14:36:02 ... we've seeded the discussion, Guide, Members, CGs 14:36:06 ... i don't want to over-manage it 14:36:21 ... it's supposed to be natural, if the AC wants to talk about something else, we'll do that 14:36:28 ... these are potentially filler points 14:36:38 SteveZ: sure, but at leas the ones on CGs would be useful to get out 14:36:53 ... 1. to remind Members that they exist and to make them more useful 14:37:23 SteveZ: so, we should put the CG items earlier 14:37:33 jeff: the passion on the panel will drive things 14:37:47 ... if no one on a panel is a spokesperson, you shouldn't be forced to speak for... 14:38:01 SteveZ: some i believe in, i'm not trying to be devil's advocate for the sake of being devil's advocate 14:38:03 jeff: ok 14:38:23 SteveZ: we don't have cwilson, but the rest of us, is there anything else we need to discuss about the panel? 14:38:44 i/talk about at the AC/Topic: Panel discussion at AC 14:38:51 -Mike_Champion 14:38:54 q? 14:38:58 q- jeff 14:39:01 ack glazou 14:39:01 ok 14:39:03 I want to say that I still think CGs will eventually be a threat to WGs because of their simplicity of launch, simplicity of operations and more (including github) ; it will become increasingly difficult to prevent them from doing spec work. Not a problem from my POV, but this has to be known/ack’d before making any choice here. 14:39:32 my choice is agility 14:39:37 whatever is agile 14:39:46 14:39:53 -chaals 14:40:02 SteveZ: i'll make the same comments in the discussion since i'm on the panel 14:40:10 s/i'll/glazou, i'll/ 14:40:14 RRSAgent, draft minutes 14:40:14 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:40:45 SteveZ: one note is the need to keep tracking multiple MLs 14:40:49 .. and that isn't very productive 14:41:02 ... maybe we just have to track one particular Github that has branches 14:41:06 s/.. and/ 14:41:07 q+ 14:41:52 timeless: branches on Github won't save you from drowniing 14:42:04 ... you'll end up getting lots of PRs for things you didn't care about 14:42:12 ... you'll have to pray that people have conventions to save you 14:42:16 s/niing/ning/ 14:42:26 SteveZ: "tell me all i want to know, not what happens" 14:42:29 timeless: right 14:42:33 [ Adjourned ] 14:42:38 RRSAgent, draft minutes 14:42:38 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:42:41 Thanks, all. 14:43:01 SteveZ: and thanks once again timeless 14:43:11 ... (see everyone else at the AC meeting) 14:43:19 timeless: y/w, and good luck all 14:43:24 sorry I joined late, was fixing an urgent crasher in some code to be released soon by a customer 14:43:27 s/[ Adjourned ]// 14:43:32 SteveZ: no meeting next week 14:43:38 -Jeff 14:43:39 [ Adjourned ] 14:44:08 glazou has left #w3process 14:44:08 -SteveZ 14:44:16 s/that isn't very productive/... and that isn't very productive/ 14:44:22 RRSAgent, draft minutes 14:44:22 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:45:21 s/topic: review letter/topic: Review letter announcing AC review of Process 2015/ 14:45:24 RRSAgent, draft minutes 14:45:24 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:46:10 trackbot, end meeting 14:46:10 Zakim, list attendees 14:46:10 As of this point the attendees have been SteveZ, [IPcaller], chaals, Jeff, timeless, [Microsoft], Mike_Champion 14:46:18 RRSAgent, please draft minutes 14:46:18 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html trackbot 14:46:19 RRSAgent, bye 14:46:19 I see no action items 14:46:33 RRSAgent has joined #w3process 14:46:33 logging to http://www.w3.org/2015/04/28-w3process-irc 14:46:38 RRSAgent, make logs world 14:46:44 s/[IPcaller], // 14:46:50 s/[Microsoft], // 14:47:27 regrets: dsinger 14:47:30 RRSAgent, make logs world 14:47:35 RRSAgent, draft minutes 14:47:35 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:47:57 present+ glazou 14:47:59 RRSAgent, draft minutes 14:47:59 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:48:18 RRSAgent, make minutes 14:48:18 I have made the request to generate http://www.w3.org/2015/04/28-w3process-minutes.html timeless 14:48:21 RRSAgent, bye 14:48:21 I see no action items