If this is dead, please tell us

[KlomDark]

Haven't seen any pull requests accepted in years. This is my favorite, but if it's dead I'd better start looking for something else.

Anyone know of active/supported forks of this?

[dauheeIRL]

looks dead. I can see a fork that upgraded to .NET 4.8 a couple months ago but thats it

[polymo1]

Now at 3 years no commit, I'd say this is abandoned based off of the number of issues and pull requests.

[latop2604]

We miss the transition to dotnet core.

I did a poc some years ago but the razor part was too dependent on the external libs. And it was too much to recreate the ui part.

Also the AD feature make it hard to test.

[latop2604]

This fork seem to be the most recent one https://github.com/Pepperdine-University/Bonobo-Git-Server/tree/Code_Review_2023-09-26

[willdean]

This was not originally my project, but I think I'm one of the last people to commit anything or make a new release.

The story of why this is not maintained is not really anything exceptional - it's much the same for all OSS.
Here are some bullet points, in no particular order:

• The original maintainer is gone
• I'm very busy, and I long-ago fixed the problems which were bothering me and why I got involved in the first place - other contributors have drifted away too.
• The typical quality of unsolicited PRs is, to my mind, low - so if I was to merge one I would have two tasks: rewriting to a reasonable standard and/or negotiating with the original author (who feels they're doing you a favour). People who have not been maintainers on OSS projects often do not appreciate what a problem this is, particularly once the code has already become ill-disciplined: it becomes harder and harder to maintain any quality.
• My feeling is that there has been a huge reduction in interest in running your own on-prem Git server - most people are using Github or Bitbucket or whatever - this means there are far fewer potential contributors
• Past maintainers have not really been very focussed on either restraint when considering extra features or consistent coding approach - so there's a terrible mix of styles and standards.
• Prior to my involvement I think there was a really, really terrible mistake made where AD users where hived-off into their own homebrew database and stored in a completely different way to non-AD users - this has been an absolute pain, particularly given the next point...
• As @latop2604 says, AD is a nightmare to test- if you don't use AD you can't simply fire-up an AD server without screwing-up your network, and if you do use AD then it's probably running your business and you can't fiddle-about with it to support testing your hobby-project. I don't know how people (used to) test apps which integrated tightly with AD, and doubt anyone is writing any more of them nowadays anyway. I think this is why so much of the AD code in Bonobo has been drive-by: people did what they needed to make something work and then ran away, perhaps screaming as they went.
• There are a bunch of dependencies on Git and Git integration libraries which are now very out of date.
• We, totally unnecessarily, support multiple RDBMS for the (trivial) internal database, probably (it's before my time) for no good reason other than that someone who was enthusiastic said that would be a cool thing to do. Doubling the test matrix in the process.
• .NET Core happened - which first created some terrible years to build .NET applications where nothing worked properly - and now that the dust has settled and .NET is great again, there is a huge gulf of time separating us from our dependencies.

I am aware of all the reasons people like Joel Spolsky say you shouldn't re-write software from scratch, but if I needed something like Bonobo which wasn't the current version of Bonobo, then I would start again. My version might not have a web-UI at all. It would serve Git over HTTPS and use a JSON file to associate users and their repositories.

It's not my place to tell you that the project's dead, because it's not my project: you'll have to draw your own conclusions there. Just as you should for all other OSS projects.