move to mozilla.org
Assignee: myk → ian
Component: User Accounts → Bugzilla: Keywords & Components
Product: Bugzilla → mozilla.org
QA Contact: mattyt-bugzilla → timeless
Version: unspecified → other
phil: Wouldn't you rather have new components, instead of accounts?
Ian and Asa: you are right; I didn't realize that's how it's done. What was done for Layout seems right here. As to Asa's question: > Would this be better done by making JSEng a Product in bugzilla > so that we could have a nice component list? I will let Brendan comment on that. The Layout categories are all components under the Browser product. Should the same be done for JS Engine, or should JS Engine be elevated to a product?
JS engine certainly could be a product; the code stands alone, or with NSPR as its only dependency apart from standard C if JS_THREADSAFE. See also Rhino. One thought: would making it a separate product make reassigning DOM bugs that are frequently mis-reported as JS bugs easier, or harder? If harder, maybe bugzilla needs to make it easier, but we could wait to take the plunge and pay the price. The Browser product needs breaking up. Should we have a "grand plan" before we start parting out things like the JS Engine? /be
Phil: I created the accounts, you can use them today. If that's enough then we can resolve this bug. Brendan: Yes reassigning across products is harder. As is moving groups of bugs across products (which we will want to do eventually). This is why layout isn't a product today. Asa: Some people (I thought you were among them) argued against growing the component list. While it would be useful to Phil to have components it will not help 98% of the Browser userbase to add those components, and splitting it out to a new product will most likely annoy the few triagers we have (namely Phil and Boris).
> I created the accounts, you can use them today. If that's enough > then we can resolve this bug. That does it for me. I agree with timeless' comments about keeping this as simple as possible. Let me resolve this bug as FIXED, then. If we wish to pursue the larger issues raised above, we can open a separate bug for that. Thanks to all!
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
No, let's please not go the rout of 8 new email addresses. Timeless, please don't create dummy bugzilla accounts while we're still discussing things. I think JSEng should probably be a product or should be made more granular as components in the new Product organization. Phil, can you hold off for a day or two while I try to make some time to sort this out?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
> can you hold off for a day or two... Sure - no hurry. I've only reassigned one bug so far, as a test: bug 2183 nor P5 PC email@example.com Sorry for resolving this bug too soon -
So what's the story here?
I'd be happy if I could just reassign all JS Engine bugs currently associated with non-existent email accounts to "firstname.lastname@example.org". I agree strongly with timeless that unless JS Engine is elevated to a product in its own right, it should remain a single component under the Browser product. It's just too confusing for users as it is without complicating things even more. Of course, I will defer to what others feel, but that's my two cents.
well in the interim i think we should make the default owner email@example.com i don't see anyone opposed to that.
Status: REOPENED → RESOLVED
Closed: 19 years ago → 18 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.