Closed Bug 354350 Opened 18 years ago Closed 14 years ago

product and components for mozilla composer

Categories

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

task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: glazou, Assigned: glob)

References

Details

name: Composer type: client product description: The gecko-based next-generation standalone wysiwyg HTML/XHTML editor components: build config installer sidebars tabbed editor startup extensions and themes accessibility site manager css editor toolbars help documentation preferences OS integration software update source view general
actually it exists, bug 255017 was fixed, it's just a secret.
(In reply to comment #1) > actually it exists, bug 255017 was fixed, it's just a secret. /me cannot believe his eyes... Why was it kept secret ?
dunno, it's open, you can file bugs in it today. and marcia will probably work on getting the missing components for you. you'll have to wait for justdave before it'll appear in the enter_bug.cgi list, but https://bugzilla.mozilla.org/enter_bug.cgi?product=Composer will work today.
Daniel: Here are the components that already exist: do you want to keep them and add the ones you detail in Comment 0 as well? Colorpicker: For bugs in the standalone Composer color picker. CSS Styles: For bugs in the standalone Composer style sheet editor. Documentation: For bugs in the standalone Composer documentation. General: For bugs in stanalone Composer which do not fit into other more specific standalone Composer components Preferences: For bugs in the standalone Composer Preferences. Site Manager: For bugs in standalone Composer site manager. Tabs: For bugs in the standalone Composer tabs. Templates: For bugs in the standalone Composer templates. Tip of the Day: For bugs in the standalone html composer's tip of the day feature.
Status: NEW → ASSIGNED
(In reply to comment #4) > Daniel: Here are the components that already exist: do you want to keep them > and add the ones you detail in Comment 0 as well? Yes please, Marcia. Here's the result of a merge : accessibility For bugs related to accessibility authoring guidelines build config For bugs related to the build configuration colorpicker For bugs related to the color picker css editor For bugs related to the CSS editor or inline styles editing documentation For documentation and inline help extensions and themes For bugs related to extensions and themes management and update general For bugs that don't fit into other components installer For bugs related to packaging and the installer OS integration For OS-specific bugs preferences For bugs related to application's preferences sidebars For bugs related to sidebars and site manager For bugs related to the site manager. software update For bugs related to application's update system source view For bugs related to the source editor startup For bugs related to the application's startup tabbed editor For bugs related to the tabeditor templates For bugs related to templates and the template manager tip of the day For bugs related to the tip of the day feature. toolbars For bugs related to the application's toolbars and their customization Thanks.
Are we going to use composer@editor.bugs as the default assignee, or nobody@mozilla.org? Also, I assume you want watchable QA components for all of these? In which case, justdave will have to add some more names for me to repurpose.
(In reply to comment #6) > Are we going to use composer@editor.bugs as the default assignee, or > nobody@mozilla.org? Also, I assume you want watchable QA components for all of > these? In which case, justdave will have to add some more names for me to > repurpose. default assignee: daniel@glazman.org default QA for components: wow, good question indeed ; this project has no QA volonteers for the time being
All of the requested components have been created and assigned to Daniel as the default assignee. Daniel: Let me know what you want to do about the QA contacts, for now they are being left blank.
As a person who follows various QAs for products, it'd be beneficial if we used QAs as we do in other products and did "component@product.bugs".
I can add QA watch aliases as soon as justdave frees up some addresses for me to reuse in bugzilla - right now there are not enough and I have already requested that he add some additional ones to use.
(In reply to comment #8) > All of the requested components have been created and assigned to Daniel as the > default assignee. Daniel: Let me know what you want to do about the QA > contacts, for now they are being left blank. Yay ! Thanks a lot Marcia !!!
Daniel: Do you still want individual QA contacts, or would you prefer a "composer" QA contact that would be for all the components?
This bug seems to have got lost in the mix - are QA watch contacts still wanted? Please advise and I can create them.
(In reply to comment #13) > This bug seems to have got lost in the mix - are QA watch contacts still > wanted? Please advise and I can create them. I say yes. My comment still stands and the (now duplicate) bug 472283 calls for them too.
Could we get Default Assignee = nobody at mozilla.org Default QA Contact = composer at composer.bugs and resolve this bug? We'll see later if we need more detailed QA addresses or not.
Assignee: mozillamarcia.knous → nobody
Assignee: nobody → glob
done. i've set the default assignee to nobody@mozilla.org, added and set the default qa as composer@compose.bugs. as daniel@glazman.org was the default assignee for the bugs, i've moved him to a default cc role.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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.