> (though there's a couple surprising names on that list)
People on that list didn't complain when I introduce that special *team* :p
That being said, reviewing permissions on a regular basis is important and
having an "alumni" or an "emeritus" team is one of the best way to keep
maintainers
Infra has an Alumni team (though there's a couple surprising names on that
list) which is essentially the same thing.
https://github.com/orgs/jenkins-infra/teams/alumni
Thanks for all your done, but as a non active contributor its risky to give
you write access to things.
Gavin
On Mon, Sep 27,
I'm not that much concerned that we wouldn't do exactly what Apache does
TBH. More of an inspiration.
IOW, we could just create a special team with no permission of "emeritus"
members. People in jenkins/core that we know have not been active since 1+
year anywhere.
And when in doubt, we'd double
At Apache, emeritus status is typically requested by the individual.
That might be hard to emulate here if some otherwise emeritus members
of Jenkins aren't here to request emeritus. Some forms of active
versus inactive members could be useful, though, for code review
purposes and other
We've got +1s from most of the active Jenkins core maintainers. I went
ahead and added Basil to the Jenkins core team.
Thanks to everyone for the votes!
On Thu, Sep 23, 2021 at 11:08 AM Raihaan Shouhell
wrote:
> +1 he has been leading the charge on a variety of improvements
>
> On Thu, Sep 23,
+1 we have this in jenkins-infra
On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus wrote:
> Hi all,
>
> Following up on Jesse's comment, and as I was reflecting on this a few
> days ago: I think we should introduce an Emeritus concept/status for
> Jenkins core team's inactive members.
>
> That
Hi all,
Following up on Jesse's comment, and as I was reflecting on this a few days
ago: I think we should introduce an Emeritus concept/status for Jenkins
core team's inactive members.
That would allow "cleaning up" the list for various reasons, while still
recognizing the contributions of such
+1 he has been leading the charge on a variety of improvements
On Thu, Sep 23, 2021, 4:25 PM Baptiste Mathus wrote:
> +1. IMO Basil is wa past the minimum criteria to get this status.
>
> Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev a
> écrit :
>
>> Dear all,
>>
>> Basil has been a very
+1. IMO Basil is wa past the minimum criteria to get this status.
Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev a
écrit :
> Dear all,
>
> Basil has been a very active contributor to the Jenkins core since 2020,
> and he has contributed a lot to Jenkins over the past several years. He is
> an
Thanks, everyone. I would be happy to join the core team. It has been
a fun ride since jenkinsci/jacoco-plugin#45. Good times, and a lot of
work, ahead.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and
+1, (if you want it Basil)
On Wed, 22 Sept 2021 at 14:32, Mark Waite wrote:
> +1 from me
>
> On Wed, Sep 22, 2021, 4:49 AM 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> > On 22. Sep 2021, at 11:14, Oleg Nenashev
>> wrote:
>> >
>> > It would be great
+1 from me
On Wed, Sep 22, 2021, 4:49 AM 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
>
>
> > On 22. Sep 2021, at 11:14, Oleg Nenashev wrote:
> >
> > It would be great to have Basil joining the Jenkins core maintainers
> team. I propose to officially add Basil
> On 22. Sep 2021, at 11:14, Oleg Nenashev wrote:
>
> It would be great to have Basil joining the Jenkins core maintainers team. I
> propose to officially add Basil to the Jenkins core team. IMHO the code
> reviewer stage can be skipped, because he has been already contributing a lot
> to
To Jesse's point, I'm plus one for the cleanup. In the maintenance guide we
set an expectation people could be demoted if they didn't contribute in the
last 6 months. Currently it's not written in the documentation explicitly
but I would be happy to support such a policy
Let's discuss it in a
+1 as well, really involved in the community so it's just natural :-)
On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
> If he is interested, absolutely +1!
>
> By the way there are a number of people in
> https://github.com/orgs/jenkinsci/teams/core/members who are no
If he is interested, absolutely +1!
By the way there are a number of people in
https://github.com/orgs/jenkinsci/teams/core/members who are no longer
active in the Jenkins community and who should likely be removed.
--
You received this message because you are subscribed to the Google Groups
Dear all,
Basil has been a very active contributor to the Jenkins core since 2020,
and he has contributed a lot to Jenkins over the past several years. He is
an active community member, and he helps a lot with the technical debt
cleanup and code reviews in Jenkins.
It would be great to have
17 matches
Mail list logo
