Hi Oleg, I totally agree with you, officer role are not one man jobs. I find it more accurate to highlight that they are about coordinating the different initiatives and finding contributors than being the person who's suppose to work on those.
> > I will add the topics to the today's governance meeting > > Best regards, > Oleg > > On Wednesday, October 7, 2020 at 12:43:49 PM UTC+2 Oleg Nenashev wrote: >> Dear all, >> >> As discussed at the previous Governance meeting, I suggest to revise the >> definition of Jenkins Officer roles listed on this page >> <https://www.jenkins.io/project/team-leads/>. These roles were defined in >> 2015-2016 as a part of the original officers proposal, and the effective >> responsibilities have drifted from the original descriptions. It would be >> great to update the role definitions ahead of the elections, so that the >> nominees and voters can see actual responsibilities. >> >> A few changes I would like to suggest: >> * Shift roles from doing the administrative/maintenance work on their own >> to coordinating the work inside the teams and SIGs led by the officers. >> While officers are responsible to ensure that the mission-critical community >> processes work, they are not expected to work on them single-handedly. More >> delegation and sharing responsibilities is a good thing for project >> sustainability. >> * Set expectations about onboarding new contributors to the teams, >> knowledge sharing, and facilitating contributions to the area of >> responsibility. All teams would benefit from having more contributors and >> clear requirements/ladder for those who want to take roles within the teams. >> * TBD: The bullet above might be even extended to having "shadow" or >> "deputy" officers as it was proposed by contributors in the past. Such >> approach could help to ensure healthy officer rotation in the project, with >> opportunity for officers to move on to other roles or to take a break when >> needed. >> * Add expectation about facilitating initiatives within the scope of the >> responsibility, and maintaining the team's roadmap. >> A while ago I submitted >> https://github.com/jenkins-infra/jenkins.io/pull/2943 for the event officer >> definition (follow-up to the previous PR by Alyssa Tong and Mark Waite). I >> suggest using it for collaborative editing of the role definitions. Please >> feel free to propose any changes in this thread or in the pull request. >> >> Best regards, >> Oleg Nenashev >> > > -- > 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/dbd6b25d-66a2-4907-9b7b-4ad73cd7df7cn%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/dbd6b25d-66a2-4907-9b7b-4ad73cd7df7cn%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/95e5479e-b906-4d25-891f-b2aed94aeea7%40www.fastmail.com.
