71–80 of 112 posts
Just curious what arrangement theses people have. -do their employers recognize their effort and give hours to the side projects? -they mostly contractors so can arrange their time accordingly? -donations? -or is it mostly a hobby done out of passion?
No payment, not a hobby, very little passion, doing it because the public needs it. (And possibly got started because, damn it, somebody had to write it / take over maintenance.)
Earlier quoted context omitted.
And most of what happens in those utilities is updating the copyright year numbers.
Which seems wholly unnecessary. The way I understand it, having only the starting year is sufficient.
Nevertheless I wouldn’t dare make any claim on this. Even in the presence of the Berne convention (https://en.wikipedia.org/wiki/Berne_Convention) the world is large and diverse.
Time Zone Database https://github.com/eggert/tz/graphs/contributors https://en.wikipedia.org/wiki/Tz_database
This is a good answer. Especially in the light of the 2021 drama and the maintainer's benevolent dictator status. What happens when the community disagrees with a benevolent dictator's decision? https://lwn.net/Articles/870478/
They discuss it, try to come to a compromise, and if all else fails, fork it.
Maybe it's not ideal, but then again, people seem to have a big problem when you have 'boards' running these projects too, so...
Earlier quoted context omitted.
> maybe also: sqlite [...] SQLite won't accept contributions from outside the core team; joining the core team is an involved process, as they're taking extreme measures to ensure it will continue to be recognised as a work in public domain in as many jurisdictions as humanly possible. You can still support the project by paying them for their work (or by getting your employer to do so): https://www.sqlite.org/prosup…
My understanding was that you could absolutely contribute without joining the core team, but you do need to file some paperwork to ensure that code can remain in the public domain. The need for the legal paperwork is that public domain is not a thing in multiple countries.
TL;DR: they have a company that legally employs every single co-author, to be able to sell you a Warranty of Title, just in case your company/jurisdiction/etc has a problem with public domain.
Earlier quoted context omitted.
Which seems wholly unnecessary. The way I understand it, having only the starting year is sufficient.
Absent any changes in a year, the copyright year shouldn't be updated. Otherwise what you're claiming is that the copyright term starts from a date after creation of the content, so it's getting artificially extended.
New editions of books have new copyright years, since they’re new books.
Same thing with code