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.

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

License notice? #3

Open
eitsupi opened this issue Jul 11, 2022 · 3 comments
Open

License notice? #3

eitsupi opened this issue Jul 11, 2022 · 3 comments

Comments

@eitsupi
Copy link

eitsupi commented Jul 11, 2022

Not limited to this repository, but if we install the quarto extension, our repository will include the filter scripts, etc., so it would be easier to handle if the License is written in each file, or _extension.yml.

@mcanouil
Copy link
Contributor

License could also be within the _extensions/NAME directory.
This way, the license is propagated when quarto install extension (or quarto use extension for templates) is used.

@mcanouil mcanouil mentioned this issue Jul 25, 2022
@cscheid
Copy link
Contributor

cscheid commented Jul 25, 2022

The main issue here is that we want to keep all quarto extensions in quarto-ext consistent, so whatever we change, we'll have to change everywhere else.

@mcanouil
Copy link
Contributor

mcanouil commented Jul 25, 2022

License guidelines should be provided in the documentation as well once the strategy is established.
This will "ensure" some consistency across all templates/extensions, even the ones not in @quarto-ext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants