News for hackers. Stuff that matters.

A comment on I wrote to the address in the GPLv2 license notice (2022).

Re:I wrote to the address in the GPLv2 license notice (2022) by roywashere on Thursday April 24, 2025 @09:34AM (#43782565)
That reminds me on the time the FSF moved, they changed their address, and the open source product I worked on had to change their address in the license notices in our product:

https://github.com/moritz/otrs/commit/e845575e1848fd0124fb8d...

And of course, as happens more often, this issue was raised to us by Debian developers, who care a great deal about 'correctness'

[ Parent | on HN ]
Re:I wrote to the address in the GPLv2 license notice (2022) by craniumslows on Thursday April 24, 2025 @10:46AM (#43783474)
The FSF offices have moved again if you weren't aware. The new address is

Free Software Foundation 31 Milk Street, # 960789 Boston, MA 02196 USA

https://www.fsf.org/about/contact/mailing

[ Parent | on HN ]
Re:I wrote to the address in the GPLv2 license notice (2022) by collinfunk on Thursday April 24, 2025 @01:13PM (#43785076)
In Gnulib we distribute and use the license with just a link to <https://www.gnu.org/licenses/> [1]. I would just use that.

Many GNU projects use a rule that will fail 'make distcheck' when it sees an address in the sources [2].

[1] https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=bf31... [2] https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=086c...

[ Parent | on HN ]
Re:I wrote to the address in the GPLv2 license notice (2022) by pabs3 on Thursday April 24, 2025 @10:48PM (#43789672)
Hmm, I wonder if there is a linter somewhere for copyright notice and license grant smells.

Made a note to add an fsf-address check to check-all-the-things.

[ Parent | on HN ]