Moving LibQGit2 under libgit2 "organization" in GitHub?

[akikoskinen]

There is this C++/Qt language binding library for libgit2, that is also mentioned on the libgit2 website: LibQGit2. There hasn't been much interest in that project and it has stagnated for a few years now. Currently it uses libgit2 API from version 0.22. But: it is about to be resurrected and patches exist (not yet pushed) already that adapt to libgit2 API version 0.27.

I'm writing this issue because LibQGit2 is currently hosted in the KDE infrastructure. During the past three years I and one another guy (with whom I was working) are the only contributors to the LibQGit2 project. I can say pretty strongly that the project was bequeathed to me.

I don't see any benefit in having LibQGit2 in the KDE infrastructure. I would propose that the repository shall be moved under the libgit2 organization in GitHub – just like pretty much all the other language binding libraries are. Could this be achieved? What would it mean in practice, politically and otherwise? Would it make libgit2 somehow (differently than currently) endorse LibQGit2 or something?

[ethomson]

Hi @akikoskinen - this is a really good question. The status quo here is that we have several bindings that are within the libgit2 organization under GitHub (rugged, LibGit2Sharp), and several that are not (NodeGit).

If you want to move LibQGit2 over to GitHub, I certainly have no strong opinions. However, it's an interesting question whether LibQGit2 should be underneath the libgit2 organization or not.

My thought is that it's a bit of a historical anomaly that we have rugged and LibGit2Sharp hosted under the libgit2 organization. rugged, for example, was maintained by vmg, who was the libgit2 maintainer, so it made a lot of sense. LibGit2 wasn't managed by vmg, but was similarly close to libgit2 in terms of hackers working on both.

But subsequent bindings have created their own organizations, which I think makes a certain amount of sense. I have periodically thought about moving LibGit2Sharp out, but I haven't done so. We should give this some more thought about what to do with LibGit2Sharp and rugged.

In any case, my initial thought is that you should either put LibQGit2 underneath your own account or create a new organization directly for LibQGit2. Either means that you get more direct control over the management of the project. We'll continue to chat about this and we can always move you in to the libgit2 organization later (and we can even get redirects from the old location to the new).

Does that sound like a reasonable start?

[akikoskinen]

Based on the reply, an own organization seems like the correct thing to do. And I just did: https://github.com/libqgit2/libqgit2

That shall be the new home for libqgit2. I will probably still keep the KDE repository updated as well, so it'll act as a mirror. But development discussion will now be open and kept in GitHub.

[ethomson]

👍 Thanks for working on this @akikoskinen, excited to see what's coming next for LibQGit2.

[pks-t]

I'm marking this discussion as closed, as it seems like you to guys figured out the best way to handle this. Feel free to reopen it, though, in case you want to further the discussion.