svn commit: r344487 - in head/sys: conf gnu/gcov
Rodney W. Grimes
freebsd at pdx.rh.CN85.dnsmgr.net
Tue Feb 26 18:08:10 UTC 2019
> On 2/26/19 9:33 AM, Rodney W. Grimes wrote:
> >> 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?
> Things on internal/ are "public" as far as developers are concerned. The
> title of https://www.freebsd.org/internal/policies.html is "Policies for
> FreeBSD Project Members" and references the committers guide as well as
> additional policies rather than the other way around.
And when is a new/returning committer refered to this document?
I do not recall being ever told about it.
I was refered to the committers guide.
> John Baldwin
Rod Grimes rgrimes at freebsd.org
More information about the svn-src-all