Date: Wed, 24 Oct 2018 06:59:42 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-stable@freebsd.org, freebsd-net@freebsd.org, freebsd-arch@freebsd.org, freebsd-fcp@freebsd.org Subject: Re: FCP-0101: Deprecating most 10/100 Ethernet drivers Message-ID: <201810241359.w9ODxgF8028397@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <CANCZdfr3%2BnHYMT3cZY75Px776G2g_SkKKos7zS3mLsvWZMgN_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
... deleted ... ... cc list trimmed, getting too many recepient gripes from mailman ... > > > > diff --git a/fcp-0000.md b/fcp-0000.md > > > > index b4fe0f3..c8cc6f7 100644 > > > > --- a/fcp-0000.md > > > > +++ b/fcp-0000.md > > > > @@ -144,7 +144,10 @@ When the discussion of a change has come to a > > suitable > > > > and acceptable close it > > > > SHOULD be updated to the `vote` state. > > > > > > > > At this time the FreeBSD Core Team will vote on the subject of the > > FCP. The > > > > -result of vote moves the FCP into the `accepted` or `rejected` state. > > > > +result of vote moves the FCP into the `accepted` or `rejected` state. > > The > > > > +core team MAY make minor edits to the FCP to correct minor mistakes. > > Core > > > > +MAY return the proposal to the submitter if there are major problems > > that > > > > +need to be addressed. > > > > > > This is a Bad Idea, because it relies on common understanding of what is > > minor. I was once involved with a standards body that had a procedure for > > so-called clerical errors intended to deal with typos, punctuation etc; > > this worked just fine until somebody claimed that the omission of the word > > ?not? in a particular place was clearly a clerical error. > > > > And I have read case law that boiled down to the presents vs absence > > of a comma in an agreement that had results far beyond "minor". > > > > Use of words minor and major should be red flags unless both > > or explicitly defined, and even then those definitions often > > have issues themselves. > > > > I'm not going to define every single word. FCP documents describe process. > They are not legal documents, nor should they be. Major and minor have > common enough meanings, and the basis of bylaws is that we trust core@. The trust isssue is not core (though in this specific case it is a core member submitting the FCP, that is not going to be the case always). The trust issue is do we allow the Author to make this minor/major change decission and how does core get informed that it has happened? -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201810241359.w9ODxgF8028397>