[Development] Proposal: Using Gerrit for new approver proposals?

Volker Hilsheimer volker.hilsheimer at qt.io
Wed May 22 09:52:20 CEST 2019

> On 22 May 2019, at 09:20, Alex Blasche <alexander.blasche at qt.io> wrote:
>> -----Original Message-----
>> From: Development <development-bounces at qt-project.org> On Behalf Of
>> Thiago Macieira
>> Sent: Monday, 20 May 2019 17:20
>> To: development at qt-project.org
>> Subject: Re: [Development] Proposal: Using Gerrit for new approver proposals?
>> On Monday, 20 May 2019 01:50:03 PDT Florian Bruhin wrote:
>>> What about using Gerrit to do so? I'm not sure how the repository
>>> would look (probably just text files with the proposal text)? Then
>>> people could +1 that change instead.
>> I'm neutral on this, so long as the announcement of the proposal is sent to the
>> list first.
>> The list is the ultimate decision-making body in the Qt Project. Just as QUIPs
>> record a decision made in the mailing list, the +1 for new approvers and
>> maintainers can be recorded in Gerrit.
> Because of this requirement to announce to everybody I actually think the list is the better media.
> In the end you shift the mail from the dev folder to the gerrit folder. Which one are you less likely to ignore?

Yes, nominating on the list, but the recording of the +1s, and also the implementation of the respective authorisation, should be made in a system that can be audited (and with a process that can be automated, rather than one that relies on someone clicking the right things in a console).

A version-controlled configuration file with user names and privileges would provide that, with the added benefit of making the list of approvers easily visible to everyone with read-access to the respective repo. Right now, only Gerrit-admins have that kind of insight, which is at the very least impractical.


More information about the Development mailing list