15:20:49 RRSAgent has joined #w3process 15:20:50 logging to http://www.w3.org/2015/02/24-w3process-irc 15:20:57 zakim, code? 15:20:57 sorry, jeff, I don't know what conference this is 15:21:02 zakim, this is process 15:21:02 ok, jeff; that matches AB_(PROCESS)10:00AM 15:21:09 zakim, who is here? 15:21:09 On the phone I see SteveZ, Jeff, Mike_Champion, [IPcaller] 15:21:11 On IRC I see RRSAgent, Zakim, jeff, chaals, mdjp, timeless, cwilso, trackbot 15:21:14 zakim, [ip is me 15:21:14 +chaals; got it 15:21:33 jeff: What in the world might we do in Process2016? 15:21:39 ...anything worthwhile? 15:22:10 ... I don't know anything important enough to pass muster; to make it worthwhile to do a rev of the process; except for possibly CGs. 15:22:26 ... but I can't get my head around what we would actually say in the process about something which is not part of the process 15:22:48 Mike: We might introduce some new process to characterize how some CGs exist in an orbit around WGs 15:23:03 ... and what might IP commitment transitions look like 15:23:21 All: But really it is Chaals who knows most about what should go into the process. 15:24:07 RRSAgent, draft minutes 15:24:07 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 15:24:17 RRSAgent, make logs world 15:24:19 RRSAgent, draft minutes 15:24:19 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 15:24:21 Steve: What are the 4-5 items you want to see in the Process2015 draft for the AC 15:24:30 ..., chaals? 15:24:58 Chaals: (1) Resigning from WG, (2) knowing if a WG has closed 15:25:18 ... (3) significant proposal for TAG 15:25:20 meeting: Revising W3C Process Community Group Teleconference 15:25:27 ... as an AC rep I will object to current draft 15:25:41 ... (4) Understand a WG decision (e.g. what the Chairs announce) 15:26:05 Steve: I believe that the text for solving the default channel has reached consensus 15:26:15 Chaals: Consensus, but no resolution. 15:26:55 RRSAgent, draft minutes 15:26:55 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 15:26:57 q+ 15:27:23 ... I don't like the proposal of a default approach. Singer liked my approach. 15:27:44 i/might we do in Process2016?/Topic: Process 2016 tasks/ 15:27:50 Steve: Singer was supportive that the announcement said where it was going. 15:29:50 ack je 15:30:17 Jeff: Suggest not having lots of open issues. 15:30:26 Steve: Resigning: we can solve with simple text which proposed how one resigns. 15:30:37 ... resign before Process2015 goes out. 15:31:18 ... Knowing if a WG has closed should go off to Process2016 15:31:37 Chaals: I understand that things not resolved will (unfortunately) go into 2016. 15:32:12 Steve: TAG objection (two things from same organization) would not be in AC cover letter; Chaals will just object 15:32:43 +??P0 15:32:56 Chaals: Defining a WG decision is for Process2016 15:32:58 Zakim, ??p0 is me 15:32:58 +timeless; got it 15:33:41 Mike: Isn't resign from a WG when you click the button to resign? 15:33:48 Chaals: Doesn't say so in the process. 15:33:52 ... should be easy to add 15:33:57 ... I will happily do so. 15:34:06 Mike: Making formal what is apparently the case 15:34:09 ... +1 15:34:31 scribe: timeless 15:34:36 Zakim, mute me 15:34:36 timeless should now be muted 15:34:45 issue-151? 15:34:45 issue-151 -- How to resign from a working group -- raised 15:34:45 http://www.w3.org/community/w3process/track/issues/151 15:34:48 Proposed: 15:34:48 15:34:48 "On written notification from an AC rep or invited expert, or equivalent action to formally leave the WG (e.g. through an automated join/leave system), the member's representatives will be deemed to have resigned from the relevant Group, effective immediately". 15:35:43 chaals: you should be able to write the team contact 15:35:51 ... saying you are resigning effective immediately 15:36:02 Mike: why not mention the form 15:36:12 chaals: if you tie the process to a thing that might go away 15:36:15 ... things could break 15:36:34 jeff: i think the team may establish additional details of how you do that 15:36:41 ... maybe it should just say notify the team? 15:36:47 s/jeff:/stevez:/ 15:36:47 s/jeff/steve/ 15:37:00 s/steve/jeff/ 15:37:08 ... "person resigns by written notification to the team" 15:37:17 chaals: i'll add "to the team" to the proposed text 15:37:33 jeff: i don't care how many ways you can resign 15:37:43 ... you say "on written notification from an AC rep or IE" 15:37:51 ... it doesn't say that the IE will have resigned 15:38:09 q+ to ask if a Member wants a rep but not all Reps for a Member to resign... 15:38:12 chaals: noted 15:38:19 Zakim, ack me 15:38:19 unmuting timeless 15:38:20 timeless, you wanted to ask if a Member wants a rep but not all Reps for a Member to resign... 15:38:20 I see no one on the speaker queue 15:38:30 Proposed: 15:38:30 15:38:30 "On written notification from an AC rep or invited expert to the Team, or equivalent action to formally leave the WG (e.g. through an automated join/leave system), the member's representatives or invited expert will be deemed to have resigned from the relevant Group, effective immediately". 15:39:33 chaals: resignation only applies to Member Entities, not representatives 15:39:48 steve: if a member resigns, then all reps of the WG are deemed to have resigned 15:39:59 chaals: members can remove all reps but retain membership 15:40:07 mike: from the patent purpose, that matters 15:40:19 steve: that's why we want to fix this 15:40:30 jeff: if it's possible for a Member to be in a WG even if it has no Reps 15:40:40 ... then i'm concerned about "equivalent actions to leave the working group" 15:40:54 ... it could be interpreted that going from X reps to 0 reps would be leaving 15:41:08 chaals: then you should instruct systems to ... 15:41:32 jeff: the proposed resolution 15:41:42 ... doesn't tie leaving the WG to the system 15:41:53 ... it ties any action that's equivalent, and that isn't defined 15:42:07 ... if the resolution ties to the existing system only, i think we're ok 15:42:15 steve: why do we need the equivalent action clause? 15:42:27 ... seems like the easiest way to fix this is to remove the equivalent action clause 15:42:47 chaals: it's pretty trivial to have a button saying "i'm taking all members out and leaving the WG" 15:43:06 mike: one employee in WG, employee leaves company, you're still in WG w/ no reps 15:43:31 jeff: company later could say "we had one person in WG, he left company, therefore we had 0 people in WG, by his leaving company, we took equivalent action" 15:43:34 mike: i agree 15:43:48 ... i'm happy having the process document saying exactly what happens in WBS 15:43:57 ... not worrying about corner case of deadline + WBS is down 15:44:04 ... we've gone 20 years w/o worrying about it 15:44:19 chaals: i've been impacted which is why i'm worried 15:44:25 mike: let's not have a vague action 15:44:39 jeff: "written notification to the team" 15:44:47 mike: "electronic means written" 15:44:55 jeff: we don't need to put that into the process 15:44:59 Zakim, mute me 15:44:59 timeless should now be muted 15:45:06 s/jeff:/steve:/ 15:45:20 steve: "using the form is accepted as written notification" 15:45:27 jeff: that works for me 15:45:54 chaals: seems backwards, but i probably would not object 15:46:09 steve: a lot of places accept electronic statements as "written notification" 15:46:15 chaals: you'd be defining "the form"? 15:46:25 steve: we leave a lot of things to implementation 15:46:45 chaals: i've lost the proposal 15:46:52 steve: drop the "or equivalent 15:47:24 Proposed: 15:47:24 15:47:24 "On written notification from an AC rep or invited expert, the member's representatives or invited expert will be deemed to have resigned from the relevant Group, effective immediately". 15:47:49 Proposed: 15:47:50 15:47:50 "On written notification from an AC rep or invited expert, or equivalent action to formally leave the WG (e.g. through an automated join/leave system), the member and their representatives will be deemed to have resigned from the relevant Group". 15:48:07 jeff: "effective immediately" is probably redundant, you could probably shorten it a bit 15:48:18 ... you just put equivalent action back in 15:48:22 chaals: copy-paste errors 15:48:40 Proposed: 15:48:40 15:48:40 "On written notification from an AC rep or invited expert the member and their representatives or invited expert will be deemed to have resigned from the relevant Group". 15:48:58 Zakim, unmute me 15:48:58 timeless should no longer be muted 15:49:28 timeless: wondering if their reps or _the_ IE ... 15:49:43 jeff: makes sense 15:50:57 [ Chaals reads a version w/ "the" as suggested by timeless ] 15:51:08 steve: any objections? 15:51:12 [ None ] 15:51:20 RESOLUTION: Add "On written notification from an AC rep or invited expert the member and their representatives or the invited expert will be deemed to have resigned from the relevant Group". 15:51:30 steve: default channel 15:51:34 ... edited rec 15:51:36 ... that one 15:51:42 ... those are the only changes 15:51:55 chaals: steve when you get back on line, can you send a formal resolution for the default one? 15:52:02 steve: i'll issue a response to the CfC 15:52:10 RRSAgent, draft minutes 15:52:10 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 15:52:19 topic: ISSUE-152 15:52:34 issue-152? 15:52:34 issue-152 -- Process2014 Regresses Editorial Revision of RECs -- open 15:52:34 http://www.w3.org/community/w3process/track/issues/152 15:52:48 steve: are we trying to solve a case that has never occurred in practice? 15:53:04 ... i conjectured that we've never done an Edited REC for solely Editorial changes 15:53:09 chaals: i suggest you're wrong 15:53:14 ... I believe RDFa is doing that 15:53:36 steve: i discussed w/ jeff -- tantek's proposal 15:53:50 ... and noted your (chaals's) slippery slope warning 15:53:58 ... on circle/oval 15:54:09 mike: i remember the discussion in tokyo that changed my mind 15:54:21 ... the PAG example that was resolved by changing the name of something 15:54:31 ... one would think that changing a name would be editorial 15:54:36 ... but we have an example where it isn't 15:54:40 ... i've changed my mind on this 15:54:49 ... we have to tell fantasai that it's deliberate 15:54:59 ... there's no way to define an editorial change that doesn't have patent implication 15:55:08 steve: i can draft text for a note to go in 15:55:41 ... that was the one issue that the AB asked be explicitly noted 15:56:02 RRSAgent, draft minutes 15:56:02 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 15:56:12 steve: i believe we have marching orders for the document going to AC 15:56:19 ... we have updates on default channels + resigning 15:56:30 ... and a note on not resolved for Edited REC 15:56:38 ... those are the only proposed changes going into 2015 15:56:47 ... the other issues are separate and likely to be 2016 issues 15:57:06 ... i'll draft a note this weekend or before for a letter to the AC for a 4 week review of the proposed 2015 document 15:57:23 chaals: i'd request that you draft some explicit explanation of the Edited REC issue 15:57:29 steve: yes 15:57:40 jeff: i think in your letter you should include the entire schedule going forward 15:57:51 ... 4 week review, review comments to TF in April timeframe 15:58:00 ... TF expects to turn around comments in April 15:58:10 ... TF expects to get out final in time for AC meeting 15:58:17 steve: that's my understanding, yes 15:58:28 ... i agree it should be in there 15:58:38 jeff: in the March 16 AB call 15:58:46 ... i'm thinking to put on the agenda the question 15:59:02 ... of whether there are sufficiently big further changes that we want to have a Process 2016 focus 15:59:13 ... steve, if i have such an Agendum, would you like to join the AB meeting 15:59:16 steve: yeah 15:59:24 jeff: question for everyone, i could tee up that item 15:59:32 ... or if someone else wants to take it up 15:59:51 steve: i sent 2 lists to the AB+public-xxx prior to the Tokyo AB meeting 16:00:00 ... (1) the list of still open issues (potentially 2016) 16:00:10 ... (2) list of things i didn't think we part of the process 16:00:18 ... slightly less than a week before the Tokyo meeting 16:00:30 ... we didn't have time to discuss that list 16:00:38 ... but it could be helpful for March 16:00:41 jeff: sure 16:00:49 ... i'm not trying to collate the potential issues 16:01:02 ... trying to argue that to make the investment, there has to be something big 16:01:11 ... CGs look promising, but we'd have to figure out what to say 16:01:26 steve: the list is a set of topics that are potentially big issues 16:01:34 ... certainly the "is new charter a new WG" is a big issue 16:01:44 jeff: a bunch of issues that PSIG have told us to stay clear of them 16:02:01 ... i don't want to have Process 2016 just to go around in circles that won't conclude 16:02:10 ... specifically don't want those 16:02:19 steve: i think there are things worth doing 16:02:28 jeff: if chaals / mike have framing for CG thing 16:02:33 steve: thanks everyone 16:02:44 i/thanks/topic: Conluding 16:02:50 -chaals 16:02:54 ... i'll get the email out by Sunday 16:02:54 -Mike_Champion 16:03:15 RRSAgent, draft minutes 16:03:15 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:03:15 -Jeff 16:03:28 -SteveZ 16:03:41 i/might we do in Process2016/scribe: jeff/ 16:03:50 RRSAgent, draft minutes 16:03:50 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:05:24 i/button to resign/topic: Members and IEs Resigning from WGs 16:06:38 s/jeffz/stevez/ 16:07:08 RRSAgent, draft minutes 16:07:08 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:08:10 s/topic: ISSUE-152/topic: ISSUE-152 Process2014 Regresses Editorial Revision of RECs 16:08:28 disconnecting the lone participant, timeless, in AB_(PROCESS)10:00AM 16:08:29 AB_(PROCESS)10:00AM has ended 16:08:29 Attendees were SteveZ, Jeff, Mike_Champion, [IPcaller], chaals, timeless 16:09:02 i/steve: default channel/topic: Noted changes for next AB Meeting/ 16:09:55 i/we have marching orders/topic: Plan of Action/ 16:10:10 RRSAgent, draft minutes 16:10:10 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:10:40 [ Adjourned ] 16:15:40 ok 16:15:43 s/ok// 16:17:46 s/for next AB Meeting/to be addressed in Process2015 prior to sending outo for AC review 16:17:51 RRSAgent, draft minutes 16:17:51 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:25:27 chair: Steve 16:25:36 s/[IPcaller], // 16:26:06 RRSAgent: 16:26:06 I'm logging. I don't understand '', timeless. Try /msg RRSAgent help 16:26:15 RRSAgent, draft minutes 16:26:15 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:26:32 s/RRSAgent:// 16:27:01 s/stevez:/SteveZ:/ 16:27:05 s/steve:/SteveZ:/g 16:27:07 RRSAgent, draft minutes 16:27:07 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:28:03 s/outo/out/ 16:28:04 RRSAgent, draft minutes 16:28:04 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html timeless 16:28:27 trackbot, end meeting 16:28:27 Zakim, list attendees 16:28:27 sorry, trackbot, I don't know what conference this is 16:28:35 RRSAgent, please draft minutes 16:28:35 I have made the request to generate http://www.w3.org/2015/02/24-w3process-minutes.html trackbot 16:28:36 RRSAgent, bye 16:28:36 I see no action items