Discourage atom- package prefixes about apm HOT 7 OPEN

I would name the repository atom-supercollider, but not the package itself in the registry.

from apm.

I like this idea. It is probably a low priority but we could add a warning to apm init or apm publish.

I also added a line to the your first package doc atom/atom#1716

from apm.

I think the atom- prefix should be reserved for packages made by the Atom team. This way, it is more obvious if something is third-party or made by the creators of the editor.

from apm.

in my case (very common): I've made a package for working with supercollider. (it includes a REPL, language grammar. not just snippets). I cannot call it 'supercollider' because that is the main project. it is "atom-supercollider" by common parlance. or should it be "supercollider-atom" ?

from apm.

honestly I cannot even publish due to this bug: #150

apm publish
Package must pushed up to GitHub before publishing: https://help.github.com/articles/create-a-repo

I actually did have the name as "supercollider", the repo as "atom-supercollider" https://github.com/crucialfelix/atom-supercollider.git and just now changed the name in an attempt to find some way to get it to publish.

many suggestions in forums say it has to do with renaming. I've been stumped for over an hour

from apm.

Weird. Looks like your package.json is correctly pointing to the repository. @kevinsawicki @thedaniel, any insight here?

from apm.

@nathansobo I think this is an apm issue. See my comment on #150

from apm.