[QA] Quality-Assurance phab project

[Greg Grossmeier]

<quote name="Greg Grossmeier" date="2015-03-25" time="08:21:23 -0700">
> <quote name="Željko Filipin" date="2015-03-25" time="15:12:05 +0100">
> > I have moved all projects from QA to either browser-tests or releng, or ci.
> > If anybody thinks we really need QA, speak up. If not, I vote for deleting
> > the project.
> 
> Let's just make sure that everything in #releng *also* has a "component"
> project (as defined by [0]) associated with it.
> 
> Why? Because I've begun removing things from the #releng backlog that
> aren't A) going to happen any time soon and B) are just general backlog
> of a certain part of our infra (eg: Jenkins, Beta, scap, whatever). This
> helps us keep honest about what it is we're working on long term (or
> want to/plan to).
> 
> Thanks for taking the lead on this, Zeljko.

Following up on this...

I went through the changes and started adding in other projects to tasks
that only have #browser-tests associated; reasoning is that, as it is
now, #browser tests is a "tag" [0] and really issues/feature requests
should have a home in a "component" [0].

But then I came across tasks like:
* https://phabricator.wikimedia.org/T64143  - "Rename URL module to
  something like MediaWikiUrl or MediaWikiURL"

* https://phabricator.wikimedia.org/T1330 - mediawiki-api gem should
  have integration tests


With a quick conversation with Dan on IRC, we came up with:
1) change #browser-tests to a "component" from a "tag"
2) have that be the home for all of the pieces that make up the browser
   tests (that aren't already covered by Jenkins/CI)


Ontologies are a hard thing to do right, so before I just push forward
I'm practicing good remotie-filled-team etiquette and keeping the list
the primary medium of discussion :)


Greg


> [0] https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project

-- 
| Greg Grossmeier            GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg                A18D 1138 8E47 FAC8 1C7D |