gbranden pushed a commit to branch master
in repository groff.
commit ca33a1b680aec5a49af4653c61c7c182c54e3fa7
Author: G. Branden Robinson <[email protected]>
AuthorDate: Fri Dec 12 15:10:09 2025 -0600
groff(1): Revise copyright notice.
Ratchet back ending year of FSF copyright notice to 2024, reflecting the
date of the last contribution to this file by anyone but me.
Add copyright notice for myself. I have never executed copyright
assignment paperwork with the FSF, so my "legally significant"[1]
changes to this file can't be under the FSF's copyright.
Justification (commit ID, summary, net lines added by commit):
2018 26be5ad7be groff(1): Recast installation directory material. (+31)
2019 4e5439d982 {g,n}roff.1.man: Give assistance to pager users. (+22)
2020 93aa422ab4 groff(1): Rewrite "Macro packages" subsection. (+60)
2021 7cf56b8eea Document use of SOURCE_DATE_EPOCH and TZ. (+22)
2022 0189723a11 [docs]: Update introductory explanation of groff. (+29)
2023 a9767ace3d [man pages]: Define page-local `MR` fallback. (+15)
2024 7249739b38 groff(1): Replace Texinfo markup. (+2)
2024 a08908f982 [man]: Revise and expand `SY` and `YS` behavior. (+4)
2024 2ae27f9608 groff(1): Fix missing words. (+2)
2024 a27a37d331 [groff]: Revise exit status computation. (+7)
2024 1e76294d21 [doc,man,ANNOUNCE]: Recast our elevator pitch. (+1)
2025 3a1b01474d [groff]: Enable "locking" safer mode (3/3). (+17)
Commits 7249739b38, a08908f982, 2ae27f9608, a27a37d331, and 1e76294d21
meet the 15-line threshold taken cumulatively. (The GNU Maintainers'
Guide does not advise for or against a cumulative interpretation.
Applying rigidly simplistic rules supporting or opposing such an
interpretation each lead to seeming absurdities. On the one hand, 15
different minor changes, like incrementing an integer, to a single line
of code--or code comment--in the source file could become "legally
significant". On the other hand, if a person contributes a net
_deletion_ of lines overall, perhaps by eliminating dead code or
withdrawn functionality, they could prevent recognition of their own
contribution(s) of any size as "legally significant" as long as those
changes added fewer than <lines deleted> + 15. Counting lines of code
may be as poor a metric of copyrightability as it is of programmer
productivity.[2])
[1] "A change of just a few lines (less than 15 or so) is not legally
significant for copyright." Conversely, >= 15 lines would be.
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
[2]
https://www.researchgate.net/publication/335535826_The_End_to_the_Myth_of_Individual_Programmer_Productivity
---
src/roff/groff/groff.1.man | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/roff/groff/groff.1.man b/src/roff/groff/groff.1.man
index 330a595ea..87755eeea 100644
--- a/src/roff/groff/groff.1.man
+++ b/src/roff/groff/groff.1.man
@@ -9,7 +9,8 @@ document formatting system
.\" Legal Terms
.\" ====================================================================
.\"
-.\" Copyright 1989-2025 Free Software Foundation, Inc.
+.\" Copyright 1989-2024 Free Software Foundation, Inc.
+.\" 2018-2025 G. Branden Robinson
.\"
.\" This file is part of groff, the GNU roff typesetting system.
.\"
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
