Remove dead projects #700

Open
opened 2025-11-19 20:58:09 -06:00 by GiteaMirror · 18 comments
Owner

Originally created by @G2G2G2G on GitHub (Oct 1, 2022).

is this removing projects that are dead, like RDPwrap? it never really worked correctly in the first place either

atom text editor is also dead, the team moved to a different text editor called zed https://zed.dev/

Originally created by @G2G2G2G on GitHub (Oct 1, 2022). is this removing projects that are dead, like RDPwrap? it never really worked correctly in the first place either atom text editor is also dead, the team moved to a different text editor called zed https://zed.dev/
GiteaMirror added the curationhelp wanted labels 2025-11-19 20:58:09 -06:00
Author
Owner

@nodiscc commented on GitHub (Oct 6, 2022):

is this removing projects that are dead?

Now it is, officially https://github.com/awesome-foss/awesome-sysadmin/blob/master/.github/PULL_REQUEST_TEMPLATE.md

Any software project you are adding to the list is actively maintained.

Anyone, feel free to send Pull Requests to remove projects that are no longer maintained.

Thanks

@nodiscc commented on GitHub (Oct 6, 2022): > is this removing projects that are dead? Now it is, officially https://github.com/awesome-foss/awesome-sysadmin/blob/master/.github/PULL_REQUEST_TEMPLATE.md >> Any software project you are adding to the list is actively maintained. Anyone, feel free to send Pull Requests to remove projects that are no longer maintained. Thanks
Author
Owner

@G2G2G2G commented on GitHub (Oct 6, 2022):

I looked at RDPWrap and the issues people are keeping their .ini file configs up to date so apparently it still works if you DL the program and go to some random git issue that has the updated stuff correct

Do we consider that dead or alive? lol

I looked into it and seems there is a community fork with "lots of life" so far
https://github.com/atom-community/atom/discussions
https://atom-community.github.io/
Should I update the URL to the github repo or what? Not sure what to do with that one either

@G2G2G2G commented on GitHub (Oct 6, 2022): I looked at RDPWrap and the issues people are keeping their .ini file configs up to date so apparently it still works if you DL the program and go to some random git issue that has the updated stuff correct Do we consider that dead or alive? lol I looked into it and seems there is a community fork with "lots of life" so far https://github.com/atom-community/atom/discussions https://atom-community.github.io/ Should I update the URL to the github repo or what? Not sure what to do with that one either
Author
Owner

@nodiscc commented on GitHub (Oct 6, 2022):

go to some random git issue that has the updated stuff correct
Do we consider that dead or alive?

Dead considering no updates since 2018, and the amount of issues piling up without triage, and no maintained fork.

https://github.com/atom-community/atom and https://atom-community.github.io/

Looks suitable

@nodiscc commented on GitHub (Oct 6, 2022): > go to some random git issue that has the updated stuff correct > Do we consider that dead or alive? Dead considering no updates since 2018, and the amount of issues piling up without triage, and no maintained fork. > https://github.com/atom-community/atom and https://atom-community.github.io/ Looks suitable
Author
Owner

@nodiscc commented on GitHub (Oct 9, 2022):

Reopening and pinning this issue

Anyone, feel free to send Pull Requests to remove projects that are no longer maintained.

@nodiscc commented on GitHub (Oct 9, 2022): Reopening and pinning this issue > Anyone, feel free to send Pull Requests to remove projects that are no longer maintained.
Author
Owner

@cu commented on GitHub (Dec 15, 2022):

Howdy! A couple of questions:

It looks like Pulsar is an actively maintained community fork of Atom. I don't use it, but would it be a worthy addition to the list?

The repo for LightTable went read-only a year ago and the last release was about 7 years ago. I presume that counts as dead?

Happy to write up PRs for either or both of these.

