Closed Bug 487983 Opened 11 years ago Closed 11 years ago

Move Bespin into its own product

Categories

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

task
Not set

Tracking

()

VERIFIED FIXED

People

(Reporter: GPHemsley, Assigned: reed)

References

Details

I've discussed with Dion the possibility of moving Bespin out of the Mozilla Labs product so that it may have its own components, as using the whiteboard is becoming unwieldy. He mentioned that he was discussing it with the higher-ups, but I noticed that there's no bug filed about it (that I can see, at least), so I've decided to file one. I don't know what classification it would be best filed under, but that's not important to me, so you can use your best judgement on that.

Here are the components that I recommend we start with:
Bespin :: General
Bespin :: Add-ons & Plugins
Bespin :: Authentication
Bespin :: Command Line
Bespin :: Dashboard
Bespin :: Documentation
Bespin :: Editor
Bespin :: Infrastructure
Bespin :: Key Bindings
Bespin :: Search
Bespin :: Server
Bespin :: Syntax Highlighting
Bespin :: Thunderhead
Bespin :: User Interface
Bespin :: Other

By default (if there is such a thing), Bespin bugs should go into Bespin :: General, after which they would be sorted into another component.
descriptions are appreciated.
My apologies. I wasn't even aware they could get descriptions.

Below are the descriptions for each of the components I listed in comment 0. One component that may be in question is that for Thunderhead, because it appears that it may be becoming its an experiment of Mozilla Labs in its own right. As of right now, though, it looks like it still falls under the Bespin component, so it can be included in this transition.

Bespin :: General
General bugs and feature requests for Bespin. Uncategorized bugs should go here.

Bespin :: Add-ons & Plugins
Bugs and feature requests related to extensions of the Bespin platform.

Bespin :: Authentication
Bugs and feature requests related to authenticating with the Bespin server.

Bespin :: Command Line
Bugs and feature requests related to the Bespin command line.

Bespin :: Dashboard
Bugs and feature requests related to the Bespin dashboard.

Bespin :: Documentation
Bugs and feature requests related to documentation of Bespin.

Bespin :: Editor
Bugs and feature requests related to the Bespin editor.

Bespin :: Infrastructure
Bugs and feature requests related to administration of bespin.mozilla.com and other developer resources for Bespin.

Bespin :: Key Bindings
Bugs and feature requests related to key bindings within Bespin.

Bespin :: Search
Bugs and feature requests related to searching within Bespin.

Bespin :: Server
Bugs and feature requests related to the Bespin server backend.

Bespin :: Syntax Highlighting
Bugs and feature requests related to syntax highlighting within Bespin.

Bespin :: Thunderhead
Bugs and feature requests related to the Thunderhead toolkit.

Bespin :: User Interface
Bugs and feature requests related to the user interface of Bespin.

Bespin :: Other
Bugs and feature requests related to Bespin that do not fall under any of the other Bespin components.
I just wanted to note that the default link for Bespin on the bug entry page should be:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Bespin&component=General

