Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS.ORG CLEANUP #2455

Closed
MattIPv4 opened this issue Oct 23, 2018 · 3 comments · Fixed by #2545
Closed

JS.ORG CLEANUP #2455

MattIPv4 opened this issue Oct 23, 2018 · 3 comments · Fixed by #2545
Assignees

Comments

@MattIPv4
Copy link
Member

MattIPv4 commented Oct 23, 2018

JS.ORG CLEANUP

The following js.org subdomains have been detected to no longer be working. If you are the 'owner' of any of these subdomains and wish to still use them, please leave a comment below in the following format:

I am responsible for `xxx.js.org`.
It now has [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) and is now working.

Subdomains that aren't accounted for after a month and are still down will be removed.

Once a subdomain has been validated through a reply below it will be crossed out and not removed from js.org.
A tick next to the subdomain indicates the 'owner' has been contacted by the js.org team.

The list


'Owners' of subdomains that are identifiable through the GitHub pages the subdomain points to will be contacted via their repository. They will receive the following message asking them to reply to this issue to keep their domain.

# JS.ORG CLEANUP
Hello, it seems a `js.org` subdomain that was requested to target this repository (or another on this user/organisation) no longer works.
The subdomain requested was `xxx.js.org` and had the target of `xxx`.
To keep the `js.org` subdomain you should add a page with [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) within a month so the subdomain doesn't resolve to a 404 any longer.
Otherwise the requested subdomain will be removed from JS.ORGs zonefile and the list of active subdomains.

**If you are wanting to keep the `js.org` subdomain and have added [reasonable content](https://github.com/js-org/js.org/wiki/No-Content), YOU MUST reply to the [main cleanup issue](xxx) with the response format detailed at the top to keep the requested subdomain.**
@MattIPv4
Copy link
Member Author

Attempts to make contact with all 'owners' of the above subdomains have been completed. In a month from now any subdomains that remain dead and unaccounted for will be removed.

@MattIPv4 MattIPv4 self-assigned this Oct 28, 2018
@ByteCommander
Copy link
Contributor

I am responsible for ubuntu-hideout.js.org.
It now has reasonable content and is now working.

@MattIPv4
Copy link
Member Author

The cleanup claim period is now over, the cleanup PR has been made #2545

@js-org js-org locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants