- From: Ian Jacobs <ij@w3.org>
- Date: Mon, 19 Sep 2011 10:21:43 -0500
- To: "Coralie Mercier" <coralie@w3.org>
- Cc: "hhalpin@w3.org" <hhalpin@w3.org>, "public-council@w3.org" <public-council@w3.org>
On 19 Sep 2011, at 10:09 AM, Coralie Mercier wrote: > > Hello Ian, public-council people, > > Having looked at the "Program Documentation" part of the priority part of the CG implementation plan: > https://www.w3.org/2010/11/community#priority > > I am reviewing Harry's draft (and started to fix some stuff as I trudged through): > http://www.w3.org/community/council/wiki/Welcome_to_Community_Groups#Community_Groups > > I have a comment and a question before I carry on. > > Most of the fleshed-out content can be found on the Guidebook [1], but the guidebook is member-only. > [1] https://www.w3.org/Guide/ > > It seems wasteful, to me, to replicate the guidebook (or to interpret it and phrase it differently) on that wiki. > > > Ian, what prevents us from making the guidebook public with a disclaimer that some links are Member-only? We might be able to do that (with a review of the content) but I'd rather not take that on as part of this project just yet. It also seems to me that: 1) We have talked about reorg of /Guide as faceted set of views but have not implemented 2) It is organized with WG flow in mind 3) It is mostly a link farm. > > If this is possible, I propose to focus the welcome! documentation only on aspects that relate to the CG infrastructure (running a group, some of the tools, how to get stuff done, all this overlaps with other types of working groups and can be found in the guidebook) > > For example, in section four, I propose to keep only 4.1, 4.5 and 4.6.: > > [[ > 4 Chairing a Group > 4.1 Adding and Changing Chairs > 4.2 Breaking The Ice > 4.3 Dealing with Disruptive Group Members or Spammers > 4.4 Making Decisions > 4.4.1 Running Meetings > 4.4.1.1 Prepare the meeting > 4.4.1.2 Manage the meeting > 4.4.1.3 Finish the Meeting > 4.5 Moving Your Work to a Standard > 4.6 Closing a Group > ]] > > In the whole draft, I'd favour keeping only the following parts (numbering no longer consistent, since I'll remove entire lines): > > [[ > 1 Welcome! > 2 W3C Forum > 3 Creating a New Group > 3.1 Proposing a Group > 3.2 Group Acceptance > 4.1 Adding and Changing Chairs > 4.5 Moving Your Work to a Standard > 4.6 Closing a Group > ]] > > What are your thoughts? How about this TOC: * Before you start your group - building support - temporary infrastructure * Proposing a Group * Getting people to support your group * How people join your group - about the legal agreements - affiliation information * Getting started in your group - picking chair(s) - using the tools * Publishing documents (COMING SOON!) - publishing mechanism - final specification commitments * Making the transition to standards track * Closing a group Ian > > Coralie > > -- > Coralie Mercier - W3C Communications Team - http://www.w3.org > W3C/ERCIM - N212 - 2004, rte des lucioles - 06410 Biot - FR > mailto:coralie@w3.org +33492387590 http://www.w3.org/People/CMercier/ > -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Monday, 19 September 2011 15:21:50 UTC