nomination committer ci-management
|
Hi Mauro Sardara is a committer in cicn and hicn projects and has contributed quite a bit in ci-management. Below his contribution to ci-management, In hicn it would be helpful to have a ci-management committer to take care of our release management. Thanks Best Luca |
|
|
|
Vanessa Valderrama
Luca, Have you discussed this Mauro and verified he is interested in becoming a committer? Thank you,Vanessa
On 1/30/20 1:25 PM, Luca Muscariello
wrote:
|
|
|
|
+ Mauro yes of course, Mauro would be happy to become a committer in ci-management. Thanks Luca On Thu, Jan 30, 2020 at 8:37 PM Vanessa Valderrama <vvalderrama@...> wrote:
|
|
|
|
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
> In hicn it would be helpful to have a ci-management committer > to take care of our release management.
In ci-management, Gerrit does not allow an owner of a contribution to vote +2 on it, even if the owner is a committer. That means making Mauro a committer will not help Cicn nor Hicn directly, unless somebody else starts contributing the needed changes.
Overall, ci-management could use more active committers, I am just making sure the limits of their power are understood.
> https://gerrit.fd.io/r/q/project:ci-management+owner:msardara%2540cisco.com
In other words, that link does not give you the list of changes that could have gotten merged sooner if Mauro were a committer. This [1] link does.
Vratko.
From: tsc@... <tsc@...> On Behalf Of
Luca Muscariello
Sent: Thursday, January 30, 2020 8:41 PM To: Vanessa Valderrama <vvalderrama@...>; Mauro Sardara (msardara) <msardara@...> Cc: ci-management-dev@...; hicn-dev@...; cicn-dev@...; tsc@... Subject: Re: [tsc] nomination committer ci-management
+ Mauro
yes of course, Mauro would be happy to become a committer in ci-management.
Thanks Luca
On Thu, Jan 30, 2020 at 8:37 PM Vanessa Valderrama <vvalderrama@...> wrote:
|
|
|
|
On Fri, Jan 31, 2020 at 12:46 PM Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) <vrpolak@...> wrote:
Alberto takes care of the release update, so in that case it would be his responsibility to take care of ci-management as well. Mauro would take care of reviewing ci-management for what concerns these release phases jointly with Alberto and myself. In any case Mauro would continue to contribute to ci-management as usual. In the past we have had problems for patches on ci-management pending for too long. We are a small team and most of the time others do not pay attention to our own patches. Any dependency with people that are not directly committed to our projects means disruption and broken distributions to our user-base. It happened more than once. This is why we'd need one team member to pay attention to our own patches in ci-management too, in due time, especially during new release phases.
The above link is something Vanessa has asked me to send because TSC requires to see measurable contributions for a committer to be nominated candidate in a given project. But the link you've shared gives additional arguments, thanks.
|
|
|
|
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
> Alberto takes care of the release update, so in that case it would be > his responsibility to take care of ci-management as well. > Mauro would take care of reviewing
Alright then.
@Vanessa Valderrama Is this thread also for committer votes? If yes: +1.
Vratko.
From: Luca Muscariello <muscariello@...>
Sent: Friday, January 31, 2020 1:37 PM To: Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) <vrpolak@...> Cc: Vanessa Valderrama <vvalderrama@...>; Mauro Sardara (msardara) <msardara@...>; ci-management-dev@...; hicn-dev@...; cicn-dev@...; tsc@... Subject: Re: [tsc] nomination committer ci-management
On Fri, Jan 31, 2020 at 12:46 PM Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) <vrpolak@...> wrote:
Alberto takes care of the release update, so in that case it would be his responsibility to take care of ci-management as well.
Mauro would take care of reviewing ci-management for what concerns these release phases jointly with Alberto and myself. In any case Mauro would continue to contribute to ci-management as usual.
In the past we have had problems for patches on ci-management pending for too long. We are a small team and most of the time others do not pay attention to our own patches. Any dependency with people that are not directly committed to our projects means disruption and broken distributions to our user-base. It happened more than once.
This is why we'd need one team member to pay attention to our own patches in ci-management too, in due time, especially during new release phases.
The above link is something Vanessa has asked me to send because TSC requires to see measurable contributions for a committer to be nominated candidate in a given project. But the link you've shared gives additional arguments, thanks.
|
|
|