vfwlkr, the code might not be completely different, but it's forked. The Firebird code (e.g. nsPasswordManager.cpp) is in mozilla/toolkit/components/passwordmgr/, whereas the SeaMonkey code is in mozilla/extensions/wallet/src.
Besides, bug 117592 is about a design decission (do we want this for Firebird as well?), and the answer might be different from SeaMonkey, so I guess it would be a good idea to file a Firebird bug.
Firebird patch reviews/checkins?
-
KaiRo
- Posts: 102
- Joined: November 11th, 2002, 5:10 am
- Location: Austria
- Contact:
It seems that nowadays Seamonkey has a more community-friendly development - also in UI - and has more coordinated development progress (yes, even in UI).
BTW, I'm quite sure that as long as FB has such a closed development model, it won't attract enough developers, as most of them will stay with Seamonkey development.
I believe the change to seperated apps would be a nice thing, but I don't want to give up the basically good develpoment model that Seamonkey currently has.
Well, I guess I'm talking to the wrong people here... Where are those more and more mystical FB devs, if not disappeared?
BTW, I'm quite sure that as long as FB has such a closed development model, it won't attract enough developers, as most of them will stay with Seamonkey development.
I believe the change to seperated apps would be a nice thing, but I don't want to give up the basically good develpoment model that Seamonkey currently has.
Well, I guess I'm talking to the wrong people here... Where are those more and more mystical FB devs, if not disappeared?
-
bernd
- Posts: 9
- Joined: October 26th, 2003, 1:44 am
Thanks to <a href="http://www.squarefree.com/">J. Rudermann</a> to link to this thread.
The shortcomings and advances of the strong ownership model are <a href="http://weblogs.mozillazine.org/mt/mt-comments.cgi?entry_id=3317">well known</a>. I see the wish to contribute code and how it clashes with the aim to keep the development team small and manageable. This aim is visible from the <a href="http://lxr.mozilla.org/mozilla/source/browser/README.html">very beginning (see Q5)</a>. So my guess is in order to become a fb dev you first need to become a know coder (cvs write permission), once you have this and you show your coding skills you will be admitted to the frontend stuff. If you dont want to go this path you always have the possibility to write an extension.
The shortcomings and advances of the strong ownership model are <a href="http://weblogs.mozillazine.org/mt/mt-comments.cgi?entry_id=3317">well known</a>. I see the wish to contribute code and how it clashes with the aim to keep the development team small and manageable. This aim is visible from the <a href="http://lxr.mozilla.org/mozilla/source/browser/README.html">very beginning (see Q5)</a>. So my guess is in order to become a fb dev you first need to become a know coder (cvs write permission), once you have this and you show your coding skills you will be admitted to the frontend stuff. If you dont want to go this path you always have the possibility to write an extension.
-
alanjstr
- Moderator
- Posts: 9100
- Joined: November 5th, 2002, 4:43 pm
- Location: Anywhere but here
- Contact:
Even longtime Seamonkey devs aren't necessarily allowed to make change to Firebird.
Former UMO Admin, Former MozillaZine General Mod
I am rarely on mozillaZine, so please do not send me a private message.
My Old Firefox config files
I am rarely on mozillaZine, so please do not send me a private message.
My Old Firefox config files
-
mconnor
- Posts: 75
- Joined: September 15th, 2003, 10:17 am
move along folks, nothing to see here
/me goes back to working on UI for new cookies features
/me goes back to working on UI for new cookies features
- Mike
Zarro Bugs Found
Zarro Bugs Found