Galeon Development

Bugs

Naturally Galeon is far from perfect, so if you find any bugs, please report them. Please make sure that what you're reporting is actually a BUG and not a problem on your end.

If you want to contribute to Galeon, but don't know what to do, there are a few easy to fix bugs and a whole lot more bugs and feature requests in Bugzilla. In addition GaleonPlan has a list of other changes that the developers would like to do.

Suggestions

If you have a suggestion for a new feature in Galeon, please subscribe to the galeon-devel mailing list, and let us know. If we like the idea, we will ask for it to be reported to Bugzilla as an enhancement, and it might get implemented.

Translations

Galeon can be easily translated into your own language. Translations are handled by the GNOME Translation Project. The best way of contributing a Galeon translation is by joining the team for your language. At least one person in the translation team has access to GNOME CVS and can commit your Galeon translation. When a new Galeon release is approaching an announcement is made to the gnome-i18n mailing list.

Submitting patches

If you have fixed a bug, enhanced some existing feature, or implemented a new exciting feature, don't hesitate to send us a patch. As the Galeon source is constantly changing we would appreciate it to have the patches against the most recent CVS source tree in unified diff format ("cvs diff -u".)

• If the patch fixes a bug, it should be added as an attachment in Bugzilla
• If the patch is a feature enhancement, or adds a new feature, it should be sent to galeon-devel mailing list with a description of the new functionality

In either case, the patch does not need to be complete. If there are some open issues feel free to send the patch to galeon-devel mailing list and we will try to give some feedback as soon as possible.

---

This is just a quick outline of the stuff that needs to go in here:

• Bugzilla lists
• CVS checkins, http://cia.navi.cx/stats/project/gnome/galeon (rss feeds from there)
• Point to galeon-devel mailing list (not too active, all developers are on #galeon)
• Point to #galeon on GIMPnet (most of the development discussion happen there)

We also probably want to change the Support page to Contact, and move all the development stuff from there to here, and add a translating section to the Contributing bit of the SideBar.

Feel free to sort this page out....

-- CrispinFlowerday - 17 Jul 2004

what does "Bugzilla lists" mean in practice? -- TK

I thought about adding links to the bug reports and the enhancements. -- CF