W3C home > Mailing lists > Public > public-w3process@w3.org > March 2015

Re: When to close a Working Group?

From: David Singer <singer@apple.com>
Date: Tue, 10 Mar 2015 17:03:37 -0700
Cc: Revising W3C Process Community Group <public-w3process@w3.org>
Message-id: <DD126CF4-7928-42D3-8FC4-9CA0BB43DE21@apple.com>
To: Harry Halpin <hhalpin@w3.org>
Hi Harry

I think that we expect that the team will notice, and start pulling in the AC reps who are involved, and so on.  When it comes down to it, if it goes dormant and then is not re-chartered, that’s probably the easiest.

Like Michael, I wonder if you can give some examples, but I realize this sensitive.  Historical examples might be better.

> On Mar 10, 2015, at 15:08 , Harry Halpin <hhalpin@w3.org> wrote:
> 
> I'd like to bring up what I think is an open issue: How do we close a
> chartered Working Group when its clearly gone off the rails and won't
> produce a useful standard?
> 
> For example, a Working Group could be chartered with lots of member
> support, but later the members withdraw or don't implement. This sort of
> Working Group seems to be a waste of W3C member resources. However, it
> seems unclear how to actually end a Working Group.
> 
> My preference would be that there could be an internal review by W3C if
> there is a motion by members, staff, or chairs to close the WG, and if
> the W3C review shows that the worries are justified even if the WG is
> chartered, then a vote goes to the AC to close the WG. All existing
> rec-track docs then transform to WG Notes before closure.
> 
>   cheers,
>      harry
> 

David Singer
Manager, Software Standards, Apple Inc.
Received on Wednesday, 11 March 2015 00:04:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 March 2015 00:04:26 UTC