There is no registration required to read this wiki or download and install Gramps. You only need an account to edit this wiki.
This is a guide only.
Because of the nature of a volunteer-driven project, it isn't possible to say with any certainty what will happen in the next release.
This page collects possibilities for the 5.2 version of Gramps
|T.B.A||Agree final roadmap (this document).|
|T.B.A||All major features should be merged into master.|
At present, we use a benevolent dictator model. The BD defines the project's strategic direction and has the final say in decisions.
- Python 3.5.x (as 3.3.x reached end of life status on 2017-09-29.)
- Gtk 3.12.x EmailIt looks like we should just move from 3.10 to 3.12 then. Nick. (3.10.x reached end of life status on 2014-05-12.)
Database model changes
Are there features that require database change? This should happen in the beginning of the development cycle. List your requirements here.
- Enhancements to the place structure to support GEDCOM-L PLAC tag
- Allow multiple place Types with date for each
- Deal with 200+ place types
- Allow multiple postal codes and other attribute like data, with date for each
- Allow places to have attributes (for above)
Changes to implement the requirements above:
- Add a list of PlaceAbbrev objects. A PlaceAbbrev object should consist of a some text and associated type (PlaceAbbrevType).
- Add a citation list.
- Add a hierarchy type.
- Add a citation list.
- Replace the place type field with a list of LocationType objects. A LocationType object should consist of a date, PlaceType, and citation list.
- Add an attribute list.
- Add an event reference list.
- No change. Type mapping should be done in the import/export code.
This section lists main goals developers want to achieve. Major goals should be started in a GEPS branch. Major goals require a developer and a reviewer.
- GEPS043 Improving GEDCOM support for Places
- GEPS045 Place Model Enhancements
- Store objects as JSON rather than pickled blobs See feature request #9392. Previously discussed on the list. 
- Remove raw methods from database API
This section lists minor goals developers want to achieve. Minor goals can be done by one developer alone.
- Some "attributes" we have currently don't match up well with GEDCOM When Gramps originally was conceived, these attributes did not have dates, places, and media attached (Gedcom did not have these either). The last version of GEDCOM allow this. Dated attribute would help, or just make these into Event/Fact types.
- A method to mark objects as "used" TODO tagged items work like this now, maybe another standard tag?
- A way to attach objects to the database itself Something like the "Researcher"/"Database owner" but including other data. See 6365 & 8734
- 11404 Change location of resource-path file to allow Python pip Wheels. eg: Running a post-install script is not possible with wheels, so it looks like we need another approach. I suggest that we look for the resources in the standard places at run-time. - Nick Hall & Re: (Gramps-devel) tar files, zip files, distutils, etc.
- 6300: Organize Tags be able to select a background color also for visability - This would be quite easy to do, but would require a database change. - Nick H
- 10777 Fulltext search on all elements, objects, items, types which can have a text / string in.
- Support Gedcom _UUID. Two choices 1) extend data model with a list of additional IDs, which would be _UUID or possibly GOVID, GEONamesID etc. 2) Store them in attributes. The former has advantage that they are invisible to users except for tools explicitly using them, also could easily support db lookup like GrampsID. The latter limits work to import/export. Gedcom L group has just completed a vote on how they should work for import/export. Ultimate goal, better merging.