-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fedora packaging #47
Comments
Probably after #32 is in and we make a release? |
v0.2.0 is out. |
Are the |
If someone uses this package, they would use the files from the package. If they prefer, they can vendor the files, which means they don't need to get this package from Fedora. What change were you thinking of? |
I was thinking about the more general case:
If the file is being maintained externally than I would need to add a |
I think that date was inherited. @jcfr? |
Was thinking you could just add
Or equivalent, marking when it got forked from kitware's |
I don't think it's a good idea to assign copyright to something that's not a legal entity. A person works, or a company, but "... developers" is too fuzzy and unclear. That's what I remember from a discussion with a lawyer a long time ago, I might be misremembering it though. |
I remember there being some discussion on Fedora mail list1 about jaraco removing copyright notice2. I need to read through the mail list more carefully, but afaiu it is ok if the authorship is self contained. There is also this article which many people resonate with, but of course inal. Footnotes |
Let me know when I should start packaging this project.
The text was updated successfully, but these errors were encountered: