[Development] QUIP 12: Code of Conduct
Thiago Macieira
thiago.macieira at intel.com
Thu Oct 25 08:34:56 CEST 2018
On Wednesday, 24 October 2018 23:17:52 PDT Ulf Hermann wrote:
> > On Wednesday, 24 October 2018 22:52:20 PDT Ulf Hermann wrote:
> >> The QUIP process follows the lazy consensus mechanism. See QUIP 2 and
> >> QUIP 3. Jason Hihn is not an Approver.
> >
> > Approvership or maintainership are not required to state opinions.
>
> Correct. However, someone who is not an Approver can neither give a -2
> nor a +2 for a change on gerrit. Therefore the invitation to review the
> QUIP does implicitly say something about "earning a right".
What you state is correct, but also besides the point.
QUIPs are the writing down of community decisions. They were created to
summarise conclusions from the mailing list discussions. Approvership is not
required to participate in those. The Gerrit review system is later used to
perfect the language of the text, but not to change its essence. And you don't
need to be an approver to post comments there, or give +1 and -1 for that
matter.
I don't know of any contributions of code that Jason H may have made,
nonetheless his email deserves to be read and answered.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list