model.js.org

[xiangnanscu]

• [✓] There is reasonable content on the page (see: model)
• [✓] I have read and accepted the Terms and Conditions

[MattIPv4]

@indus thoughts on the naming here? model feels incredibly generic to me -- the actual package is scoped to the user, @xiangnanscu/model. I fear this could be confused with another package, say https://www.npmjs.com/package/model?

[indus]

@MattIPv4 I don't think it is a problem that the repo is connected to a user and not an organisation. And while the name is very generic it makes sense (from what it says in the github repo Readme). I think we don't have to wait for the biggest project of every generic term to claim their JS.ORG subdomain.
On the other hand such a generic term may lead to a situation where another project requests this subdomain as well. @xiangnanscu In such a situation you may loose you subdomain (based on this procedure: Naming-Conflicts). So in your own interest you may want to request maybe some prefixed version or otherwise less generic term?!?

[xiangnanscu]

@indus The brave enjoy the world first. So add model.js.org please.

[indus]

Welcome http://model.js.org