Contents |
Get Involved
We appreciate all the help that goes into this project to make F-Spot great.
There are many ways to get involved with F-Spot. The first and easiest approach is to translate.
Translate
F-Spot is an internationalized program translated into many languages. If you are fluent in a language other than English, we can use your help.
You can track the translation status of the application and its manual here.
Please don't submit translations to bugzilla. Gnome translation is organized in teams. If you feel the translation of your language is outdated first contact your translation team and get in touch with them, then start translating!
Document
Another big help you can do is document F-Spot. Developers often have very short time, and spend that in coding new features or fixing bugs. The result is that user manual is often outdated or imprecise.
This website is a wiki that you can edit. Ask for an account on the mailing list or on IRC. There is also a budding Gnome-based documentation effort.
Test development and/or patches
Development version is updated quite often, and contains latest bleeding edge code rich of new features and fixes for existing bugs.
A big help you can give to the project is constantly update and build GIT version and try normally using it. In case you discover malfunctions or misbehaviours you can report a new bug or contact developers on IRC.
Running SVN is encouraged in test environments only. Code can be unstable, not working, or even damage your data, so using it on your main collection is strongly discouraged.
Once you've set up the test environment you can search for untested patches attached to bugs, and report back directly there your experience on that fix. Help in testing patches is available at here.
Report Problems
If you get a crash, misbehaviour or find room for improvement idea please file a bug and attach a detailed trace.
In case of error please attach a log of f-spot --debug to the bug, and steps on how to reproduce the problem. Usually last lines before crash are enough for digging the problem, but in case you prefer pasting the whole log save it to a file and attach it to the bug.
Before entering a new bug perform several searches. We know it's annoying, but it's also annoying and time-consuming for developers to identify the same bugs.
Often submitted bugs for releases have already been fixed in development version, so common suggestions could be:
- use different search terms
- search in bug title but also in bug content! Often searching for the first line of the crash exception in the bug comments will find bugs that have unrelated title
- search among open bugs, and if fails in closed ones
Please always open one bug per issue. If you experience different problems open different bugs!
Develop
F-Spot is written in C# on the Mono platform and released under the GNU GPLv2.
Few advices advices:
- Read the HACKING file for coding style and standards
- Check out bugzilla for ideas
- Get in touch with F-Spot community on mailing list and IRC
- Submit patches by opening a bug and attaching them
- Extend F-Spot by writing your own custom extensions
Propose New Ideas
F-Spot has a great list of features already, but to push the cutting edge of photo management, new ideas are always welcome. Please file an enhancement bug, e-mail the list, or edit the new features page of this website.
Patches should always be posted on bugzilla, and never in mailing list.
Maintainers
Larry Ewing, Stephane Delcroix, Gabriel Burt
In memory of Ettore Perazzoli.
