Closed
Bug 755026
Opened 12 years ago
Closed 12 years ago
Please create a new product called "webmaker.org"
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: boozeniges, Assigned: dkl)
References
()
Details
The name of the product: mozillaignite
The classification (group) you would like the product in: Other
A longer description, usually including a web link for more info on the product
Site that will help support the Mozilla Foundation webmaker strategy - "creating the next generation of web makers"
The initial list of components, with their info (see below):
- "general" will do.
The initial list of versions, with their info (see below)
- nothing needed.
The initial list of target milestones, with their info (see below)
- nothing needed
The security group(s) bugs should be classified under when a user checks the security flag (if you don't know, we can help figure this out for you)
Don't think so
The number of votes needed to confirm a bug (UNCO --> NEW) (optional, disabled by default)
disabled please.
If you could make the default QA contact be (me) ross@mozillafoundation.org, that'd be great!
(In reply to Ross Bruniges from comment #0)
> The name of the product: mozillaignite
/me assumes webmaker.org
given you don't appear to have any special requirements with regards to components, versions, milestones or security, a product for this website is probably an overkill for your requirements.
are you ok with a component "webmaker.org" under the "Websites" product?
Reporter | ||
Comment 2•12 years ago
|
||
We're hoping for a project in the same manner as https://bugzilla.mozilla.org/enter_bug.cgi?product=Webpagemaker
We'll likely need components and stuff in the future as it's going to scale up rather a bit in upcoming months and have different features that having this ability will be really useful.
Is that going to be OK?
Assignee | ||
Comment 3•12 years ago
|
||
done
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•