---
# System prepended metadata

title: Email - Fedora - RFR to initiatives
tags: [' initiatives', email, ' infra']

---

---
title: Email - Fedora - RFR to initiatives
tags: email, infra, initiatives
---

Subject: RFR to initiatives?

Good Morning Everyone,

Our current procedure for Request For Resources (RFR) [1] involves a number of steps that are all nicely documented and necessary but ends up relying pretty much only on the Fedora Infrastructure team.
Meaning, it is on us to accept/reject a request for resources and our track records shows that even when we accept a request because it checks all the tick boxes, most often, at some point, it ends up on the CPE team to keep the service running.

For this reason, I would like to propose that we migrate our RFR process to the initiative process [2].
This would mean that the CPE stakeholders will be involved in evaluating the needs and importance of the application that is being asked to be deployed. It also means that the decision to approve or reject a RFR will no longer be solely on us (we will still be involved in it, but we will no longer be alone in that decision).
It will also require that RFR be filled with enough lead time for it to be investigated and evaluated at the quarterly planning meetings. RFR due ASAP will no longer be an option (or rather, that as soon as possible will only be whenever the next meeting is).

What do you think of the idea? +1/-1/rotten tomates?

Thanks,

Pierre


[1] https://docs.pagure.org/infra-docs/sysadmin-guide/sops/requestforresources.html
[2] https://docs.fedoraproject.org/en-US/cpe/initiatives/