473111 - Create Mozilla Labs :: Bespin component

Status: RESOLVED FIXED

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

Description

[Dion Almaer]

We are going to be releasing a new project called "Bespin" shortly. I would love to have a place on Bugzilla to collect bugs/issues.

Can we get one setup? Under labs?

Cheers,

Dion

Comment 1

[Reed Loden [:reed]]

Not an IT issue.

Need a description to use. See https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Labs for examples.

Comment 2

[Dion Almaer]

Thanks. This would work well:

"Bugs and feature requests for the Bespin experiment from Mozilla Labs."

Comment 3

[Dion Almaer]

And if we can put in the email as [e-mail] that would be great. I am new to this, will we be able to setup sub-components ourselves?

Comment 4

[Marcia Knous [:marcia]]

Dion: Do you want to be the default assignee and then for us to create a watch email for the QA field?

You will not be able to setup any of the versions, milestones, etc - that will have to be done by a bugzilla admin.

Comment 5

[Dion Almaer]

Marcia,

That sounds fantastic. Thanks!

Once setup, should I file another bug with subcategories, milestones, versions that the project needs?

Cheers.

Comment 6

[Marcia Knous [:marcia]]

Dion: Just so you know, there is not another level under the Component category. So right now your project will be in Mozilla Labs | Bespin (component). You can then add milestones and versions, but nothing else under the Bespin component level. If you want milestones and versions to be added now, feel free to add them to this bug and we can do it all in one fell swoop.

Comment 7

[Reed Loden [:reed]]

(In reply to comment #4)
> Dion: Do you want to be the default assignee and then for us to create a watch
> email for the QA field?

I doubt he really wants to be the default assignee unless he's absolutely the only one working on this project... [e-mail] is usually better in all cases.

Comment 8

[Dion Almaer]

Ah yes, [e-mail] for default makes sense. I just want [e-mail] to get notifications.

As far as the other data, how about this:

Versions:

0.1
0.2
0.3
Trunk

Milestones:

Initial Launch 0.1
Future

--

Thanks!

Comment 9

[Marcia Knous [:marcia]]

Dion: If you have the watch email be yours then that means no one else can watch those bugs - just like it is better to have the default assignee be nobody, I think it better to have the watch email be generic such as [e-mail]. If that sounds good I will go ahead and create the component.

Comment 10

[Dion Almaer]

Marcia,

Great. Can we seed that bespin@ list with [e-mail] (which is the list that has the current team) ?

Comment 11

[Reed Loden [:reed]]

(In reply to comment #10)
> Marcia,
> 
> Great. Can we seed that bespin@ list with [e-mail] (which is the list
> that has the current team) ?

Nope, but you can watch that bespin@ account yourself by going to https://bugzilla.mozilla.org/userprefs.cgi?tab=email#new_watched_by_you and entering the full address in the box once it's been created.

Comment 12

[Dion Almaer]

A ha!

Thanks for the hand holding on all of this. Much appreciated.

Comment 13

[Marcia Knous [:marcia]]

Component created. I added the requested versions. Regarding milestones, Mozilla Labs already has 0.1 and Future, so I don't think we need to add anything there.

Resolving as fixed.

Comment 14

[Dion Almaer]

Great thanks. How are keywords used? I would love to use them as subcategories of Bespin.... but I don't know if that is how things work.

Comment 15

[Marcia Knous [:marcia]]

Dion: Probably better to use the status whiteboard field for that, since you can type anything you want. Keywords are more customarily used across projects, not for categorizing individual subcomponents.

Comment 16

[Dion Almaer]

Ah ok. Where do I see the status whiteboard? I don't see it in the UI... and I only found:

--
usestatuswhiteboard: This defines whether you wish to have a free-form, overwritable field associated with each bug. The advantage of the Status Whiteboard is that it can be deleted or modified with ease, and provides an easily-searchable field for indexing some bugs that have some trait in common. 
--

Comment 17

[Marcia Knous [:marcia]]

The Whiteboard is listed directly under the Status of the bug.