+1 for all candidates. FTR I would recommend making ICLA a prerequisite for Triage team as well. If everyone is fine, I will proceed with enabling EasyCLA for the https://github.com/jenkinsci/infra-cla repository so that we switch to a new flow instead of the PDF requirements
On Wednesday, November 3, 2021 at 8:01:17 AM UTC+1 [email protected] wrote: > +1 > > On Wed, 3 Nov 2021 at 06:48, 'Gavin Mogan' via Jenkins Developers < > [email protected]> wrote: > >> Sounds good to me. >> >> On Tue, Nov 2, 2021 at 4:04 PM Mark Waite <[email protected]> wrote: >> >>> During Docs Office Hours yesterday we discussed adding more people to >>> the copy editors team on Jenkins.io. The process that has been outlined >>> previously >>> <https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#teams-and-roles> >>> >>> is that we first assign people to the triage team, then mentor them for a >>> time. Once there is a pattern of contributed reviews, then the docs >>> officer or the contributor proposes that they be added to the copy editors >>> team. >>> >>> I propose that the following regular attendees at Docs office hours be >>> added to the jenkins.io triage team: >>> >>> - Kristin Whetstone <https://github.com/kwhetstone> - Google Summer >>> of Code mentor, Google Season of Docs mentor, pipeline steps doc >>> generator >>> author, regular participant in Docs office hours >>> - Dheeraj Singh Jodha <https://github.com/dheerajodha> - Jenkins >>> weekly changelog reviewer, regular contributor to Jenkins documentation, >>> regular participant in Docs office hours >>> - Meg McRoberts <https://github.com/stackscribe> - Jenkins training >>> author, contributor to Jenkins documentation, regular participant in >>> Docs >>> office hours >>> >>> During the mentoring period, they will also need to submit their >>> individual contributor license agreements. Once the mentoring period is >>> complete and the ICLA's have been submitted, we'll propose that they be >>> made copy editors. >>> >>> Mark Waite >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/c886e34a-513a-4366-b50b-76809e88afdan%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/c886e34a-513a-4366-b50b-76809e88afdan%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut8bka4iE6SoFfVHLjmP%2B6_gK0ipzJ-bLq2ump7L-Ku1Q%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut8bka4iE6SoFfVHLjmP%2B6_gK0ipzJ-bLq2ump7L-Ku1Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e1476679-4c47-4d1e-88ee-cd9b62b4b745n%40googlegroups.com.
