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

Copyright year in LICENSE files #102

Closed
annevk opened this issue Jan 17, 2020 · 13 comments · Fixed by #132
Closed

Copyright year in LICENSE files #102

annevk opened this issue Jan 17, 2020 · 13 comments · Fixed by #132
Assignees

Comments

@annevk
Copy link
Member

annevk commented Jan 17, 2020

The discussion in #51 never really resolved the year question properly and since 2018 we have not bumped the year in LICENSE files across our repositories as it's easy to forget without automation. The standards themselves do include updated years as they are automatically generated.

Before investing effort into this I'd first like to get a more definitive answer as to whether it's needed at all.

@foolip
Copy link
Member

foolip commented Mar 10, 2020

@whatwg/sg I think there are mainly two options:

  • Use the year when the file was created and never update it
  • Update files to have a range of years when touched

The first option is the status quo. @annevk do you have a preference if multiple options could be made to work?

@annevk
Copy link
Member Author

annevk commented Mar 10, 2020

My preference is a magical third option where we are not required to list a year. Failing that I suppose never updating would be nice, but that will make it out-of-sync with the standards where we do update it (technically they are newly created files, so...). See the final paragraph of https://dom.spec.whatwg.org/#acks for instance.

(Translations (discussed in #59) are yet another place where these years would end up as currently proposed with perhaps yet another year, depending on how timelines line up.)

@hsivonen
Copy link
Member

Surely there's a third option:

  • Not having a year in the notice.

@othermaciej
Copy link
Contributor

Automatic updating is the safest choice. We can also ask lawyers if it's ok to have no year.

@annevk
Copy link
Member Author

annevk commented Apr 30, 2020

@othermaciej please ask them. It'd be great to have a more definitive answer on whether it's okay to not have it at all. We're now rather inconsistent across a large set of files in many repositories and automating them all would be a bit of a hassle.

@foolip foolip self-assigned this Jun 23, 2020
@foolip
Copy link
Member

foolip commented Jun 23, 2020

We have gone back to get legal input on this and now have the answer: it's OK for us to not include the copyright year in copyright notices.

I've self-assigned to implement this, which I think amounts to updating https://github.com/whatwg/sg/blob/master/LICENSE and https://github.com/whatwg/spec-factory/blob/master/LICENSE.template.

@annevk are you aware of any other places we have a hardcoded copyright year?

@annevk
Copy link
Member Author

annevk commented Jun 24, 2020

That's really great, hurrah!

The specifications themselves (in the Acknowledgments section usually through Bikeshed templating except for HTML) and some repositories not covered by spec-factory, such as https://github.com/whatwg/whatwg.org. (It seems some repositories lack a LICENSE file, I've filed some issues already.)

@foolip

This comment has been minimized.

annevk added a commit to whatwg/whatwg.org that referenced this issue Jun 24, 2020
annevk added a commit to speced/bikeshed that referenced this issue Jun 24, 2020
annevk added a commit to whatwg/participate.whatwg.org that referenced this issue Jun 24, 2020
annevk added a commit to whatwg/html that referenced this issue Jun 24, 2020
annevk added a commit to whatwg/html that referenced this issue Jun 24, 2020
@annevk

This comment has been minimized.

@foolip

This comment has been minimized.

@annevk

This comment has been minimized.

@annevk
Copy link
Member Author

annevk commented Jun 24, 2020

Overview (in somewhat ideal order of landing):

Other LICENSE repository issues are tracked in #133.

foolip added a commit that referenced this issue Jun 27, 2020
@annevk annevk reopened this Jun 28, 2020
annevk added a commit to whatwg/html that referenced this issue Jun 29, 2020
annevk added a commit to speced/bikeshed that referenced this issue Jun 29, 2020
annevk added a commit to whatwg/participate.whatwg.org that referenced this issue Jun 29, 2020
foolip pushed a commit to whatwg/whatwg.org that referenced this issue Jun 29, 2020
@foolip
Copy link
Member

foolip commented Jun 29, 2020

Everything in #102 (comment) is done now.

@foolip foolip closed this as completed Jun 29, 2020
mfreed7 pushed a commit to mfreed7/html that referenced this issue Sep 11, 2020
travisleithead added a commit that referenced this issue Nov 3, 2020
foolip pushed a commit that referenced this issue Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

4 participants