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

Licenses: Include in individual packages or just at repository root? #1236

Open
2 tasks
ryan-roemer opened this issue Sep 22, 2022 · 0 comments
Open
2 tasks

Licenses: Include in individual packages or just at repository root? #1236

ryan-roemer opened this issue Sep 22, 2022 · 0 comments
Labels
Chore Tasks considered to be routine

Comments

@ryan-roemer
Copy link
Member

So, we have spectacle-mdx-loader with a LICENSE.txt in the package which also gets published to npm. By contrast, create-spectacle and spectacle don't. Victory doesn't have per-package licenses. Our new tracing repository does.

Tasks:

  • Figure out what we should do
  • Standardize the packages across the projects.
@ryan-roemer ryan-roemer added the Chore Tasks considered to be routine label Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Chore Tasks considered to be routine
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ryan-roemer