Consider moving dgit from my account to github org?

[driusan]

Now that there's more than 1 person actively contributing, it might be worth moving the repo from directly under my account on github to a new dgit org. This would have the advantages of:

1. My changes won't get special treatment (which right now can result in me accidentally breaking the build.)
2. My dev and the master branch won't get intermingled
3. It would look more professional/mature which could potentially attract more developers
4. There would be an obvious place for related repos such as the proposed 9p server.

The disadvantage is that rewriting the import paths everywhere would be a bit of a pain, and we'd need to point people to the new location from here, but I don't think there's such a large userbase right now that that would be too onerous if it's a one time thing.

[driusan]

Slight hiccup with this plan: the name is already taken by another user.

[sirnewton01]

I hadn't considered an org for this, but I think it makes a lot of sense for the reasons you gave. The pain should be pretty minimal, especially if we keep this repo around and point people to the new place. According to godoc, it is not aware of anyone else referencing the git package. Now might be a good time.

https://godoc.org/github.com/driusan/dgit/git?importers

I think that time-wise we could get some more of the test suites added to travis in #63 and have them consistently passing. It will make the project look quite legitimate that it has hundreds of official git test cases passing with it.

[sirnewton01]

How about sgit? The organization name isn't taken yet.

[sirnewton01]

Another option is to name the organization go-git or something else and then the repo remains dgit.

[tie]

Why not go-dgit? That will make possible the use of gopkg.in in the future.

The advantage of using gopkg.in is that the URL is cleaner, shorter, redirects to the package documentation at godoc.org when opened with a browser, handles git branches and tags for versioning, and most importantly encourages the adoption of stable versioned package APIs.

Repositories in GitHub that have no version tag or branch matching the pattern described above are also considered unstable, and thus gopkg.in takes their master branch as v0. This should only be used once the package maintainers encourage the use of gopkg.in, though.

[driusan]

I'm not a huge fan of go-prefixes, but that's a good idea @b1narykid, and at least out wouldn't be exposed on the command line level

[sirnewton01]

Perhaps the org name could be used to add a hint/wink to Plan 9. Maybe something like 9git?

[sirnewton01]

If this moves to an org, I would also like to eventually move my https://github.com/sirnewton01/ghfs to the same place.

[sirnewton01]

I wonder if 9fans would be a good place for this?