engine-patches mailing list

[Itamar Heim]

On 06/09/2015 03:22 PM, David Caro wrote:
> On 06/09, Roy Golan wrote:
>> On 06/09/2015 02:45 PM, Omer Frenkel wrote:
>>>
>>> ----- Original Message -----
>>>> From: "David Caro" <dcaroest at redhat.com>
>>>> To: "Omer Frenkel" <ofrenkel at redhat.com>
>>>> Cc: "infra" <infra at ovirt.org>
>>>> Sent: Tuesday, June 9, 2015 2:19:42 PM
>>>> Subject: Re: engine-patches mailing list
>>>>
>>>> On 06/09, Omer Frenkel wrote:
>>>>> Hi,
>>>>> I've been monitoring the pending requests list for the engine-patches
>>>>> mailing list for a while now,
>>>> >from what i could see, no one send mails to this list except automated
>>>>> mails initiated at gerrit (which is pretty much expected).
>>>>> the rest is spam..
>>>>>
>>>>> this makes a requirement for people using gerrit (code contributors and
>>>>> reviewers) to subscribe to the list,
>>>>> and get all the mails on all gerrit activity.
>>>>> some people do not want to subscribe, and mails on their activity needs
>>>>> manual processing.
>>>>>
>>>>> maybe there is a way to have automated job to run daily/weekly to add all
>>>>> gerrit users to the accept list for this list?
>>>>> then i would change the list to automatically reject all mail from
>>>>> non-subscribers and users that are not in the accept list.
>>>>>
>>>>> what do you think?
>>>>> any other suggestion?
>>>>
>>>> see http://lists.ovirt.org/pipermail/devel/2015-June/010693.html
>>> how this affect the engine-patches mailing list administration?
>>
>> David why is engine-patches is needed at all? gerrit hooks are the one who
>> triggers ci jobs no?
>
> That seems a common misunderstanding, the gerrit hooks are not related to
> jenkins, jenkins connects to gerrit itself (has stream access) independently of
> the hooks.
>
> Clarified that, not sure why engine-patches is needed but I think itamar and
> some team leads use it to monitor activity. Though afaik that can be done
> subscribing to the project (maibe that feature was not available on gerrit
> before)

its not the same.
registering to the mailing list allows to see everything going through 
in batch.
registering to a project means no difference from patches you are added 
to directly.

having said this - I'm not sure engine-patches is that useful still. 
engine-commits still is.