<<O>>  Difference Topic GaleonDevelopment (r1.6 - 29 Jul 2005 - TWikiGuest)
Line: 1 to 1
Changed:
<
<
META TOPICINFO TommiKomulainen date="1090187572" format="1.0" version="1.5"
>
>
META TOPICINFO TWikiGuest date="1122606789" format="1.0" version="1.6"

META TOPICPARENT Home

Galeon Development

Changed:
<
<

Bugs

>
>

Bugs and Suggestions


Changed:
<
<
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 think that you have found a bug in Galeon, then please report it, but please ensure that what you're reporting is actually a BUG and not a problem on your end.

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.

Line: 12 to 8

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.

Added:
>
>

Translations

Changed:
<
<
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.
>
>
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.

Added:
>
>

Developing Galeon


Changed:
<
<

Submitting patches

>
>
Galeon is actively developed, and the main developers hang around #galeon on GIMPnet, which is where the majority of development discussion takes place, although you can also post to the galeon-devel mailing list.

Changed:
<
<
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 you just want to help develop Galeon, and don't know where to start, then 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.

Changed:
<
<
  • 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
>
>
You can follow what is happening in the Galeon tree using the CIA website which has real-time feeds of galeon changes.

Changed:
<
<
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.
>
>

Development Documentation


Added:
>
>

Changed:
<
<

<!-- "discussion" below -->
>
>

Submitting patches


Changed:
<
<
This is just a quick outline of the stuff that needs to go in here:
>
>
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").

Changed:
<
<

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.... smile

>
>
  • 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

Added:
>
>
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.

Deleted:
<
<
HELP what does "Bugzilla lists" mean in practice?

Changed:
<
<
I thought about adding links to the bug reports and the enhancements.
>
>
NOTE If you are coding Galeon and need some help, then IRC is the best place to contact the developers, but be patient, we all have day jobs.


Revision r1.5 - 18 Jul 2004 - 21:52 - TommiKomulainen
Revision r1.6 - 29 Jul 2005 - 03:13 - TWikiGuest
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Galeon? Send feedback.