6.0 Roadmap
From Gramps
|
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.3 version of Gramps
Contents
Schedule
| T.B.A. | Agree final roadmap (this document). |
| T.B.A. | All major features should be merged into master. |
| T.B.A. | Feature freeze. |
| T.B.A. | String freeze. |
| T.B.A. | Final release.* whoosh!! |
Policy changes
Project governance
At present, we use a benevolent dictator model. The BD defines the project's strategic direction and has the final say in decisions.
Dependency upgrades
- Python 3.9 (3.8 will reach end of life status in Oct 2024.)
Database model changes
Are there features that require database change? This should happen in the beginning of the development cycle. List your requirements here.
Major goals
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.
Minor goals
This section lists minor goals developers want to achieve. Minor goals can be done by one developer alone.
Suggestions:
- 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. [1] GEPS 009: Import Export Merge: UID, GUID and _UID, what is needed in Gramps?
- Lossless GEDCOM Export - Custom GEDCOM tags required to round trip import/export via Gramps to GEDCOM to Gramps!
- 12874: Translations/gettext - make context the norm [2]
