Changes

; ===Improved [[:Gramps_and_GEDCOM|GEDCOM]] import and export: ===It seems that no matter how hard we work at [[:Gramps_and_GEDCOM|supporting more GEDCOM attributes]], there is something that always needs to be improved. If you are a GEDCOM expert [[:Contact|contact]] the developers.; ===Resolving bug reports: ===Bug reports arrive all the time, often several a day. Resolving bug reports is a major way in which you can help the team to be able to spend more time enhancing the system. See [[Bug triage]]; ===Profiling the application on large datasets, and speed improvements: ===See [[Gramps Performance]] and [[Tips for large databases]]; ===Streamline the import of data & and merging of duplicates: ===if more sources are used and data is imported from those sources, it is sometimes very hard to find duplicate data.

; ====Develop database test cases: ====We need sample databases that handle all the features of the program. If possible, expand the [[Example.gramps|example]] data file.; ====Help with interface testing: ====Either testing the interface by hand, or help writing [https://gitlab.com/dogtail/dogtail dogtail] tests for automated testing.; ====Identify problems : ====If you encounter a bug, [[Using_the_bug_tracker|file a good Bug Report]]. Filing a unique &ampand; reproducible Bug Report is an enormous help.; ====Validate aging Bug Reports : ====As new releases enhance Gramps and address known problems, it is helpful to confirm old Bug Reports are still be valid. It is best to validate your own Bug Reports first and amend with any new insights.

Help us identify where the Gramps interface, workflow &ampand; documentation could be more intuitive or flow more naturally.

: Some specialty documentation:<br />* [[:Category:How do I...|How I do ...]], * [[:Category:Tutorials|Tutorials]], * [[:Category:Tips|Tips]], * [[:Category:Screencasts|Screencasts]].

: As a user, you can best explain how you go about its use. And sharing this knowledge is a great thing to do. An interesting side effect of writing documentation is that it causes you learn the features more fully and learn how to take better advantage of them.

: The more you use Gramps, you will gain more &ampand; more knowledge of the reports, how they work, and how they can be made better. Expanding the [[:Gramps_{{Version manual}}_Wiki_Manual_-_Reports|Reports]] documentation will make the original learning curve less steep for other and easier for you the next time.

Share how you use Gramps by showing others. [http://www.unixuser.org/~euske/python/vnc2flv/index.html vnc2flv], [http://recordmydesktop.sourceforge.net/ recordmydesktop], [http://www.tortall.net/mu/wiki/Cankiri Cankiri], [https://www.lifewire.com/how-to-capture-a-screencast-using-vlc-2533002 VLC], [http://xvidcap.sourceforge.net/ xvidcap], gifsicle or [http://www.swftools.org/ SWFTools] programs can be used to create screen movies that could be used to show people how to perform different tasks. [http://imagination.sourceforge.net/ Imagination] and [http://www.openshot.org/ OpenShot] could help us to generate a video with some screenshots addition. Also see the list of screencast tools on [http://en.wikipedia.org/wiki/List_of_screencasting_software wikipedia]