Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scoped Packages for Trails organization #308

Open
scott-wyatt opened this issue Oct 23, 2017 · 2 comments
Open

Scoped Packages for Trails organization #308

scott-wyatt opened this issue Oct 23, 2017 · 2 comments
Labels
discussion

Comments

@scott-wyatt
Copy link
Member

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?
@scott-wyatt
Copy link
Member Author

Fellow @trailsjs/maintainers I'm still onboard with this, any one blocking this? If not, I say we go for it.

@Nishchit14
Copy link

from the first site, it seems like a good idea. I will go more deep into it and share my views :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scott-wyatt @Nishchit14