Is this project abandoned?

[jonringer]

Last commit to master was almost a year ago. Last release was almost 2 years ago.

From a python package standpoint, being two years stale makes it hard to continue to maintain this package in package repositories.

[BradKML]

not even sure, but gitless sounded revolutionary.

[sourcedelica]

From the bottom of the home page:

Gitless is part of a research project exploring concept design. This research is part of a collaboration between MIT and the Singapore University of Technology and Design (SUTD), and is funded by a grant from SUTD's International Design Center.

It's PhD-ware. They have probably moved on to other research topics, lost their funding or both.

[goldstar611]

I'm going to see how far I can get using gitless in combination with git-worktree. I've forked the code and fixed (as far as I can tell) 2 bugs so far. https://github.com/goldstar611/gitless

[sirlucjan]

@goldstar611

Thanks for taking on such a difficult task, well done.

[spderosso]

Last commit to master was almost a year ago. Last release was almost 2 years ago.

From a python package standpoint, being two years stale makes it hard to continue to maintain this package in package repositories.

Unfortunately I don't have much time to work on Gitless actively anymore. I'd be happy to create a new release if someone makes a contribution.

I'm going to see how far I can get using gitless in combination with git-worktree. I've forked the code and fixed (as far as I can tell) 2 bugs so far. https://github.com/goldstar611/gitless

@goldstar611 this is amazing, thank you. Switching to using git-worktree instead of stashing for keeping branch independents will be a huge perf boost. Let me know if I can help with something.

[chenrui333]

Any timeline to make a release to keep the train going?

[FlorianHeigl]

@spderosso it's silly but after reading the paper many years ago i was so frustrated that the git community didn't simply pick up on this and gave users a hand to a better experience. so i forgot. then found it again when researching for ways to remove errors in (Dev)Ops envs, since there's quite a difference between build failures on Dev and env failures on Prod. And now, 4 or 5 years later I finally cared enough for myself to just install it and i see it's under threat of staleness...

Could you:

• make @goldstar611 co-maintainer asap? if he tries the work, he should have the involvement
• add a fundme button so if there's user interest there's an option to contribute monetary

it might have the following benefits:

• to at least remove partially a constraint (but without any commitment expected to work on the project. consideration if you feel like working on it a moment. and if not, not)
• at least you could have benefits from your past work
• it could (and that's a good one) fairly cover the time you'd spend on doing releases or triages
• it'll enable to also thank further contributors

That all together could make the project sustainable in a fair manner. As long as people care to keep it sustainable. and if they don't - no problem to think about.

[weakish]

i see it's under threat of staleness As long as people care to keep it sustainable.

Fortunately, spderosso mentioned that "I'd be happy to create a new release if someone makes a contribution." :heart: It just need more loves from users to send pull requests.