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

Update copyright, author, and version information for RTD #474

Closed
sbenthall opened this issue Jan 20, 2020 · 7 comments
Closed

Update copyright, author, and version information for RTD #474

sbenthall opened this issue Jan 20, 2020 · 7 comments

Comments

@sbenthall
Copy link
Contributor

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.

@sbenthall
Copy link
Contributor Author

Current version 0.10.3

@sbenthall
Copy link
Contributor Author

sbenthall commented Feb 3, 2020

@llorracc @mnwhite @shaunagm

I can update this. But what should it say in the AUTHOR field?

@llorracc
Copy link
Collaborator

llorracc commented Feb 3, 2020 via email

@sbenthall
Copy link
Contributor Author

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.

@llorracc
Copy link
Collaborator

llorracc commented Feb 8, 2020 via email

@MridulS
Copy link
Member

MridulS commented Feb 8, 2020

IANAL
CLA (contributor license agreements) are usually used in the case of copyleft licenses like GPL or if the open source project is backed by a corporation (this is at least what I have seen in the wild).
With apache license and econ-ark project I highly doubt we should have a CLA.

@sbenthall
Copy link
Contributor Author

I agree with both of you.

I think this Q/A is sensible:
https://opensource.stackexchange.com/questions/5585/benefits-of-a-cla-when-using-apache-2-0-license

Recollecting now, CLA's came up in earlier work because we were considering GPL licensing.

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

No branches or pull requests

3 participants