Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Time for my monthly whine, where I ask for help from the user community.
The following is a list of tasks that we need help with that do not
require any programming experience. If you can help out, please contact
GRAMPS TODO List for Non-Programmers
The manual needs significant work to bring it up to speed with the
current version. A lot of features are not mentioned in the manual.
There are a lot of functions in the program that need some
clarification for the average user. A nice step by step guide on how
to accomplish certain features would be good.
* GEDCOM testcase development
GEDCOM files come in many different flavors. No two programs
produce the same GEDCOM, any most generate invalid GEDCOM or GEDCOM
with custom extensions. We need a wide variety of test cases that
we can keep for testing purposes. These need to be fairly complete,
exercising the full set of options each program can generate.
* XML test case development
A good XML file needs to exist that exercises all features on the
GRAMPS XML database. The current files (in examples/gramps) are
lacking with Source and Repository information.
* CSS style sheet development for web page generator
Additional style sheets for the web page generator are always needed.
We need several more high quality style sheets.
* Web page optimization
Examine the web page output and look for optimizations that would
reduce the file sizes.
* Packaging for different distributions
We have most of the major distributions covered, but the more
packages we have available, the better off we are.
* Test Plan development
Develop a test plan to identify step by step which items need to be
* Automated testing (dogtail)
Develop scripts for dogtail that will allow automated testing of the
interface. The scripts should be based off the Test Plan.
Translations are always needed. The more language support we have,
the better of we are.
* Bug verification
Monitor the bug reports both on the mailing lists and on the bug
tracker, and verify that bugs are actually bugs. Collect any
additional information you can get to help the developers duplicate
the problem. Look for duplicate bugs and identify them.
* "Expert" on the mailing lists
Right now, the developers seem to be the only one who answer
questions asked on the mailing lists. Participate in the mailing
lists, answering questions asked by users.
* IRC participation
Participate in the IRC channel (#gramps on irc.freenode.net). Help
new users with questions and discuss issues with the developers.=20