|
<
< |
| META TOPICINFO | TommiKomulainen | date="1090187572" format="1.0" version="1.5" |
|---|
|
>
> |
| META TOPICINFO | TWikiGuest | date="1122606789" format="1.0" version="1.6" |
|---|
|
|
Galeon Development
|
|
<
< |
Bugs
|
>
> |
Bugs and Suggestions
|
|
|
|
<
< |
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.
|
|
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.
|
>
> |
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.
|
|
|
|
>
> |
Developing Galeon
|
|
|
|
<
< |
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.
|
|
|
|
<
< |
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.
|
|
|
|
<
< |
- 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.
|
|
|
|
<
< |
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
|
|
|
|
>
> |
|
|
|
|
<
< |
<!-- "discussion" below -->
|
>
> |
Submitting patches
|
|
|
|
<
< |
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").
|
|
|
|
<
< |
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.... 
|
>
> |
- 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.
|
|
|
|
<
< |
 what does "Bugzilla lists" mean in practice?
|
|
|
|
<
< |
I thought about adding links to the bug reports and the enhancements.
|
>
> |
 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.
|
|
|
|
<
< |
| META TOPICINFO | TommiKomulainen | date="1090140569" format="1.0" version="1.2" |
|---|
|
>
> |
| META TOPICINFO | TommiKomulainen | date="1090151058" format="1.0" version="1.3" |
|---|
|
|
Galeon Development
|
|
<
< |
Submitting patches
The Galeon source is constantly changing. If you want to submit a patch, please do so from the most recent CVS source tree, subscribe to the galeon-devel mailing list and post your patch with a description of functionality.
If you want to contribute to Galeon, but don't know what to do, there a lots of bugs and features requests in bugzilla. In addition GaleonPlan has a list of other changes that the developers would like to do.
|
|
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 a lots of 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.
|
|
<!-- "discussion" below -->
This is just a quick outline of the stuff that needs to go in here:
|
|
<
< |
|
>
> |
| META TOPICINFO | TommiKomulainen | date="1090140569" format="1.0" version="1.2" |
|---|
|
|
Galeon Development
|
|
>
> |
Submitting patches
The Galeon source is constantly changing. If you want to submit a patch, please do so from the most recent CVS source tree, subscribe to the galeon-devel mailing list and post your patch with a description of functionality.
If you want to contribute to Galeon, but don't know what to do, there a lots of bugs and features requests in bugzilla. In addition GaleonPlan has a list of other changes that the developers would like to do.
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.
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.
<!-- "discussion" below -->
|
|
This is just a quick outline of the stuff that needs to go in here:
|
|
<
< |
- Point to galeon-devel
- Link to the plans here
|
>
> |
|
|
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.
|
|
-- CrispinFlowerday - 17 Jul 2004
|
|
>
> |
what does "Bugzilla lists" mean in practice?
-- TK
|
