- From: Doug Schepers <schepers@w3.org>
- Date: Thu, 20 Jun 2013 10:37:09 -0400
- To: spec-prod@w3.org
- CC: Philippe Le Hegaret <plh@w3.org>
Hi, folks- I have a suggestion for our publication workflow that I think would provide clarity and consistency: a publication request form. This would be a form that contains all the fields needed for each stage of the publication process, including spec name, shortname(s), URLs of Editor's Draft and TR draft, abstract, WG name, WG approval to publish, planned publication date, news-item blurb, optional list of changes, notes (for anything out of the ordinary), etc. Anyone could fill out this form, though typically it would be the staff contact's responsibility; once submitted, the publication request goes into the DB, and emails to the appropriate people and lists (chairs list, domain lead, staff contacts, marcomm, webreq, etc.) are sent out automagically. In addition, it's queued up in a list/tool (maybe team-only, but with a public view) that lets the domain lead and/or director click a checkbox to approve the publication if necessary; this would also generate the correct emails. This list would include crucial status information, to make it easier to track what stages have been done for the publication, and what is blocking, making it consistent and easy to review and approve without hunting through email lists. Some odd cases would need to be done by regular email, of course, but the vast majority of spec publications would be handled by this. This would be an optional tool, though staff contacts would be encouraged to use it; if the pub requests came through email, the staff contact or webmaster could just make sure they are filed in this system correctly. This would empower WG participants, and could free up some of the more tedious time from staff contacts. This may already have been suggested elsewhere or elsewhen (I thought of it years ago), but I think it'd be useful. Anyone like this idea? Regards- -Doug
Received on Thursday, 20 June 2013 14:37:20 UTC