This helps to ensure that new bugs get filed in the correct default component (since bug reporters are often lazy and report bugs in the defaultly-selected component).
(In reply to comment #3)
> I just wanted to note that the default link for Bespin on the bug entry page
> should be:
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Bespin&component=General

That's not currently possible to do with Bugzilla. Sorry.

Also, this needs to be signed-off by a member of the Bespin team before it can happen.
Ok great,

How about if we trim out the authentication item and we will lump that into "Server" (can use a whiteboard for that). Can we make this so Reed?

----
Bespin :: General
General bugs and feature requests for Bespin. Uncategorized bugs should go
here.

Bespin :: Add-ons & Plugins
Bugs and feature requests related to extensions of the Bespin platform.

Bespin :: Command Line
Bugs and feature requests related to the Bespin command line.

Bespin :: Dashboard
Bugs and feature requests related to the Bespin dashboard.

Bespin :: Documentation
Bugs and feature requests related to documentation of Bespin.

Bespin :: Editor
Bugs and feature requests related to the Bespin editor.

Bespin :: Infrastructure
Bugs and feature requests related to administration of bespin.mozilla.com and
other developer resources for Bespin.

Bespin :: Key Bindings
Bugs and feature requests related to key bindings within Bespin.

Bespin :: Search
Bugs and feature requests related to searching within Bespin.

Bespin :: Server
Bugs and feature requests related to the Bespin server backend.
whiteboard: authentication, language type (e.g. python, ruby, php, javascript)

Bespin :: Syntax Highlighting
Bugs and feature requests related to syntax highlighting within Bespin.

Bespin :: Thunderhead
Bugs and feature requests related to the Thunderhead toolkit.

Bespin :: User Interface
Bugs and feature requests related to the user interface of Bespin.
(In reply to comment #5)
> Ok great,
> 
> How about if we trim out the authentication item and we will lump that into
> "Server" (can use a whiteboard for that). Can we make this so Reed?
> 

> Bespin :: Server
> Bugs and feature requests related to the Bespin server backend.
> whiteboard: authentication, language type (e.g. python, ruby, php, javascript)

Sounds good to me. I just want to clarify that the "whiteboard" portion of this is not part of the description.
Things I still need:
* Description for the entire Bespin product
* Versions to add
* Target Milestones to add
* (optional) URL describing target milestones
Assignee: marcia → reed
Status: NEW → ASSIGNED
(In reply to comment #8)
> Things I still need:
> * Description for the entire Bespin product
> * Versions to add
> * Target Milestones to add
> * (optional) URL describing target milestones

Other than perhaps updating the description, is there any reason why those items can't/shouldn't be carried over from their current values?
(In reply to comment #9)
> Other than perhaps updating the description, is there any reason why those
> items can't/shouldn't be carried over from their current values?

I don't know which ones apply to Bespin directly as opposed to other Labs products, so I'd like a list. The current Mozilla Labs :: Bespin description is inappropriate for a product description.
(In reply to comment #8)
> Things I still need:
> * Description for the entire Bespin product

Edited from the Bespin website:

Bespin is a product, designed in Mozilla Labs, that proposes an open, extensible, web-based framework for code editing that aims to increase developer productivity, enable compelling user experiences, and promote the use of open standards. 

> * Versions to add

0.1, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6
0.2.0, 0.2.1
0.3.0
Trunk

> * Target Milestones to add

0.1.x, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6
0.2.x, 0.2.0, 0.2.1, 0.2.2
0.3.x, 0.3.0, 0.3.1
Future

> * (optional) URL describing target milestones
The Release Notes are here:
https://wiki.mozilla.org/Labs/Bespin/ReleaseNotes

I'm not sure if it'd be wise to link to the individual sections, though, because those links may change at the whim of any wiki editor.
(In reply to comment #5)
> Ok great,
> 
> How about if we trim out the authentication item and we will lump that into
> "Server" (can use a whiteboard for that). Can we make this so Reed?
What happened to the "Other" component? I was hoping to be able to keep separate the "to be sorted" bugs and the "doesn't have a component" bugs.
Done. Please let me know when I can remove the Mozilla Labs :: Bespin component.

Also, let me know if the placement of the --- TM is in the correct space.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
(In reply to comment #13)
> Done. Please let me know when I can remove the Mozilla Labs :: Bespin
> component.

I'll comment here when the migration is complete.

> Also, let me know if the placement of the --- TM is in the correct space.

If your goal was to put it between past and future releases, then it is indeed in the right place. Thanks so much!
(In reply to comment #14)
> (In reply to comment #13)
> > Done. Please let me know when I can remove the Mozilla Labs :: Bespin
> > component.
> 
> I'll comment here when the migration is complete.

As of right now, [ Mozilla Labs :: Bespin ] is empty, so it should be able to be removed. If there happens to be any new bugs there by the name you get to it, move them over to [ Bespin :: General ].
Component:  	Bespin
Component Description: 	Bugs and feature requests for the Bespin experiment from Mozilla Labs.
Default assignee: 	nobody@mozilla.org
Default QA contact: 	bespin@mozilla-labs.bugs
Component of Product: 	Mozilla Labs
Product Description: 	For bugs and requests related to management of Mozilla Labs and related projects.
Product Milestone URL: 	
Closed for bugs: 	No
Bugs: 	None
Blocks: 490250
No longer blocks: 490250
verified components, versions, milestones, qas, product description.

fwiw, the target milestone url wasn't specified, but something like https://wiki.mozilla.org/Labs/Bespin/Roadmap is more in keeping with the design of Bugzilla, if you'd like that specified, just file a new bug and suggest it.

also note that many products have a "more info" link in their description. if you'd like one added, simply file a bug with a suggestion.
Status: RESOLVED → VERIFIED
Blocks: 491652
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.