Re: Call for Consensus: Please review the draft charter

Hi Jay,
Welcome to group, btw!  

On Monday, December 5, 2011 at 12:54 PM, Jay Balunas wrote:  
> Hi All,
>  
> I'm new to the group, my name is Jay Balunas and I am a project lead for RedHat/JBoss on mobile platform development. I hope to have more time in the near future to contribute, but wanted to introduce myself!
>  
> Comments inline...
>  
> On Dec 3, 2011, at 5:25 AM, Scott Wilson wrote:
>  
> > On 2 Dec 2011, at 23:47, Carr, Wayne wrote:
> >  
> > > Nice going!
> > >  
> > > Just a couple of comments. The last one is the only serious one.
> > >  
> > > "The CG treats specifications as living documents: specifications are not versioned and they are not dated"
> > > I'd delete that line. Maybe it doesn't need to be (though when working with a WG I think it's going to be necessary to know exactly what was the input for a particular stage). You could just remove the prohibition and see what works.
> > >  
> > > "A W3C Working Group takes ownership of it to progress it along the Recommendation track."  
> > > But, you never give ownership do you? You give them a version. They make change requests, you give them another version. They decide to publish some version as a Candidate Rec. You don't actually give them "ownership" - you give them copies of versions. The actual editing of the doc for technical content would be in the CG, not the WG.
> > >  
> > > "Every conformance requirement has a tests"
> > > Typo - "test"
> > >  
> > > "A specification is “done” when"
> > > I'm not sure about that list - I'd drop it. That's when a version of a spec is gone to REC. But if there are no "versions" it isn't meaningful so say that means it is done. It would be done when no one wants to keep working on it. It seems a spec is done when the CG no longer wants to work on it because they think it is done or decides to drop it.  
> >  
> >  
> >  
> > That makes more sense.
>  
> +1 - if there are no versions, its hard to mark as "done"
What is we clearly mark it as such? Like at the top of the document we put "DONE" or "Work in Progress".  

For example, see the red box at the bottom of:
http://www.w3.org/TR/html5/


  
> > > "If a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Editor of a specification can make a decision on a matter. In extreme cases, the Chair will put a question"
> > > Instead of "In extreme cases" it would be better to have some process to object to an Editor's decision and call for a vote. One possibility is someone objects, the chair then makes a decision. Someone formally objects to that and it goes to a vote. And it should say that should be avoided whenever possible. But there needs to be a way to not have ultimate decisions be one or two people.
> >  
> >  
> >  
> > Sounds good - as a CG the ultimate authority should rest with the community, not the editors.
> >  
> > ... but thats a last resort as you say - for most practical decisions lazy consensus will work.
>  
> Coming from a community lead role at JBoss I agree here 100%. The original wording could put some people off.
Be great if you could give the Charter a final review!  

Also, is there anything in particular you want to work on?  

Kind regards,
Marcos

Received on Monday, 12 December 2011 18:16:12 UTC