@cu commented on GitHub (Dec 15, 2022): Howdy! A couple of questions: It looks like [Pulsar](https://github.com/pulsar-edit/pulsar) is an actively maintained community fork of Atom. I don't use it, but would it be a worthy addition to the list? The repo for [LightTable](https://github.com/LightTable/LightTable) went read-only a year ago and the last release was about 7 years ago. I presume that counts as dead? Happy to write up PRs for either or both of these.
Author
Owner

@nodiscc commented on GitHub (Dec 15, 2022):

The repo for LightTable went read-only a year ago and the last release was about 7 years ago. I presume that counts as dead?

It does. PR welcome.

It looks like Pulsar is an actively maintained community fork of Atom.

Ideally we should only list a single fork, unless there are significant differences between Atom-community and Pulsar.

I don't use it

Ideally when submitting a new tool, you should have been using it for some time and have good experiences with it. The tool should also be mature and stable enough. See also https://github.com/awesome-foss/awesome-sysadmin/pull/357 for discussion on possible quality guidelines.

Judging by the first PR submitted in the Pulsar repo, this fork is only 4 months old, so I'd say it's not mature enough. Please read the comments at https://github.com/awesome-foss/awesome-sysadmin/pull/357 and let us know your opinions there, if you have any.

@nodiscc commented on GitHub (Dec 15, 2022): > The repo for [LightTable](https://github.com/LightTable/LightTable) went read-only a year ago and the last release was about 7 years ago. I presume that counts as dead? It does. PR welcome. > It looks like [Pulsar](https://github.com/pulsar-edit/pulsar) is an actively maintained community fork of Atom. Ideally we should only list a single fork, unless there are significant differences between Atom-community and Pulsar. > I don't use it Ideally when submitting a new tool, you should have been using it for some time and have good experiences with it. The tool should also be mature and stable enough. See also https://github.com/awesome-foss/awesome-sysadmin/pull/357 for discussion on possible quality guidelines. Judging by the first PR submitted in the Pulsar repo, this fork is only 4 months old, so I'd say it's not mature enough. Please read the comments at https://github.com/awesome-foss/awesome-sysadmin/pull/357 and let us know your opinions there, if you have any.
Author
Owner

@ColonelThirtyTwo commented on GitHub (Dec 21, 2022):

I'll add to this: Ori Filesystem hasn't had a commit since 2019: https://bitbucket.org/orifs/ori/wiki/history/Home

@ColonelThirtyTwo commented on GitHub (Dec 21, 2022): I'll add to this: Ori Filesystem hasn't had a commit since 2019: https://bitbucket.org/orifs/ori/wiki/history/Home
Author
Owner

@ColonelThirtyTwo commented on GitHub (Dec 21, 2022):

Bolo's homepage is a default nginx page. I found https://github.com/huntprod/bolo which looks like the source code, but hasn't had a commit since 2018.

@ColonelThirtyTwo commented on GitHub (Dec 21, 2022): Bolo's homepage is a default nginx page. I found https://github.com/huntprod/bolo which looks like the source code, but hasn't had a commit since 2018.
Author
Owner

@nodiscc commented on GitHub (Dec 24, 2022):

Ori Filesystem hasn't had a commit since 2019

-> https://github.com/awesome-foss/awesome-sysadmin/pull/441

@nodiscc commented on GitHub (Dec 24, 2022): > Ori Filesystem hasn't had a commit since 2019 -> https://github.com/awesome-foss/awesome-sysadmin/pull/441
Author
Owner

@nodiscc commented on GitHub (Dec 24, 2022):

Bolo's homepage is a default nginx page. I found https://github.com/huntprod/bolo which looks like the source code, but hasn't had a commit since 2018.

-> https://github.com/awesome-foss/awesome-sysadmin/pull/442

@nodiscc commented on GitHub (Dec 24, 2022): > Bolo's homepage is a default nginx page. I found https://github.com/huntprod/bolo which looks like the source code, but hasn't had a commit since 2018. -> https://github.com/awesome-foss/awesome-sysadmin/pull/442
Author
Owner

@MBadberg commented on GitHub (Jan 20, 2023):

Link to https://itpi.org/the-visible-ops-handbook-review.html is dead. Page no longer exist. I've found no alternate link. :(

Link under Books -> Visible OPS handbook

@MBadberg commented on GitHub (Jan 20, 2023): Link to https://itpi.org/the-visible-ops-handbook-review.html is dead. Page no longer exist. I've found no alternate link. :( Link under Books -> Visible OPS handbook
Author
Owner

@G2G2G2G commented on GitHub (Jan 20, 2023):

It comes right up with https://itpi.org/the-visible-ops-book-series/
but what is this site? looks like a cash grab book..
also the sites it links to for sale are unencrypted and you can't even add stuff to the cart

@G2G2G2G commented on GitHub (Jan 20, 2023): It comes right up with https://itpi.org/the-visible-ops-book-series/ but what is this site? looks like a cash grab book.. also the sites it links to for sale are unencrypted and you can't even add stuff to the cart
Author
Owner

@nodiscc commented on GitHub (Jan 20, 2023):

Apparently this link was added in 31313e9e83

Please send PRs to help cleanup the list. Personally I think that links to any resources that are not freely available should be removed.

@nodiscc commented on GitHub (Jan 20, 2023): Apparently this link was added in https://github.com/awesome-foss/awesome-sysadmin/commit/31313e9e83d1d6cddf9fb3c2bd571842e32d9a5c Please send PRs to help cleanup the list. Personally I think that links to any resources that are not freely available should be removed.
Author
Owner

@G2G2G2G commented on GitHub (Jan 20, 2023):

https://github.com/awesome-foss/awesome-sysadmin/pull/448

I had to delete all those books except the only page that actually links to a massive .pdf book for free..

@G2G2G2G commented on GitHub (Jan 20, 2023): https://github.com/awesome-foss/awesome-sysadmin/pull/448 I had to delete all those books except the only page that actually links to a massive .pdf book for free..
Author
Owner

@nodiscc commented on GitHub (Sep 4, 2023):

Automated checks return errors for a few URLs:

https://atomiadns.com/ : HTTP 500
https://www.cacti.net/ : HTTPSConnectionPool(host='www.cacti.net', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)')))
https://ceph.com/ : HTTP 500
https://about.gitlab.com/gitlab-ci/ : HTTP 404
https://community.openvpn.net/ : HTTP 403
https://status-ksk5.onrender.com/ : HTTPSConnectionPool(host='status-ksk5.onrender.com', port=443): Read timed out. (read timeout=10)
https://tahoe-lafs.org/trac/tahoe-lafs : HTTPSConnectionPool(host='tahoe-lafs.org', port=443): Max retries exceeded with url: /trac/tahoe-lafs (Caused by SSLError(SSLError(1, '[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1007)')))

We should check whether these URLs are still valid, and if needed, update them or remove these projects from the list.

In some cases, URLs are actually valid but something prevents the link checker from accessing the page (e.g. DDoS protection pages). In this case it is possible to skip these URLs using exclude_regex in https://github.com/awesome-foss/awesome-sysadmin/blob/master/.hecat/url-check.yml (example usage here)

In other cases, the error is temporary and we should just wait for a while for it to resolve itself. I will implement a daily URL check.

In the future, last commit date will be gathered automatically, and a warning/error will be raised when it is older than the configured threshold (I suggest 6 months for warning, 12 months for error like we did in https://github.com/awesome-selfhosted/awesome-selfhosted-data)

@nodiscc commented on GitHub (Sep 4, 2023): [Automated checks](https://github.com/awesome-foss/awesome-sysadmin/actions) return errors for a few URLs: ``` https://atomiadns.com/ : HTTP 500 https://www.cacti.net/ : HTTPSConnectionPool(host='www.cacti.net', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)'))) https://ceph.com/ : HTTP 500 https://about.gitlab.com/gitlab-ci/ : HTTP 404 https://community.openvpn.net/ : HTTP 403 https://status-ksk5.onrender.com/ : HTTPSConnectionPool(host='status-ksk5.onrender.com', port=443): Read timed out. (read timeout=10) https://tahoe-lafs.org/trac/tahoe-lafs : HTTPSConnectionPool(host='tahoe-lafs.org', port=443): Max retries exceeded with url: /trac/tahoe-lafs (Caused by SSLError(SSLError(1, '[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1007)'))) ``` We should check whether these URLs are still valid, and if needed, update them or remove these projects from the list. In some cases, URLs are actually valid but something prevents the link checker from accessing the page (e.g. DDoS protection pages). In this case it is possible to skip these URLs using `exclude_regex` in https://github.com/awesome-foss/awesome-sysadmin/blob/master/.hecat/url-check.yml (example usage [here](https://github.com/awesome-selfhosted/awesome-selfhosted-data/blob/master/.hecat/url-check.yml#L11)) In other cases, the error is temporary and we should just wait for a while for it to resolve itself. I will implement a daily URL check. In the future, last commit date will be gathered automatically, and a warning/error will be raised when it is older than the configured threshold (I suggest 6 months for warning, 12 months for error like we did in https://github.com/awesome-selfhosted/awesome-selfhosted-data)
Author
Owner

@Rabenherz112 commented on GitHub (Sep 10, 2023):

We should check whether these URLs are still valid, and if needed, update them or remove these projects from the list.

Done with the latest PRs (#529, #530, #531, #532, #533)

I suggest 6 months for warning, 12 months for error for the last commit date

I would agree with this.

@Rabenherz112 commented on GitHub (Sep 10, 2023): > We should check whether these URLs are still valid, and if needed, update them or remove these projects from the list. Done with the latest PRs (#529, #530, #531, #532, #533) > I suggest 6 months for warning, 12 months for error for the last commit date I would agree with this.
Author
Owner

@animeai commented on GitHub (Nov 3, 2023):

VestaCP is pretty much abandoned at this point and should probably be replaced with the active (and much improved) fork HestiaCP https://github.com/hestiacp/hestiacp/ I don't have time to make a PR right now though!

@animeai commented on GitHub (Nov 3, 2023): VestaCP is pretty much abandoned at this point and should probably be replaced with the active (and much improved) fork HestiaCP https://github.com/hestiacp/hestiacp/ I don't have time to make a PR right now though!
Author
Owner

@nodiscc commented on GitHub (Nov 3, 2023):

HestiaCP added in https://github.com/awesome-foss/awesome-sysadmin/pull/515, VestaCP removed in https://github.com/awesome-foss/awesome-sysadmin/pull/539. Thanks

@nodiscc commented on GitHub (Nov 3, 2023): HestiaCP added in https://github.com/awesome-foss/awesome-sysadmin/pull/515, VestaCP removed in https://github.com/awesome-foss/awesome-sysadmin/pull/539. Thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#700