I would like to make another call for help with gramps development.
This is a particular this moment's need, not some crazy wishlist.
We need help with handling bug reports. No, you don't have to
know python or be able to program, but if you can that does
Here's the typical scenario of the bug report development.
Some are better, few are worse, but this happens quite often:
1. The user reports a problem in a form that is either not
clear or clear but not incomplete, or just not reproducible.
2. The developer follows up trying to understand what is
These two steps can go forever, and this wastes a lot of
developer's time. So we could really use some help with
triaging the bug reports.
When I have little time to work on bugs, I want to see the
problem in front of me. Instead I spend at least an hour every
day trying to follow up on the bug reports to extract the
information about the problem. More often than not I spend
this time trying to make guesses as to what the problem is.
Most of the guesses are incorrect, because there's only one
correct scenario for every bug :-)
For instance, when there's a report saying "gedcom export
from gramps has such and such problem", I need to be able
to see it. I don't doubt that the submitter had the problem,
but I need a testcase. In this case, a gramps file that
shows the problem (unless any file shows it).
When the report says "page size is incorrect in format X"
I want to see the file created by gramps with the incorrect
page size, and so on.
So we could use the help of an unlimited number of people.
All that's needed is to go through the bugs as the time
permits and see if the problem is reproducible. If it is
reproducible, then add a short note saying how. If not, ask
the submitter to submit enough data/information for a human
being to reproduce it. If the report is obviously complete
and clear then do nothing.
Also, some bugs are sent to gramps-bugs mailing list.
Unless a recurring issue, those should be entered into the
tracker, the submitter contacted for help, etc.
In other words, these are purely chores of communication,
not programming. If you help us with that, we will fix more
bugs and make better gramps.
We often hear many thanks from the users for developing gramps.
If you think you benefited from gramps and can give something
back, you have a very good chance. Go to http://bugs.gramps-project.org
and go through the bugs that seem like they can use help.
Alexander Roitman http://www.gramps-project.org