-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Update copyright, author, and version information for RTD #474
Comments
Current version 0.10.3 |
How about "Econ-ARK" as the author? Or, "Econ-ARK team"?
…On Mon, Feb 3, 2020 at 6:56 PM Sebastian Benthall ***@***.***> wrote:
@llorracc <https://github.com/llorracc> @mgerring
<https://github.com/mgerring> @shaunagm <https://github.com/shaunagm>
I can update this. But what should it say in the AUTHOR field?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#474?email_source=notifications&email_token=AAKCK72GZIPCJN45VAKQANTRBBLDJA5CNFSM4KJFPFH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKUY66A#issuecomment-581537656>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKCK744BACXQ3JH6E2SOUTRBBLDJANCNFSM4KJFPFHQ>
.
--
- Chris Carroll
|
Ok, I will change it to "Econ-ARK Team" However, as this is used in the copyright notice, it may be that the real answer is more complicated than this. As far as I know, there's no agreement for copyright assignment as part of contributing to HARK. So while implicitly everything put here is licensed under the same license, each code author maintains copyright ownership over what they wrote. @shaunagm may correct me on this. On some projects I've been on, there's been some paperwork to clear this up. In my experience, this is a bit of legal complexity that rarely matters in practice, but potentially could in the long future. It's probably easier to resolve sooner than later. |
Hmmm, I'm pretty sure that the terms of the Apache license are such that
once someone has contributed something to the archive they do not retain
any residual property rights over it.
It is of course possible to hire people to do work beforehand, and to use
stuff on which they retain licensed ownership (like, we are all the time
using stuff from other open source tools).
But I don't think there is an issue to clear up here; that's the point of
being very specific about the license from the get-go.
…On Tue, Feb 4, 2020 at 10:43 PM Sebastian Benthall ***@***.***> wrote:
Ok, I will change it to "Econ-ARK Team"
However, as this is used in the copyright notice, it may be that the real
answer is more complicated than this.
As far as I know, there's no agreement for copyright assignment as part of
contributing to HARK. So while implicitly everything put here is licensed
under the same license, each code author maintains copyright ownership over
what they wrote.
@shaunagm <https://github.com/shaunagm> may correct me on this.
On some projects I've been on, there's been some paperwork to clear this
up. In my experience, this is a bit of legal complexity that rarely matters
in practice, but potentially could in the long future. It's probably easier
to resolve sooner than later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#474?email_source=notifications&email_token=AAKCK7Y64FKTLMJZDR3SEWDRBHORNA5CNFSM4KJFPFH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKZJQ2Y#issuecomment-582129771>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKCK77HOJUHY6PCHTYT2KLRBHORNANCNFSM4KJFPFHQ>
.
--
- Chris Carroll
|
IANAL |
I agree with both of you. I think this Q/A is sensible: Recollecting now, CLA's came up in earlier work because we were considering GPL licensing. |
There are a number of fields in the Sphinx configuration that have to do with the copyright, authors, and version numbers of the software being documented.
https://github.com/econ-ark/HARK/blob/master/Documentation/conf.py#L70-L82
It looks like these are unchanged from their default values.
They should be changed to more appropriate values, and a procedure for updating them should be added to whatever instructions there are for the release process.
The text was updated successfully, but these errors were encountered: