W3C home > Mailing lists > Public > public-webplatform@w3.org > July 2014

Re: List of TODOs discovered during the QA Review

From: Jen Simmons <jen@jensimmons.com>
Date: Thu, 17 Jul 2014 17:03:47 -0400
Message-ID: <CAB0bRKNY_LFkAN5Up2KUJG2Mae=4=hvfdq=HW7TosUpfZNyS9g@mail.gmail.com>
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Cc: List WebPlatform public <public-webplatform@w3.org>
Let's talk tomorrow about adding these to the PM system. It'd be great for
you to do that soon.

Jen Simmons
designer, consultant and speaker
host of The Web Ahead
twitter: jensimmons <http://twitter.com/jensimmons>

On Fri, Jul 4, 2014 at 8:39 PM, Amelia Bellamy-Royds <
amelia.bellamy.royds@gmail.com> wrote:

> Hello all,
> I've been having various chats by email and IRC about quirks and
> questionable content discovered while assigning readiness states during the
> QA Sprint.  RenoirB suggested that I start an email thread to collect them
> all -- and suggestions on what to do with them -- in advance of the next
> community telcon.
> Here's what I have so far.  Please reply with any additions to this list
> or related commentary.
> 1. Glossary pages.  There are a number of pages in the top-level file path
> (like wiki/absolute_unit) that contain glossary entries.  These should all
> be grouped into a logical file path like wiki/glossary/absolute_unit, but
> there are probably other things that can be done to make the glossary as a
> whole more useful and organized.
> 2. Tables with listings of other pages.  We've discussed the problems with
> the formatting and content of listings in a separate thread [1], but this
> should move up the priority once the QASprint is over.  [1]:
> http://lists.w3.org/Archives/Public/public-webplatform/2014Jun/0014.html
> 3.  TEST: namespace pages.  With a completely separate test wiki, I don't
> think there is any use for the TEST: namespace, but the pages should be
> reviewed to determine if there is content that should be merged into the
> main wiki before they are deleted.
> 4.  Similarly, renoirB noted that there is a Meta: namespace which was
> used to back-up custom content before mass import of docs from MSDN.  These
> need to be reviewed and content merged into the main docs (perhaps this
> could be a DocSprints task?).
> 5.  Imported pages with no page templates / default forms.  There are a
> lot in the SVG pages I was going through, but there may be others.
> Any other quirky issues to add to this list?  Of course, you will have
> also discovered a lot of content-related TO-DOs, to address all the "Not
> Ready" and "In Progress" pages.  But for now, I'm mostly focusing on issues
> where a decision has to be made about what should be done.
> Best,
> Amelia BR
Received on Thursday, 17 July 2014 21:04:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:02 UTC