Is this project still active?

[zeripath]

The last commit to this project was 1 November 2019. Is this project still under active development?

[filipnavara]

I am a bit concerned about it too. Source-d, the company behind the project, went dark around 4 months ago without any official news explaining what happened.

[filipnavara]

I tried to find more information but there's not much to report. All the previous maintainers of this project are no longer listed on src-d organization. Source{d} went dark last November, disappeared from all social media, the site is down and the community Slack (which is no longer accessible for new members) has no further information either. At this point I think the only reasonable course of action is to fork this project.

cc @jfontan @smola @mcuadros ... I don't expect any official information or blessing but if there's anyone who could shed a little bit of light on this and say some yay/nay on the fork it would be appreciated.

[mcuadros]

Hi everyone.

Yes, this project is still active @smola, @jfontan, and I will maintain the project.

The problem was that in November source{d} went bankrupt, and this repository felt in a legal void. Actually, none of us has merge rights anymore. But don't worry we are figuring out how to tackle this problem, as a hard deadline this will be cleared in mid-March.

I co-founded a new company, and this company will be the official maintainer of go-git. But we are open to any other IC or company willing to maintain the project with us.

We will move the repository a new organization, but we need to resolve the legal issues about the repository itself and see if we can move the repository there, or we need to do a hard fork losing all the issues and PRs, but we want to avoid this as much as possible.

This will be solved in mid-March, since the new company is initiating the activity in the next weeks and our project relies heavily on go-git.

Meanwhile, you can find me in gophers.slack.com

Thanks for the patience

[zeripath]

Hi @mcuadros !

Thank you for the update.

You must have had a terribly stressful and frustrating few months. I hope things are settling down a little.

If you can, please keep us informed. I'll suggest Gitea makes a mirror of this repo in case things go awry in the meantime.

[mcuadros]

Thanks for caring, but don't worry, things happen!

We have the hard fork at https://github.com/go-git/go-git but we don't want to update anything since if we need to do the hard fork, we will merge the PRs and after that update all the paths from the library.

So I suggest you hold any movement for two weeks, this should be more than enough. This next week we are going to take the decision and during the next week we are going to take the actions need it to make this project maintained again.

[lunny]

@mcuadros Thank you for your efforts on this project.

Since gitea support to migrate with issues/prs/comments/reactions and many of others, I think you can consider migrate to a gitea instance. If you don't want to set up a new one, you can migrate it to https://gitea.com or other public gitea instances.

Gitea has used some parts of this library and would like to use more if it's maintained actively. Gitea depends on many talent go libraries and we don't want to maintain most of them ourselves if they are maintained well.

[tebrizetayi]

@mcuadros I am excited to contribute to go-git project. Do you have any slack channels for team conversation? How to begin?