Creating a Working Group |
Organizing a Workshop |
setting up a meeting registration with WBS |
mostly good |
reviewing position papers with WBS |
ad-hoc |
Creating the Working Group charter |
Use the Charter template |
manual |
Setting milestones |
manual |
Getting the Working Group charter reviewed |
setting up a WG charter review questionnaire |
ready |
Starting a Working Group |
Creating a Call for Participation |
setting up a group in IPP |
mostly ready |
drafting the Call for Participation |
ready |
Maintaining WG participants list |
using DBWG (can be synchronized with mailing list subscriptions) |
ready |
automated for IPP groups |
ready |
Creating a WG Web space |
news system (à la blog and Wiki) |
mostly ready (with Markup Guidelines) |
using a standard layout |
low end (with Markup Guidelines) |
setting ACLs per area |
ready |
Organizing regular meetings |
Setting up meetings |
deciding day, time (teleconf), place (f2f) |
ad-hoc with WBS and the meeting planner |
setting up a F2F meeting registration with WBS |
ready |
informing W3C members of a F2F |
low-end (, generated iCalendar) |
requesting a teleconference slot |
low-end (adminreq) |
Managing meetings |
creating and announcing an agenda |
nothing |
finding a scribe |
low-end (manually maintained list or Zakim) |
publishing minutes with RRSAgent and scribe.perl (or with the related comma-tool) |
can be improved but already pretty good |
recording issues, resolutions, action items with RRSAgent |
can be improved but already a basis |
recording issues, resolutions, action items with trackbot |
very efficient |
Getting to consensus |
Tracking issues |
with GitHub |
can be improved but already a basis |
and more |
ad-hoc |
Organizing straw poll & votes |
setting up formal votes and straw polls with WBS |
ready |
Publishing documents |
Getting write-access for Editors |
GitHub access | ad-hoc |
Making progresses on internal drafts |
gathering requirements and use cases |
nothing specific |
gathering requirements and use cases |
nothing specific |
Using GitHub |
proper workflow |
annotating a document |
Annotea but rarely used |
using editing templates |
,new ? |
maintaining a list of test assertions |
nothing specific |
Getting document ready to publish |
ReSpec | unobtrusive JavaScript spec editing tool |
TR Bibliography generator |
mostly ready, but rarely used |
Bikeshed converts a document in Bikeshed format (a mixture of HTML5, MarkDown and its own extensions) to a W3C Technical Report |
Ready. Source & documentation. As of 2017 actively developed. |
TR "munger" (fix documents to make them pubrules-compliant) |
munge 0.1 (Bash script;
run postprocessor afterwards) |
TR postprocessor
(ToC, bibliography, cross-refs, section numbers, alphabetic index,
etc.). |
Ready.
(Manuals 1
and 2 assume a CSS spec, but
tool works for any.) |
Pubrules checker |
ready |
Producing diffs between 2 versions of a draft |
tools available but not really deployed? |
Producing PDF versions of the spec |
ad-hoc tools in WGs, but nothing deployed (see also Norman Walsh XSL FO) |
Normative references checker |
ad-hoc |
TR References checker |
ready |
IETF References checker |
ready |
spell checker |
ready |
Getting a document published |
finding a publication date (Webmaster, Comm Team)
|
nothing |
Setting automatic publication |
ready |
Managing document transitions |
finding a date with Director |
nothing |
draft a director decision |
nothing |
prepare a call for review (PR, PER) |
ready |
Tracking and responding to feedback |
Setting a feedback system |
creating a specific mailing list |
ready, but harder to track |
using GitHub |
ready |
Tracking feedback |
using GitHub |
reliable |
Generating a disposition of comments |
Using GitHub
|
nothing |
Managing patent disclosures |
with WBS |
ready |
IPP |
ready (but limited to groups under PP) |
Managing implementation reports |
Managing test cases |
Using WPT |
reliable |
packaging test suites |
nothing specific |
Managing test results |
Using wpt.fyi |
Need browser upgrades |
gathering results using WBS (e.g. XKMS Test Suite) |
ad-hoc |
Generating Implementation Reports |
Using wpt.fyi |
nothing specific |