Community

Quick Links

Getting Started

The GEDCOM X project is maintained at Github, allowing us to leverage the powerful collaboration features that Github provides.

If you haven't worked with Git yet, now's the time to start! (We promise, you'll never go back.) Github has accumulated a lot of great resources on how to get started at github:help. Get familiar with the Github M.O., and take particular note of how to fork a repo, how to send a pull request, and how to be social.

To get started with Git, we'd recommend Pro Git.

Connecting With The Community

Well, the first thing you'll want to do is make sure you're watching the project. You might even be interested in following some of the people involved in the project.

The project has a blog to which news, announcements, and other articles are posted.

Got a question? Try searching the issues database, the stack overflow feed, or browsing the modeling recommendations. But don't be shy if your question still isn't answered! We recommend that you put your question in the form of an issue and submit it so we can discuss it. For example, if you've got a question about something regarding source references, create a new issue entitled "clarify source references regarding ..." and put a statement about what needs to be clarified in the description. There is always room for another recipe request.

We don't have a mailing list. Yet. If you feel like you'd like to take a stab at convincing us that we need one, leave your comment on issue #42

GEDCOM X Development Platform

GEDCOM X is defined by its set of [specification documents|Specs], which are maintained at Github. The official GEDCOM X repository is established by FamilySearch at FamilySearch/gedcomx. Issues are managed by the issue tracker. Documentation is managed by the wiki.

Contributing Patches, Proposals, and Extensions

If GEDCOM X is missing something, please consider making it better! Don't be shy about forking the repo and sending a pull request. Also use the issue tracker to open up and issue and start a conversation. For larger changes (such as a new extension proposal), you may need to create a new document on the wiki that defines the formal proposal.

And there's always room for another recipe.