Description
👋 Hey all,
It's time for another annual cleanup of allocated subdomains on js.org again, like we did last year... oh, wait, I forgot to do it last year... so just like we did in 2023 (#7913).
I intend to start the cleanup process next weekend, 7th June 2025. As usual, folks will then have just over one month to action any issues with subdomains, with the final removal of any subdomains happening the weekend of the 12th July 2025.
@indus any issues with this on your end?
An explainer on what the annual cleanup process is:
We have a script over in https://github.com/js-org/js.org-cleanup that will run through every subdomain in the cnames_active.js file here. It will make http & https requests to each one to confirm that an okay status code (2xx or 3xx) is returned, and that there is content on the page. If a redirect is returned by a subdomain (3xx), it must be to another js.org subdomain to be considered valid.
For any subdomains that fail validation, an issue will be opened in the corresponding GitHub repository for subdomains targeting one, and all failing subdomains will be listed in an automatically created issue in this repository (js-org/js.org).
Once the mega issue has been created, folks have roughly a month to action the issue if their subdomain is failing, letting us know in the issue once it has been fixed. At the end of the month, any domains that weren't fixed and are still failing will be removed from js.org and released for new folks to request if they desire.