Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming this Repository #21

Open
clarkegj opened this issue Nov 4, 2020 · 2 comments
Open

Renaming this Repository #21

clarkegj opened this issue Nov 4, 2020 · 2 comments

Comments

@clarkegj
Copy link

clarkegj commented Nov 4, 2020

In preparation for the release of GEDCOM Version 7 we would like to use the FamilySearch/gedcom repository which is now being used for code relating to parsing GEDCOM. I have the names and emails of all the contributors so they can be notified of the change 30 days before it happens. Jimmy Z. suggested naming it GEDCOM5-java so that GEDCOM is available for a public version of the next version of GEDCOM and beyond. Please share thoughts.

@clarkegj
Copy link
Author

clarkegj commented Nov 6, 2020

I letter was sent to all collaborators that we had emails for that said:

"GEDCOM Parsing Collaborators.

In preparation for the next release of GEDCOM we would like to use the FamilySearch/gedcom repository which is now being used for code relating to parsing GEDCOM 5.5.1. We will be renaming the repository GEDCOM5-parsers so that GEDCOM is available for a public version of the next version of GEDCOM and beyond. This will be still searchable in GITHUB with the string of “gedcom”. There will also be a note in the readme when the new gedcom repository is created that explains that the repository formally named “gedcom” is now named gedcom5-parsers.

@michelesalvador
Copy link
Contributor

The name FamilySearch/gedcom5-parsers seems consistent with other FamilySearch repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants