-
Notifications
You must be signed in to change notification settings - Fork 101
Is this project dead? #797
Comments
there is a very active Fork of it: |
@aligator Isn't it the same project like this here? |
@aligator Ah no sorry. But the same Discord group right? |
its a fork, means its the same project + several more commits. Thats how opensource works. If in opensource someone stops maintaining a project (like in this repo) anyone else can create a fork and maintain it on its own (like paulwedeck seems to have done it here). As currently the Paulwedeck fork is ahead 400+ commits, just use that. Edit: there you can see if other forks are more active. |
And original devs are still reading in this repo, in case you have any questions about the "old" code ;-) |
So, I take from all this that this "official" / "original" here is dead? The fork has neither newer releases nor an issue tracker. |
Nobody is actively developing. If you want to, you can do development, ask questions, send PRs. We are always open to that. But the original devs have moved to other projects, so the project is "dead" but not completely abandoned. |
@foobar13373 I wasn't aware that forks don't have an issue tracker by default but mine has one now. I am planning to publish a release but that will still take some work. |
I wonder if it’s worth linking/redirecting to a more active fork such as @paulwedeck’s version than have people thinking this project is dead. I don’t see anyone PRing to this repo if it’s inactive and fragmenting effort like that doesn’t sound efficient. It’s always helpful to signal to users and contributors what the situation is. Even if it’s just a few words on the front page readme. |
Last commit is almost 2 years ago. However, nobody seemed to made it officially that is is dead.
(It's ok to stop working on a project, being a freetime project after all, but please don't leave the community in an undefined state. Too many projects do this lately, just leaving without further notice...)
The text was updated successfully, but these errors were encountered: