Wikimedia Technical Committee/Essential duties
This page is currently a draft.
Coordinate handling of RfCs
This currently includes:
- Document and maintain the documentation of the RfC process
- Maintain, groom, and update the RfC-related phabricator workboards
- Committee members volunteer to be "shepherds" for specific RfC tasks
- Organize IRC discussions about RfCs, and posting the results
- Provide feedback to RfC owners
- Meet weekly as a committee to review and plan IRC meetings, monitor and update the status of active RfCs, and have specific high-level or framing discussions about specific RfCs
Approve (or deny) RfCs
The primary goal of the RfC process is to ensure that any major change has been documented and thought through, and has benefited from feedback and review by relevant and interested parties. In a sense, the process serves as a form of "whim dampener", increasing the odds that major changes are likely to remain good ideas for some years after they are implemented.
The architecture committee's responsibility is to assess and summarize how the relevant technical community feels about an RfC. To that end, they will provide guidance and help to the RfC proposer, so that the ideas within the RfC are communicated clearly to the appropriate people, and a rich discussion follows. While committee members are expected to participate in those discussions, their opinions are as individuals, not as powerful members of some committee. The RfC proposer is expected to answer clarifying questions, correct errors, and generally make the RfC complete and accurate.
As objections or concerns are raised, the RfC proposer is expected to treat concerns as legitimate, and address them. They might alter the proposal, or they could explain why, in their opinion, changes are not necessary. If an RfC is changed in significant ways, it should be subjected to another round of community review, in its new form. Legitimate responses to feedback could include "we disagree that <X> will be a problem", or "yes, <Y> is a possibility, but we are willing to accept the risk".
After a reasonable amount of time and discussion, the committee might "approve" or "deny" an RfC.
Approval of an RfC indicates that any concerns raised by the technical community have been acknowledged and addressed in some way. Members of the committee might personally disagree with the proposal, or harbor concerns. But their role is to reflect the consensus of the broader technical community. Approval of an RfC is indicated by adding the "ArchCom-approved" tag to the phabricator task. Developers who try proceed with a major change that has not been approved through the RfC process are likely to face questions and resistance.
Denial is a strong action, which the committee should not take lightly. It indicates that:
- The technical community has serious concerns that this RfC would be problematic or harmful, AND
- The proposer appears to be unwilling or unable to make changes that would solve the concerns.
Approval or denial is based on "consensus" of the committee members. The exact threshold for this consensus is not defined, and may vary depending on the scope and risk of the RfC in question. Again, this is not based on how the members themselves feel about the proposal, but rather on their interpretation of how the broader technical community feels.
Discussions about strategic/high-priority projects
This has mostly been ad-hoc. To bring it into the normal process, the RfC process documentation should be changed to make it clear that no idea is too large or audacious to be an RfC. Instead of discussing massive possible changes in unstructured ways, those ideas could be turned into an RfC, and then discussed through the normal RfC process. It's possible that a massive RfC might end up spinning off multiple smaller RfCs, as tangible steps to work toward the overarching goal.
Proposal: Robla should update the RfC documentation to explicitly allow/encourage RfCs that cover large, strategic proposals.