Question about Acceptable use of a js.org subdomain

[javaarchive]

I read the newest message on the README most recently "Due to the increased number of requests for js.org subdomains recently, with many having questionable relevancy to the JavaScript community and ecosystem, we've decided that going forward JS.ORG will be focusing on accepting subdomain requests from projects with a clear relation to the JS community. As some examples, personal pages, blogs, and Discord bot pages will no longer be accepted"
The requirement seems to be "Projects such as NPM packages, libraries, tools that have a clear and direct relation to JavaScript, will be accepted when requesting a JS.ORG subdomain.".

I am writing an electron music player application that is open-source and extremely customisable with a sort of plugin system that allows you to set it up to play from other sources. Would this be a valid use case to get a js.org domain since I am planing to set up a quick static website in the future to give basic information on the app and host a copy of the documentation.

[praveenscience]

So Electron is a JavaScript thing. And since you're going to do it Open Source, IMHO, this seems to be a valid use case. 😊

[indus]

We had a similar discussion here: #5496

TLTR: If the the JS code is mostly hidden from the visitor and it is just part of your product (the player) then it doesn't qualify for a JS.ORG domain. If the opensource and or JS aspect is prominent and you encourage people to mod the player or reuse the code, or interact with its API, etc. I'm fine with it.
@praveenscience: (Almost) Every website in the internet "is a JavaScript thing". But that doesn't mean every website qualifies for a JS.ORG domain...

[praveenscience]

Wow, that was a great clarification @indus. Thanks! 😊 Just curious, why don't you enable Discussions for stuff like these? 😊 We don't want issues to be cluttered with discussions, right? 😊

[indus]

@praveenscience I'll give it a try: #5705