News for hackers. Stuff that matters.
Re:One Guy Ruined Hacktoberfest 2020 by cbanek on Friday October 02, 2020 @12:29AM (#24658884)
I have done one letter typo fixes to doc repos as a 3rd party and felt great about them. One of them was actually a typo in a command line that I found by going through their instructions step by step copying and pasting each line. I was seriously confused when it didn't work!
Re:One Guy Ruined Hacktoberfest 2020 by dannyw on Friday October 02, 2020 @04:50AM (#24660530)
Yes. Fixing up documentation is always helpful, even if it’s a one letter change!

Now, updating “copyright 2018-2019” to “2020” isn’t.

Re:One Guy Ruined Hacktoberfest 2020 by rjmunro on Friday October 02, 2020 @06:23AM (#24661051)
The point of the date it to tell people when the material was created. In some jurisdictions / situations, copyright expires N years after it was created, so that date tells people when copyright has expired.

Unfortunately, in many cases now, copyright is based on the year the author died, rather than the year the work was created, which means it is much harder to work out if something has entered the public domain.

Changing the date without changing the code significantly is arguably fraudulent.

Re:One Guy Ruined Hacktoberfest 2020 by schwartzworld on Friday October 02, 2020 @09:35AM (#24662416)
doesn't moving the creation date forward in time make you vulnerable?

if you create some content in 2018 and I rip it off in 2019 and then you update your copyright to 2020, what's to stop me from saying I came up with it first?

Re:One Guy Ruined Hacktoberfest 2020 by rjmunro on Thursday October 08, 2020 @02:01PM (#24721872)
That's partly why you have a span like "Copyright 2018-2020" - you are saying some of this material is older, some isn't. You need to keep copies of the older version with the older copyright to be clear which parts were invented when.
Re:One Guy Ruined Hacktoberfest 2020 by 0xFluegel on Friday October 02, 2020 @05:41PM (#24667304)
I want to like that idea. Unfortunately, I can counter with: When you (as an outsider) see two very similar projects, one claiming to be from 2018 the other from 2020, what will you look into/try out first?
Re:One Guy Ruined Hacktoberfest 2020 by schwartzworld on Friday October 02, 2020 @07:26PM (#24668072)
Depends on the selling point. A 2 year old library sounds to me like it's just getting mature.
Re:One Guy Ruined Hacktoberfest 2020 by ric2b on Sunday October 04, 2020 @05:46PM (#24682505)
Obviously the one from 2018. It should still be quite modern but with big issues already ironed out.
Re:One Guy Ruined Hacktoberfest 2020 by noja on Friday October 02, 2020 @07:09AM (#24661349)
> Changing the date without changing the code significantly is arguably fraudulent.

In some countries the publishing date is what counts, and they define publishing for websites as when the site was viewed.

Re:One Guy Ruined Hacktoberfest 2020 by Zarel on Friday October 02, 2020 @03:34PM (#24666269)
Presumably, even if publishing date is relevant, it's only first publication that's relevant. No work should stay copyrighted forever just because it's constantly being republished.
Re:One Guy Ruined Hacktoberfest 2020 by noja on Sunday October 04, 2020 @03:01AM (#24677032)
> it's only first publication that's relevant.

No, the publishing date is relevant (not the first publishing date).

Re:One Guy Ruined Hacktoberfest 2020 by user5994461 on Monday October 05, 2020 @12:10PM (#24689023)
It's useful in showing the project is maintained and how old it is.

I regularly have to shop around for libraries. Seeing a copyright 2017 doesn't bode well for the documentation or the project being maintained.