@generate scope

[jonschlinkert]

we have the @generate scope on NPM. For the next release, we can either move all "utils" or non-generator libs to the @generate scope, or we can move all generators to the @generate scope.

I'm fine with either, we can automate most of it anyway. Also, since most generators are more likely to be installed globally than to be used as dependencies, I think a transition to use @generate/foo won't be quite as painful for users as it would be otherwise. We can just let ppl know that generate-foo is deprecated and to use @generate/foo going forward. This also gives us a clean way to differentiate "official" generators vs. generators published by users.

@doowb et al, thoughts?

[doowb]

I think we should move all the generators to the @generate scope. I don't think it imposes a barrier to people using them and they'll all be neatly put into the @generate folder in either global or local node_modules. I also like how it can differentiate between "official" generators and community generators.

[jonschlinkert]

k, one more thing we might consider, is using the util-* prefix for non-generators.