[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Copyright years in source code
From: |
Mark Atwood |
Subject: |
Re: Copyright years in source code |
Date: |
Sat, 09 May 2020 18:36:47 -0700 |
User-agent: |
Cyrus-JMAP/3.3.0-dev0-413-g750b809-fmstable-20200507v1 |
Is there any question for me to answer in this thread?
I dont considering myself controlling of the gpsd project. Does the gpsd
project want me to be?
I do think that the gpsd project can scrub all the years out of their copyright
statements, include the "year of first publication".
One of the reason for simplifying the text of the copyright statements in this
way is because if the day ever does come that there is actually is a copyright
lawsuit and that it does turn on the point of "what year was it published", the
digits after the word "copyright" are not actually controlling. Instead the
parties before the court will spend a bunch of analysists and researchers on
all the actual publication artifacts and incidentals to publication, and use
that to determine what year is what.
In modern terms, what that means is they will look in the git history and the
email headers, and at any 3rd party tech news publications, and use that.
Scrub the dates. Use the text "Copyright the contributors of the GPSD
project". Put SPDX-License-Identifiers in.
..m
- Copyright years in source code, Sanjeev Gupta, 2020/05/06
- Re: Copyright years in source code, John Ackermann, 2020/05/06
- Re: Copyright years in source code, Gary E. Miller, 2020/05/06
- Re: Copyright years in source code, Richard Laager, 2020/05/08
- Re: Copyright years in source code, Gary E. Miller, 2020/05/08
- Re: Copyright years in source code,
Mark Atwood <=
- Re: Copyright years in source code, Gary E. Miller, 2020/05/09
- Re: Copyright years in source code, Bernd Zeimetz, 2020/05/10
- Re: Copyright years in source code, Gary E. Miller, 2020/05/10
- Re: Copyright years in source code, Bernd Zeimetz, 2020/05/10
- Re: Copyright years in source code, Sanjeev Gupta, 2020/05/09