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

RE: When to close a Working Group?

From: Michael Champion (MS OPEN TECH) <Michael.Champion@microsoft.com>
Date: Tue, 10 Mar 2015 23:01:47 +0000
To: Harry Halpin <hhalpin@w3.org>, Revising W3C Process Community Group <public-w3process@w3.org>
Message-ID: <BLUPR03MB4889B0B8856DB624E3DFA6797180@BLUPR03MB488.namprd03.prod.outlook.com>
> How do we close a chartered Working Group when its clearly gone off the rails and won't produce a useful standard?

I'm sure it's a sensitive topic, but can you give some examples?  

The obvious way to close a chartered WG is to wait for its charter to expire and then not renew it.  I don't recall that happening very often.  The Web Services Architecture WG was one "success" story of the team and chairs deciding to pull the plug on an effort that wasn't on the road to success, but that was 10 years ago.  Also note that there is a current AC ballot open in which  someone :-)  formally objected to rechartering the WG until it shows it can reach the milestones identified in its existing charter. 

So, my immediate reaction is that this is a team problem: if a WG doesn't show progress, the team shouldn't devote resources to getting its charter extended or renewed. And arguably it's not fair to close a WG until it has had the time period identified in its charter to reach its objectives, so it's not clear that there needs to be a mechanism to shut down WGs before their charters run out. 

Another way to look at this: Let's think about how to not charter WGs until there is a spec with a community behind it plus some implementation plans by browsers, frameworks, or tools... and likely IP holders ready to make RF patent commitments. One way to do this would be to more strongly encourage potential WGs to incubate their spec in a Community Group to get at least an initial draft of a spec written down and socialized among implementers and users, and do a Final Specification Agreement to identify those who will make patent commitments.  In short, if we are more selective about chartering only WGs that already have draft specs and  viable communities behind them, we don't have to worry as much about pulling the plug on those that don't get real support.  

I haven't thought about this much, but perhaps there should also be a WG->CG transition mechanism so WGs that don't get members or implementers can easily reboot as CGs to give them a chance to refocus and demonstrate they're ready to get back on the Recommendation track.  

-----Original Message-----
From: Harry Halpin [mailto:hhalpin@w3.org] 
Sent: Tuesday, March 10, 2015 3:08 PM
To: Revising W3C Process Community Group
Subject: When to close a Working Group?

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

Received on Tuesday, 10 March 2015 23:02:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 March 2015 23:02:15 UTC