Last call for Volunteers! Re: The June 2014 WebPlatform Quality Assurance Sprint

We're almost ready to get rolling on the massive blitz to assign readiness
states to every article in the wiki.

I've updated the project page ( ), and
will be sending all the volunteers a link to a search page with their
assigned articles on Thursday.  We'll be trying to get everything done by
the end of June.

But we've got 4400+ articles and only 10 volunteers so far, so if you think
you can spend a few hours this month madly skimming through web platform
articles, PLEASE SIGN UP on the project page.  The more people we have, the
fewer articles we have to do each.

These are the names I've currently got on the list:

   1. shepazu
   2. renoirb
   3. jensimmons
   4. julee
   5. eliot
   6. AmeliaBR
   7. eliezerb
   8. garbee
   9. frozenice
   10. Michaela

To everyone who has volunteered, please

   - Review the Decision Tree and To-Do lists I posted on the project page
   and reply if anything is unclear.
   - Indicate next to your name which subject areas
   (HTML/DOM/CSS/Javascript/SVG) you're most comfortable with; I'll try to
   make most of your articles in those sections

P.S.  If anyone wants to turn the decision tree into a proper flow chart,
that would be great.  The list format isn't very easy to read at a glance.


On 27 May 2014 14:25, Amelia Bellamy-Royds <>

> Hello everyone,
> If you read these emails regularly, you know that there have been a number
> of infrastructure activities going on in order to get
> looking professional and ready for public consumption, so that we can
> remove the big purple "*Web Platform Docs is in alpha
> <>*" warning that is currently on
> the top of every page.
> A key part of this is the new article-by-article readiness marker system,
> so that we can clearly indicate to readers which individual pages still
> need work and which are ready to use.  We currently have the templates in
> place [1], and Jen Simmons is working on adding some style to make the
> information part of the layout instead of a warning box [2].
> However, for all that to mean anything we need to assign a readiness state
> to each an every article.  Currently there are 4408 articles showing up in
> my search of pages that use the readiness template [3], of which 4405 are
> "Unreviewed".
> In the weekly teleconferences, it was agreed that the best approach was to
> do this was to divide the articles up among regular contributors (people
> who are familiar with the content expectations and the structure of the
> site), and assign readiness states manually.
> *If you can participate, please add your name to the list on the QA Sprint
> project page:*
> *
> <>*
> (Note that I've already signed up the "usual suspects", so you might want
> to check and remove your name if you're busy all June!)
> At the same time as the readiness review, since we don't want to do this
> again any time soon, we would also want to take care of any other clean-up
> tasks that need to be done manually by someone familiar with the site.
> We therefore need to decide on a checklist of Quality Assurance tasks.
>  These have to be simple, quick assignments that someone can do without any
> additional research, and which will make a meaningful improvement to the
> consistency and reliability of the site content.  So far we have:
> *The QA Checklist for June 2014 QA Sprint:*
> 1. Assign a readiness state. More about readiness states (requires
> clean-up)
> 2. Add any details about readiness/what is required to the editorial notes
> box.
> 3. For DOM method pages, assign index values to the parameter entries in
> order to get the correct syntax to display, as described in this email post.
> 4. Confirm that the new compatibility tables are pulling in the correct
> data (Doug Schepers is going to give us more information about this once
> the import from MDN happens later this week).
> Possible additions (if we have enough volunteers that we can afford to
> spend more time per page):
> 1. Ensure that every page has a summary section.
> I've added a couple other sections and ideas to that project page [4], but
> everything else is still pretty tentative.  Ideas and initiative welcome --
> I'm not going to have time to do much extra work on this myself, but we
> wanted to get the ball rolling sooner rather than later.
> Best,
> Amelia
> [1]:
> [2]:
> [3]:
> [4]:

Received on Wednesday, 11 June 2014 05:34:06 UTC