557770 - create Plugins product for third party plugins

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[timeless]

Attachment: list of components, qa contacts, descriptions

bug 487938 comment 20, bug 487938 comment 21...

I'm going to attach a .csv file with a list of components

the general format is:

Component name, proposed qa contact, description row, description row, description row, created

The last couple of items are plugins which I know about but for which I didn't spend enough time verifying we have existing bugs.

I've precreated the product and components which I've marked as created in the csv file, leaving the qa contact in the description field.

I need marcia/reed to create these accounts:
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]

Once they're created, I'll move them to the qacontact field and unhide the product, open it for business, and start moving bugs to it.

Comment 1

[Gervase Markham [:gerv]]

This page may be useful in confirming you've provided all the info necessary:
https://wiki.mozilla.org/Bugzilla_Administration

The description should probably add a note saying "Note: these are not the same thing as add-ons", or better words than that.

Gerv

Comment 2

[timeless]

* I've picked the components Classification for plugins. If someone objects, we can trivially move it.

* product description is "For problems with third party plugins (NPAPI)" [see attachment], we can extend it later or point to a link later. I suppose that chofmann or tomcat might have some links

* components [see attachment]
* i might provide versions later and will probably add target milestones, but i'd plan to do this on a plugin by plugin basis (i.e. one bug per plugin)

* i suppose i'll probably enable the core security group and ask for the enter_bug cgi to auto route its magical security checkbox to that.
- currently i'm using a different group just to hide the product from 99% of users (this will go away once i get my watchable qa accounts configured)

i'd rather make any of these (or) additional changes later in additional bugs, we've had a need for this for many years now, and waiting doesn't benefit anyone.

Comment 3

[timeless]

oh, oops, there's a second paragraph to the product description:

This product is for enabling collaboration between mozilla.org and third party plugin vendors. Vendors will be recognized, and able to mark bugs as fixed with references to their software versions.

Comment 4

[timeless]

spoke to reed, and we picked this naming convention:

[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]

Comment 5

[Reed Loden [:reed]]

(In reply to comment #4)
> [e-mail]

Done except for this one, as I assume we'll just move the existing JEP component to this new product, and I'll just rename the QA contact when that happens...

Comment 6

[timeless]

yep

Comment 7

[timeless]

the collapsing of JEP into Plugins was bug 557953

I've changed "problems" to "issues" in the descriptions of the components.

I've filed bug 558096 for the initial set of versions/target milestones.