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

How should this content be licensed? #2

Open
vermiculus opened this issue Jul 11, 2015 · 1 comment
Open

How should this content be licensed? #2

vermiculus opened this issue Jul 11, 2015 · 1 comment

Comments

@vermiculus
Copy link
Owner

@johannesbottcher noted on gitter:

Question to all: Should a template have a license, and if so, which? Should a template introduce itself as a template in a meta-comment? When does a template stops being a template and getting a personal document? google lists thousands of files stating: % This is a simple template for a LaTeX document using the "article" class. where the user simply did not remove that comment. I guess we all agree, that there aren't so many templates.

There are several things I can think to consider:

  • Do users implicitly or explicitly agree to whatever license the repository uses (LPPL would be most appropriate), or does each contribution have its own license (a management/legal nightmare)?
  • How are template authors given credit for their work?
@vermiculus
Copy link
Owner Author

I think there is room for a YAML, JSON, or XML document describing all the metadata for each file in a given directory so that the files themselves are kept clean. The only things that could stay in any given file, I suppose, are the contributor's name and any given contact information.

Though that in itself raises an interesting point – who to contact when things go wrong – which I'll defer to #3.

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

1 participant