Remove dead projects

[G2G2G2G]

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/

[nodiscc]

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

[G2G2G2G]

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

[nodiscc]

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]

Reopening and pinning this issue

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

[cu]

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.

[nodiscc]

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.

[ColonelThirtyTwo]

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

[ColonelThirtyTwo]

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.

[nodiscc]

Ori Filesystem hasn't had a commit since 2019

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

[nodiscc]

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

[MBadberg]

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

[G2G2G2G]

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

[nodiscc]

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.

[G2G2G2G]

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..

[nodiscc]

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)

[Rabenherz112]

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.

[animeai]

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!

[nodiscc]

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