Re: [jgrapht-users] moving source control to github, and build to Maven

[John S. <js...@gm...>]

On Sun, Apr 8, 2012 at 3:43 PM, Oliver Schrenk <oli...@gm...> wrote:
> I don't want to step on anyones toes here but wouldn't it be better to move the jgrapht project to it's own organization? Or is this overkill as there probably will only be two projects jgrapht  itself and maybe jgrapht.github.com (for hosting the project page)?

You're right, that would be better (I so look forward to the day I can
add some team members!).  I've created a new jgrapht organization and
forked it over to there (after merging your pull request), so now the
repository everyone should submit pull requests against is

https://github.com/jgrapht/jgrapht

I will create a jgrapht.github.com repository as part of moving the
website content over.

> Also I was confused to see jgrapht as a fork from rcpoison/jgrapht. I understand why this is the case but I think it should be the other way arround.

Well, Andreas (rcpoison) did the initial work, then Owen started
helping, and then I needed to set up the primary repository, so I
forked from their work.  The alternative would have been to do a fresh
import of the tree, but github discourages that when there's already a
place to fork from.  So I think those old repositories can just be
considered prehistory and ignored now.

Likewise for the move I just did from lingeringsocket organization to
jgrapht organization.

JVS