Repository Naming in typed-typings

[unional]

<purpose>-<name>

• env-atom, env-electron

<most common package manager>-<name>

• “most common package manager” can still change (e.g. bower)
• "most common package manager" is subjective.
• npm is not likely to go away, but others not really sure (e.g. bower)
• Also, I don’t like to “think and determine” what the name of the repo should be. And also don’t like to “look and discover it is only distributed in npm so I name it as npm-*”.

typed-<name>

• typed- is redundant.

<owner>-<name>

• Aware that some package transfer ownership (e.g. atom/electron to electron/electron)
• Is it relatively rare?

[unional]

<name>: The most obvious name

Another alternative:

<name>

• As in NPM registry discussion @typings/<name> or @typed/<name>. Don't need any prefix.
• Is TS plan to use NPM registry even the source is not NPM package?
  • i.e. atom, electron, etc

[blakeembrey]

Is TS plan to use NPM registry even the source is not NPM package?

As far as I can understand, yes 😟 It'll be a mirror of DefinitelyTyped, which is definitely not separated in any distinct way. The obvious issue here is collisions, I know there's even been a couple on DefinitelyTyped.

[blakeembrey]

Here's an old discussion they had on this, without any obvious resolution: DefinitelyTyped/DefinitelyTyped#1951.