Hi FESCo members,
That title is too long, but correct in essence. For a few months, the Community Platform Engineering team has been reworking their approach to how they prioritise initiative-sized work requests, in consultation with the FPL, FCA & FOA. It was generally felt that the initiative work the team does could be more embedded in the wider Fedora Community, and the discussion and prioritisation of a work list could be done more transparently, and by a more appropriate group in the Fedora community than by the current group of people - team, team product owner, team management and a small set of stakeholders. As the technical leadership group in the Fedora project, the team felt you would be the ideal group to engage with them to prioritise requests the team receives, based on the engineering needs of the Fedora project.
I have created a wiki page for review and feedback, and will assign this ticket to me as the person responsible for the formation of a new process, and tag the proposal owners in this ticket for questions you may have.
There is a lot to digest in the proposal, and I am aware that we are going to be in the busiest part of the release cycle, so there is no immediate deadline to adhere to. However, it is my hope that we could trial this process post F40 release, which would give you a number of weeks to review and iterate on the proposal, while allowing the CPE team time to compile infrastructure projects to a backlog ahead of a prioritization meeting. I'm happy to put the above suggestion in an 'implementation timeline' section of the proposal if that's helpful.
[https://fedoraproject.org/wiki/CPE_Infrastructure_Projects Wiki Page]
@ashcrow @blc @humaton
Hi Aoife,
In general, I think FESCo would be happy to have some input the prioritization of CPE tasks and goals. But the proposed workflow seems rather strict. I think it'd be fine to have a much looser rules, and once the list of goals is known, people can informally decide what to work on at specific point in time without official approval. I don't think FESCo has the capacity to manage tasks and make such strict linear prioritization and to approve amendments to list in a timely manner.
I also think there's some internal tension in the proposal: on the one hand, "Anyone can work on items in the public Infrastructure Projects List", but on the other hand, "If an Infrastructure Project request is rejected a reason will be provided by FESCo and submitted to the original Infrastructure Project request before closing it. Not prioritizing on the list is effectively a rejection." We can't effectively reject proposals if people can work on them anyway.
In summary, if this is what CPE really wants, we could try this. But I would prefer a simpler approach where FESCo together with CPE makes short lists of high-priority and medium-priority tasks out of the overall queue, and updates it every one in a while, esp. when tasks are finished and removed from the list.
I propose a minor adjustment to the current process, suggesting the creation of a dedicated thread on https://discussion.fedoraproject.org/ specifically designated for discussions under the topic "Infrastructure Projects." This dedicated space aims to involve a broader audience, providing a platform for engagement and collaboration. Additionally, it serves as a foundation for generating actionable items for CPE.
I am volunteering to take on the role of moderating the Discourse thread and compiling the monthly reports. My responsibilities would include creating actionable items and presenting them to FESCO monthly in the form of a ticket here. This approach aims to enhance transparency, streamline communication, and improve the decision-making process within the Fedora community and with CPE.
Thank you @zbyszek and @humaton for your thoughtful replies. I brought this to the attention of the CPE management team and they would like to reword the proposal to something more simplistic, with the inclusion of @humaton 's idea of bootstrapping the process in discourse. From a council point of view, this is a +1 as this leverage's the platform in yet another way to unify community conversations. I would like to make a request on behalf of the CPE teams management that this proposal be added to a FESCo meeting sometime soon, and they would like to offer to attend and either present/pitch the proposal in more detail, but mainly to be available to answer any questions FESCo members might have.
Is there an upcoming meeting that has space on the agenda for this proposal to be added to?
Next Monday (19/02) should work. We only have one ticket there so far. But in general, feel free to set the meeting ticket here whenever the other participants are ready, and we'll just handle it on the next meeting. We can always put the item first, so that it's at predictable time and without risk of dropping.
meeting
Metadata Update from @ngompa: - Issue tagged with: meeting
Feb 19th is a bit too soon for me to finish making the requested modifications, summary, short slide deck, and peer review for those changes. Could we Feb 26th or Mar 4th? cc @jbley @ancarrol
@smilner I am ooo both dates but will catch up with you afterwards.
Metadata Update from @zbyszek: - Issue untagged with: meeting
Ok, if it's possible, let's do March 4th. I'll be around and I believe @ancarrol will be as well.
OK.
Metadata Update from @mhayden: - Issue tagged with: meeting
https://fedoraproject.org/wiki/CPE_Infrastructure_Projects has been updated with the tl;dr version and noting the usage of Discourse.
This was discussed during the FESCo meeting on 2023-03-04.
Proposal: FESCo agrees to assume responsibility for reviewing and aiding in the prioritization of Fedora Infrastructure Initiatives. The list will be maintained and presented to FESCo by the CPE team as needed.
!agreed FESCo accepts the task of reviewing priorities for CPE Infrastructure Projects (+8, 0, -0)
See https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-04/fesco.2024-03-04-19.30.log.html for the full discussion.
Metadata Update from @zbyszek: - Issue untagged with: meeting - Issue tagged with: pending announcement
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PMVLDXTL42YXFEUEI5NBBUSTCPJNNQFE/
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.