Re: Asynchronous decisions Re: Webex details for Process Task Force

On 2015-06-29 09:35, wrote:
> 26.06.2015, 03:24, "Michael Champion (MS OPEN TECH)" 
> <>:
>> > weekly Process Task Force,
>> I'd like to discuss whether the demise of Zakim is a good opportunity 
>> to retire this call and find a better way of collaborating on process 
>> revision.
>> The trend is to use GitHub to collaboratively edit specs and its 
>> issues tracker rather than unstructured email threads to resolve 
>> issues. I believe the Process CG and the AB task force should eat 
>> this dog food and get away from conference calls as its discussion 
>> and decision making mode.
> I believe there is a lot of value in using documents rather than 
> conference calls as a basis for decision-making instead of conference 
> calls.
> I don't find that github is terribly helpful for managing a document 
> with many proposals until the participants are highly proficient in 
> the use of it. I am not sure this high barrier to entry is typically 
> something that the people most concerned by W3C process have to meet 
> otherwise.
> If the people in this discussion, and the AC, are happy to use github 
> pull requests and issue lists to propose and discuss questions, I am 
> not opposed to that.
> But I am yet to see any real reason beyond "it's the shiny new tool" 
> why we should ask people to invest significant effort in learning it.

You could do it where you do the pull requests typically, but use the 
Issues to focus discussions.  That does make it easier to track the 
discussion and see the actual resolution in what changed in the document.

People who are tracking can "watch" the repository and get in in mail 
just like this mail list. The CG page can have a link to the GitHub 
Issues.  And the tracking tools being developed look pretty good.  I 
don't think it makes it harder to track.

>> Anyone disagree? assuming so, where do we have the conversation and 
>> resolve the issue?
> Demonstrate that the proposal has been widely reviewed by the relevant 
> stakeholders - i.e. people who participate in the discussion or who 
> need to be able to track it in order to make a decision on whether or 
> not to adopt a proposed change. I guess some of those people are in 
> this mailing list, some are in the AC, some are chairs, and perhaps 
> there are people who really care about W3C process in none of those for

Seems that's the people who are tracking this.  So, if someone doesn't 
like it they could say so here.  If they aren't tracking this list, it 
wouldn't impact them.

> cheers
> ------------------------------------------------------------------------
> From: Maria Auday <>
> Sent: ‎6/‎25/‎2015 2:58 PM
> To: <>
> Cc: Jeff Jaffe <>
> Subject: Webex details for Process Task Force
> Hello,
> Below are the Webex details for the weekly Process Task Force, 
> effective 30 June. Please let me know if you have any questions.
> Topic: Process Task Force
> Date: From Tuesday, June 30, 2015, to no end date
> Time: 10:00 am, Eastern Daylight Time (New York, GMT-04:00)
> Dial-in: +1-617-324-0000
> Access code: 641 501 274
> Meeting number: 641 501 274
> Meeting password: process
> Host key: 628756
> Regards,
> Maria
> ---
> Maria Auday
> Executive Assistant to Dr. Jeffrey Jaffe, CEO
> W3C, World Wide Web Consortium at MIT
> Phone: +1.617.324.0368
> <>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> - - - Find more at

Received on Monday, 29 June 2015 16:48:32 UTC