Hi Everyone,
As we kick off our team's work for Quarter 3 of this year, we would like to take this opportunity to ask for your feedback on our engagement over the last few months.
The CPE has been working on trying to improve our communication with our communities and increase visibility on how we decide on what to work on. We have taken many steps to improve our communication such as IRC Office hours, regular initiative updates on our taiga board, weekly mail and blog posts on what we achieved in each quarter and what we are planning to work on next. We have also had a few discussions before with some Fedora Council and CentOS Board members on how best to engage with the CPE Team when you wish to brief in an initiative or need to file a bug/issue/enhancement, and as time goes by we are refining our processes. We would like to share with you our current approaches that we are using for you to provide feedback on how you feel these are working.
It is important for our team to feel like their time is protected so that they are able to enjoy a healthy work-life balance, so we have categorized work requests that the team responds to into two categories which we believe benefits both the CPE team and the communities we serve:
- Project Teams - These teams are created based on an initiative that has been: - Received by our product owner in advance - The work involved has been scoped, reviewed and accepted to the backlog by the CPE Review Team - Prioritized and actioned for work during our teams quarterly planning sessions by CPE Team Stakeholders and Review Team
- Sustaining Team - This team responds to 'lights on work' and requests that come in on an ad hoc & regular basis such as: - BAU infra/releng requests - RFEs - Bug fixes
## How we propose to deal with Project Team Initiatives?
* We have published deadlines for initiatives to be briefed into our team by for each quarter here: https://docs.fedoraproject.org/en-US/cpe/time_tables/ * Project requests that are recieved are then discussed further with the requestor and relevant team lead(s) with our product owner * During our monthly quarterly planning sessions, the CPE Review Team reviews and prioritises which proposals to scope. * All scoped proposed initiatives are brought into our QP session for review and consideration to be worked on in the next quarter. * Our CPE Review Team review all and vote on the initiatives they would like to see actioned in the next quarter. Our CPE Review Team include: * Fedora - mmiller, mnordin, bcotton * CentOS - rbowen, bex * RHEL - bex, dperpeet, aslobodova * CPE - * CPE Product Owner - amoloney * CPE Management - lgriffin, antcarroll, smattejiet * CPE Team Leads - pingou, bstinson
As a picture is worth a thousand words, so here is one :)
Image Credit goes to Smera Goel, the very talented graphic designer that is currently interning as part of the Fedora Outreachy Project.
## How we propose to deal with Sustaining Team BAU requests, RFEs and bug fixes?
In order to allow the people working on initiatives to focus on them, our Sustaining Team members will be responsible for dealing with all these requests. They can be filed in the normal ways by community members.
BAU infra requests can be made on the fedora-infrastructure issue tracker: https://pagure.io/fedora-infrastructure/ BAU releng requests can be made on the releng issue tracker: https://pagure.io/releng/
## Project Team vs Sustaining Team Work Classification
### Project Initiatives Initiatives are weeks to months long projects involving a team of people to work on and deliver.
We have some deadlines that we try to work towards Examples of initiatives: - rawhide package gating - FAS replacement - ...
### BAU infra/releng requests Business As Usual (BAU) requests are simple requests that do not need anyone to code something, just run some code to solve the request.
Examples of BAU requests: - A new mailing list - A new FAS/dist-git/copr group - A new IRC channel - A new project on ci.centos.org - A new tag in koji
### RFE
Requests For Enhancements (RFE) are requests to improve a changes made to either an application or a workflow used in Fedora.
### Bug fixes
Bug fixes are what they are, request to fix bugs.
Examples of bug fixes: - Well you know: https://github.com/fedora-infra/bodhi/issues or pagure.io/pagure/issues are full of them ;-)
This is our team's current way of working, and we are seeing the benefits from this but wanted to have your feedback too. We would like to publish this as a 'policy' of sorts for our team on docs.fpo and on the CentOS wiki and want to include you in this process. So what are your thoughts on these ideas? Are they suitable for you or do they need more adjustments? If they do, what are your suggestions?
To view this email in hackmd, please visit this link https://hackmd.io/xgkPVcv1Swuy9U-wGiKQPw?view
Looking forward for your feedback,
Aoife