[Development] Maintainer "TrustMes"
aschmidt at dekaresearch.com
Mon Apr 2 15:35:02 CEST 2012
Does the project maintain a list of "Subject Matter Experts"
from which 1) volunteers could be solicited or 2) reviewers
could be "drafted"? If not, *SHOULD* the project maintain
such a list?
Otherwise, it's as we saw in "T2"...
From: development-bounces+aschmidt=dekaresearch.com at qt-project.org [mailto:development-bounces+aschmidt=dekaresearch.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: Monday, April 02, 2012 09:22
To: development at qt-project.org
Subject: [Development] Maintainer "TrustMes"
One of the duties of a maintainer is to ensure that every contribution to the
code he/she maintains is being reviewed. That is, if no one else approves or
rejects, the maintainer has the duty to make that happen. I've done this in
the past and approved based on +1 given by other people, or by reviewing stuff
What are we supposed to do when no one else approves or rejects a commit that
we created ourselves? Or worse, when no one reviews at all?
My question applies mostly to QtDBus, since I don't expect most people will
know anything about that module. I've (ab)used Stephen's goodwill to review
simple things, but I don't expect him to understand the message delivery path
What is the suggested procedure?
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.
Please consider the environment before printing this email.
More information about the Development