+1 from me
| | |
|
|
|
On 03/26/2021 00:16,Mark Waite wrote:
+1 from me.
On Thursday, March 25, 2021 at 3:55:16 AM UTC-6 Olblak wrote:
Hi Everybody,
I am currently collecting feedback about the best way to manage user access to
the Jenkins-infra GitHub organization and more specifically
Hi,
I requested myself to be added as a maintainer
for https://github.com/jenkinsci/amazon-ecs-plugin, I raised PR etc, all
done. However, I still cannot merge anything on this repo? Is there
something else I'm missing?
--
You received this message because you are subscribed to the Google
+1 from me.
On Thursday, March 25, 2021 at 3:55:16 AM UTC-6 Olblak wrote:
> Hi Everybody,
>
> I am currently collecting feedback about the best way to manage user
> access to the Jenkins-infra GitHub organization and more specifically for
> people who don't contribute anymore (whatever the
Recording of the regular governance meeting on Mar 24:
https://youtu.be/lIVWi3PSGoI. We discussed the recent news and upcoming
Jenkins events. Then we discussed the trademark transition to CDF and the
new Contributor License Agreement process we want to introduce. After that
we reviewed the
+1. I suggest we do the same for the jenkinsci organization.
We have quite a number of core maintainers who have stepped down. They are
still the org members, but having a team for these contributors would be
helpful.
On Thu, Mar 25, 2021 at 11:15 AM Carlos Tadeu Panato Jr
wrote:
> +1
>
> Em
+1
On Thu, Mar 25, 2021 at 10:55 AM Olblak wrote:
> Hi Everybody,
>
> I am currently collecting feedback about the best way to manage user
> access to the Jenkins-infra GitHub organization and more specifically for
> people who don't contribute anymore (whatever the reason).
>
> I recently
Hi Everybody,
I am currently collecting feedback about the best way to manage user access to
the Jenkins-infra GitHub organization and more specifically for people who
don't contribute anymore (whatever the reason).
I recently review user permissions on the Github Jenkins infrastructure