Date: Tue, 26 Feb 2019 09:33:30 -0800 (PST) From: "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> To: John Baldwin <jhb@freebsd.org> Cc: "K. Macy" <kmacy@freebsd.org>, Brooks Davis <brooks@freebsd.org>, Matt Macy <mmacy@freebsd.org>, svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers <src-committers@freebsd.org> Subject: Re: svn commit: r344487 - in head/sys: conf gnu/gcov Message-ID: <201902261733.x1QHXU0f046905@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <59e33dc7-cd10-7edd-9ff3-418d3eeef1f2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 2/25/19 5:11 PM, K. Macy wrote: > >> This commit needed more through review. > > > > How would this be achieved:? I had several people on the review and no > > one had substantive feedback. > > As a developer it is your responsibility to be aware of the policies that > we do document. One of the things in the license policy Brooks pointed you > at is that adding new GPL code requires core@ sign off. This doesn't mean > core@ will say know. It does mean that core@ has to make an explicit > decision. > > (I know Brooks said he intended to update the policy, but in fact it > already requires core@ sign off for any new code that isn't following > one of the accepted licenses which are all BSD/MIT-style licenses.) In defense of K Macy here, the copy of this text in the publically visible committers guide does not say that. Hence my earlier mail about is this text planned as an update to what is in the committers guide. Or can you point me to something in the public area that points at this /internal/license.html file? > -- > John Baldwin -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201902261733.x1QHXU0f046905>