Re: List of TODOs discovered during the QA Review

Thank you for your work on this!
My my biggest (and only, currently, because this is why I am not using the
issue tracker at all) pain point is the lack of an SSO support. I do not
want to create yet another user just for this system.


On Fri, Jul 18, 2014 at 1:59 AM, Amelia Bellamy-Royds <> wrote:

> I will make a point of importing these to the project manager; thanks for
> the reminder Jen.
> To everyone else on the list:
> A team of us are working on re-vitalizing and re-organizing the Web
> Platform Docs issue tracker and project management system, at
> We'd appreciate everyone's feedback about that system.  Are there any
> features you find particularly useful?  Are there any areas you find
> particularly confusing?
> For starters, we know that the landing page needs to be a little more
> welcoming.  In the meantime, there is a brief how-to at the bottom of this
> page:
> And of course, if you (like me) have been using the email list to document
> areas that need improvement, you can make sure to create a matching issue
> so it won't get forgotten.
> On 17 July 2014 15:30, Julee Burdekin <> wrote:
>>    1. +1
>>    2. +1
>>    3. Test pages have been needed in the past to test imports and such.
>>    4. Web Platform Wednesdays and some guidelines are also in Meta, so a
>>    review would be good.
>> Also, a lot of the pages I checked have a section called “Related Pages
>> (MSDN)”,[1] indicating imports that haven’t been resolved.
>>  J
>> [1]
>>  -------------------
>> Julee Burdekin
>> Content Strategist
>> Adobe Web Platform
>> @adobejulee
>>   From: Amelia Bellamy-Royds <>
>> Date: Friday, July 4, 2014 at 5:39 PM
>> To: WebPlatform Public List <>, Doug Schepers <
>> Subject: List of TODOs discovered during the QA Review
>> Resent-From: WebPlatform Public List <>
>> Resent-Date: Friday, July 4, 2014 at 5:39 PM
>>   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]:
>>  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 Friday, 18 July 2014 08:24:55 UTC