Re: [janusgraph-foundationdb] initial fork options


Misha Brukman <mbru...@...>
 

I'd like to propose another option:

4. Ask Ted & Expero if they wouldn't mind transferring the initial repo experoinf/janusgraph-foundationdb into the JanusGraph org as-is so it becomes the authoritative home (rather than forking it), and then each of the existing fork owners can propose PRs to merge their changes incrementally into the new base repo.

On Tue, Jun 16, 2020 at 10:14 AM Jason Plurad <plu...@...> wrote:
For the new janusgraph-foundationdb repo, we need a starting point. Here are a few options:

1. Fork from experoinc/janusgraph-foundationdb into JanusGraph/janusgraph-foundationdb. The external fork authors submit PRs with their changes to the new repo, and the code changes will be reviewed before commit.

2. Fork from one of the external janusgraph-foundationdb forks into JanusGraph/janusgraph-foundationdb. rngcntr/janusgraph-foundationdb has the most commits among the three. The other two forks would submit PRs to the new repo.

3. Have the 3 authors merge their forks first, then fork the unified fork into JanusGraph/janusgraph-foundationdb. This could provide a unified repo before imposing code review process.

I haven't reviewed any of the code out there, so I don't have a strong opinion on any of these options. Open for more ideas or suggestions from the authors, committers, and others in the community.

-- Jason

--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/ed630d2d-cf9d-44ab-85d4-27042208e932o%40googlegroups.com.

Join janusgraph-dev@lists.lfaidata.foundation to automatically receive all group messages.