Re: nomination committer ci-management
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
@Vanessa Valderrama Is this thread also for committer votes?
If yes: +1.
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.