Scoped Packages for Trails organization
Issue Description
Scoped Packages
The general consensus is to move from tagged releases to eg. v2-latest to normal version numbers. This is going to take a fair bit of work to do this so it's a good time to bring up scoped packages.
Npm allows open source organizations to use scoped packages eg @trails/*. I wanted to start the conversation about using scoped packages for packages that the trails organization maintains. Thoughts for or against?
Fellow @trailsjs/maintainers I'm still onboard with this, any one blocking this? If not, I say we go for it.
from the first site, it seems like a good idea. I will go more deep into it and share my views :)