os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove text about handling software with GPLv3 upstreams.

Browse source 
While our ancient toolchain still falls into this category, we are
rapidly transitioning away from it and few if any bugfixes have been
merged from upstream in recent years.

Approved by:	core@
Differential Revision:	https://reviews.freebsd.org/D19356
This commit is contained in:
Benedict Reuschling 2019-03-09 18:26:04 +00:00
parent 28daf1309d
commit fd3ed382a7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=52852
1 changed files with 0 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
en_US.ISO8859-1/htdocs/internal/software-license.xml
View file

@ -73,26 +73,6 @@
</ul>
</li>
<li>
<p>We will allow existing GPLv2 licensed software to be
converted to GPLv3 or other similar license changes on a
case-by-case basis provided that the FreeBSD Core Team is
given appropriate technical justification.</p>
<p>Each piece of software that is being converted to a
different license must be submitted to the FreeBSD Core Team
for approval through this process as though it were a new
piece of software.</p>
<p>For Free Software Foundation maintained software except
GCC, GDB, and binutils, all patches posted after the date the
software switched to GPLv3 will be considered to be covered by
the GPLv3 and thus will be subject to this rule. For GCC, GDB
and binutils we accept the community practice of allowing
patches to be relicensed under GPLv2 at the patch author's
discretion. The author's permission must be documented in the
commit message for each patch that is committed.</p>
</li>
<li>
<p>Historically, the phrase 'All Rights Reserved.' was
included in all copyright notices. The BSD releases had it to