Dear KDE community,
Recently, on planet KDE
(https://ervin.ipsquad.net/blog/2023/01/27/web-review-week-2023-04/)
Kevin Ottens wrote about reducing the maintenance and development burden
of a project by not periodically changing every copyright year. For
example, Curl:
- https://daniel.ha
"Every January 1st, an army of open source developers rushes out to
update their copyright attributions in licenses and documentation. Why?
Because we’ve always done it that way.
I’ve stopped participating after I learned that copyright statements
need only the year of the first publication an
On Saturday, 4 February 2023 20:58:30 CET Toni Asensi Esteve wrote:
> Do you think that changing and reviewing too many changes every year is
> worth it? What do you think that would be better?
One of the best places *right now* to ask this question is the Legal &
Licensing room at FOSDEM, in Bru
Or just come to the Software Bill of Materials room where peopl that
develop and do the tools for that are meeting right now :-)
On Sat, Feb 4, 2023 at 11:43 PM Adriaan de Groot wrote:
> On Saturday, 4 February 2023 20:58:30 CET Toni Asensi Esteve wrote:
> > Do you think that changing and review
On 04.02.23 20:58, Toni Asensi Esteve wrote:
Do you think that changing and reviewing too many changes every year is
worth it? What do you think that would be better?
Another perspective is this:
https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code.
Mat
Another perspective is this:
https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code. Matija suggests to add the year once as the year of file creation, but not change it afterwards.
Thanks, the writings of that lawyer coincide with the text that I found
later
