Lots of little bugs are being raised on embedding chrome & packaging (it's like being pecked to death by ducks!) so we need an Embedding: Packaging component to deal with it. To expedite quick fixes, we'll need to CC people from the security, installer, chrome & themes components. Thae list of names isn't decided yet, but I'll announce this bug on some mailing lists so we can put one together.
Garret Arch Blythe <email@example.com> would like to be CC'd
please suggest default assignee, qa contact, and perhaps a description, although I think we could probably glean one from this.
adam, can you provide a description for the component as well as who will be the default Assignee and QA contact?
in the also ran category, see bug 38922
actually, to be honest, for what you need atm, it'd be better to use a tracking bug because you can put your 'default cc list' onto the tracking bug and have people file new bugs wherever and have them block the tracker. when they add the dependency, the people cc to the tracker will be notified. I think i'm going to put up my "we don't really need this component" flag. Since you will be better served by a tracking bug and bugs filed where they actually belong. dveditz kinda spans security and installer. the other two are kinda wishy washy in general.
To do this, I need a good component description which says what kinds of bugs are expected for the component, and volunteers for initial owners and QA contact.
Is anyone interested in taking this? Description wise, the Embedding: Packaging component would be responsible for the scripts and manifests used to produce the embedding and GRE distributions and any chrome or packaging issues specific to these distributions.
Not much response...