Proposed process for Core Dev decision making

[luckyparadise]

New Process Adoption for Core Dev Decision-Making and Communication Enhancements

Please read in conjunction with the recording from Core Dev No 66 HERE

In light of the valuable discussions and feedback from our recent Core Devs meeting, I am proposing we adopt a refined process for managing how we make ad hoc decisions including time-sensitive ones while at the same time documenting these decisions and the rationale behind them. This approach is designed to address the challenges identified, particularly around achieving swift consensus and enhancing the clarity and accessibility of decision-making.

Our New Approach

Recognizing the need for a more responsive and streamlined process, I suggest we integrate several key mechanisms into our workflow. These changes should not just be proposals but steps we should actively take, with the understanding that Core Dev feedback will be essential in fine-tuning and activating these processes.

Immediate Actions

• GitHub Issues and Tags for Prompt Documentation: We're implementing the use of GitHub issues and tags to document and highlight urgent decisions or discussions required from Core Devs. This will ensure that critical items are quickly brought to attention and not lost amidst other communications, particularly in Slack. Core Devs are encouraged to weigh in when these issues are brought up. Governance TPMs will assist in preparing documentation to guide debates and shepherd the team to arrive at a logical decision based on input made, however, Core Devs alone will drive this process.
• GitHub Discussions for Detailed Analysis: For a more in-depth exploration of issues or a decision to be made, including proposed solutions and their implications, GitHub Discussions will be utilized. This will allow for structured and accessible debates on various proposals, with all related discussions being interlinked in both the document and the issues thread in GitHub for ease of navigation. One of the main reasons for doing this is to also be more open in our decision-making and processes. While utilising Slack is great for internal discussions, but when it comes to deciding on a subject matter, it is better to have open discussions in the Core Devs discussion thread.
• FIPs Moving to Last Call: Would it be better if FIPs ready for Last Call are opened as a PR for some time for Core Devs to offer feedback before they formally move to Last Call phase? Practically, only FIP Editors will be able to do this as they are the first line of contact with Authors when FIPs are ready for Last Call. I am only concerned that the FIP Editors are usually contributors with immense workload thereby making the implementation of this procedure difficult or inconsistent. In this regard, it is my recommendation that we maintain the current practice. The Governance Project Manager (Lucky Nwachukwu) will obtain Core Dev input before any FIP moves to Last Call.

Maintaining Effective Communication

• Enhanced Use of Core Dev Slack Channel: While integrating new tools, the Core Dev Slack channel remains our primary platform for immediate communication and updates, ensuring that the dynamic exchange of ideas continues unabated.
• Encouraging Asynchronous Participation: To accommodate the global nature of our community, asynchronous discussions will be emphasized, enabling all Core Devs to contribute to conversations at their convenience.

Future Considerations

• Development of a Notification Bot: To further streamline our process, we're considering the development of a bot that would automatically notify Core Devs of new issues or discussions requiring their input. This tool would serve to enhance responsiveness and engagement across our team.
• Periodic Review and Feedback Sessions: Implementing regular sessions to review the effectiveness of these new processes and gather feedback for continuous improvement.

Seeking Feedback and Collaboration

I invite all members to share their feedback on these changes and suggest any additional measures that could further improve our decision-making and communication processes.

I welcome your input and comments.