426352 - Create "Fennec" product and related components in Bugzilla

Status: VERIFIED FIXED

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

Description

[Christopher Blizzard (:blizzard)]

It's time to add a full mobile product, right there along side firefox + tbird.  Can we use this as an icon?

http://blog.blacknight.com/images/black-phone.jpg

Comment 1

[timeless]

you need to specify:
0. classification (client software?)
1. product name
2. product description
3. one or more components (names+descriptions)
4. assignees+watchable contacts for each component
5. it'd be nice if you specified a roadmap url

Comment 2

[Christopher Blizzard (:blizzard)]

0. Client Software
1. Fennec
2. Fennec is the code name for the Mobile Browser from Mozilla
3+4 (list this out separately - we'll work on that)
5. Things are starting to show up here: http://wiki.mozilla.org/Mobile/FennecRequirements

Comment 3

[Christopher Blizzard (:blizzard)]

So for initial components I think we might want to have the following to start:

1. UI (Front End)
2. Extensions and Add-ons
3. Platform: Hildon
4. Platform: GTK+ on X
5. Platform: Windows Mobile
6. Platform: S60R3
7. Platform: GTK+ on DirectFB
8. Build Config
9. Bookmarks
10. Touch Navigation
11. Keyboard Navigation
12. Search
13. Software Update
14. Startup and Profile System

That's a good start, no?  A lot of these will have the same owners + qa contacts as Firefox (which is where a lot of that list comes from.)

Comment 4

[Reed Loden [:reed]]

(In reply to comment #0)
>  Can we use this as an icon?
> 
> http://blog.blacknight.com/images/black-phone.jpg

Really? Just seems a bit odd and out of place. I guess this will eventually be replaced with the Fennec logo once there is one.

Do we have permission from the creator of the image to use it for this purpose? Need to respect the author's rights here...

(In reply to comment #3)
> 1. UI (Front End)

Is this the equivalent of Firefox :: Theme? Just don't want this becoming a blackhole for things that should be in a more specific component, but this should be ok for now.

> 2. Extensions and Add-ons

What about themes? Maybe just "Add-ons" or "Add-ons Manager" since add-ons encompasses both extensions and themes? Firefox :: Extensions/Themes Manager will be renamed to "Add-ons Manager" as part of the bmo component reorganization by gerv.

> 3. Platform: Hildon
> 4. Platform: GTK+ on X
> 5. Platform: Windows Mobile
> 6. Platform: S60R3
> 7. Platform: GTK+ on DirectFB

What type of bugs would go under these components? Are these new widget interfaces or something? We don't usually have "platform" bugs under an end-user product but under something like "Core" since they affect more than just the product itself.

> 9. Bookmarks

Will you be using some other form of bookmarks, or will you be using Places? Firefox :: Bookmarks is deprecated, as Places has replaced it, so if you're using Places, might want to go with a different name, as Places isn't just Bookmarks.

> 10. Touch Navigation
> 11. Keyboard Navigation

How do these relate to Core :: Keyboard Navigation? If these changes aren't specific to Fennec, might be better to have stuff under Core, as per the reasons listed above.

> 13. Software Update

Will Fennec have any specific Software Update code that's different from what Firefox has? Toolkit actually contains Software Update, so the Firefox :: Software Update component should really be under the Toolkit product. This is getting moved as part of the bmo component reorganization by gerv.

What about some equivalent of Firefox :: General? Yes, the General component is a blackhole, but you do need a component to catch Fennec-specific bugs that don't fit into any other component. When you see that you're having a lot of the same type of bugs, then that's when you should request another component and move those bugs to it.

Hope this helps some.

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

I believe that 3-7 should be under "Core" with the other "Plaform: Xxx" components

Comment 6

[Christopher Blizzard (:blizzard)]

> Really? Just seems a bit odd and out of place. I guess this will eventually be
> replaced with the Fennec logo once there is one.
> 
> Do we have permission from the creator of the image to use it for this purpose?
> Need to respect the author's rights here...

I was kind of kidding about this. :)

Although I would love to have a pic of an old-school telephone.

Comment 7

[Christian Sejersen]

(In reply to comment #3)
> So for initial components I think we might want to have the following to start:
> 
> 1. UI (Front End)
> 2. Extensions and Add-ons
> 3. Platform: Hildon
> 4. Platform: GTK+ on X
> 5. Platform: Windows Mobile
> 6. Platform: S60R3
> 7. Platform: GTK+ on DirectFB
> 8. Build Config
> 9. Bookmarks
> 10. Touch Navigation
> 11. Keyboard Navigation
> 12. Search
> 13. Software Update
> 14. Startup and Profile System
> 
> That's a good start, no?  A lot of these will have the same owners + qa
> contacts as Firefox (which is where a lot of that list comes from.)
> 
We probably should add Qt as well.

Comment 8

[Christian Sejersen]

(In reply to comment #5)
> I believe that 3-7 should be under "Core" with the other "Plaform: Xxx"
> components
> 
I don't see any "Platform: Xxx" under "Core". I can follow the reasoning for putting these components under "Core" but on the other hand they are also closely tied to fennec (right now at least). Will it be difficult to move them to "Core" later if necessary?

Comment 9

[Christopher Blizzard (:blizzard)]

Yeah, we need to add Qt on that list.  It's going to be a factor at some point in the future, I'm sure.  Plus there's a lot of interest from community folks for Qt support - we should give them an outlet and place to work.

The platform bits should probably live in Core, as we discussed offline.  They largely deal with gfx/ and widget/ support and that's historically part of code and is owned by layout owners.

Comment 10

[Reed Loden [:reed]]

As for Platform: xxx, you probably just really mean GFX: xxx and Widget: xxx. :)

Comment 11

[Mike Schroepfer]

Reed are we blocking on anything to get this done?

Comment 12

[Reed Loden [:reed]]

Still waiting on some answers to my questions. Probably would be good to just get a group together on IRC to hash out exactly what components Fennec needs. It's very important to get this pretty much correct in the beginning, as it's a royal pain to rename/move/change components later. :)

Comment 13

[Reed Loden [:reed]]

I created http://wiki.mozilla.org/Mobile/BugzillaComponents for tracking exactly what components, descriptions, etc. are needed here.

Comment 14

[Reed Loden [:reed]]

I've created everything specified on http://wiki.mozilla.org/Mobile/BugzillaComponents. Please file new bugs for components as you need them. Let me know if something is missing or not correct.

Comment 15

[timeless]

verify created:
[Fennec] General 	[e-mail] 	[e-mail]
For bugs in Fennec which do not fit into other more specific Fennec components.

^ the description here needs work, would someone please file a bug w/ a new description (note: there are no other components, so anyone reading this should get a bit confused)
see: https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec&format=guided

votes to confirm: 100
milestones: M1..M6, A1..A4
http://wiki.mozilla.org/Mobile/FennecRequirements#Milestones
which lists M1..M6, A1 but not A2..A4 <- would someone please address this?

note that milestones in the requirements is of the form M1..M6, but the milestones in Bugzilla are Fennec M1..

I don't see any valid reason for using the extra prefix "Fennec " in milestones, and would like to remove it. (searching for fennec m1 can be done by using product:fennec, milestone:m1)

[Core] Widget: Qt   	 [e-mail]   	 [e-mail]
Mapping of cross platform widget interfaces to Qt platform APIs.

already existing (which perhaps should have been renamed?)
Ports: Qt 	[e-mail] 	[e-mail]
Bugs that occur only in the Qt version of Mozilla, but not in other versions like the Gtk one. Sample Bugs: Printing does not work in the Qt port; Images don't show in the Qt port. Unless you know it's a Qt bug, don't file your bug here!

not created (or possibly already destroyed):
[Core] Widget: Symbian
[Core] Widget: Windows Mobile