Description
Description:
Proposing a trial of SIP Deputies—a role designed to support SIP authors throughout the proposal process. The concept is inspired by the recently updated (March 2025) BIP Process, which introduced the role of BIP Deputies: stand-in owners who can help advance a proposal, support the original authors, or serve as points of contact when authors are unavailable [BIP-0003]. Similarly, through our experience coordinating 10+ SIPs in recent years, we’ve seen how dedicated support roles can help authors keep proposals moving and ensure they don’t stall unnecessarily.
As stated in BIP-0003:
"Authors may want additional help with the BIP process after writing an initial draft. In that case, they may assign one or more Deputies to their BIP. Deputies are stand-in owners of a BIP who were not involved in writing the document. They support the authors in advancing the proposal, or act as a point of contact for the BIP in the absence of the authors. Deputies may perform the role of Authors for any aspect of the BIP process unless overruled by an Author. Deputies share ownership of the BIP at the discretion of the Authors."
Rationale
SIP authors are often developers who focus their time on coding, rather than coordinating decentralized input and feedback, which is critical for advancing SIPs. From past experience, we’ve seen a need for dedicated coordination support to help with:
Engagement: Keeping discussions active and collecting community feedback.
Awareness: Ensuring SIPs are properly introduced to relevant stakeholders.
Education: Clarifying SIP details to improve accessibility.
SIP Deputies fill this gap by assisting authors with communication, coordination, and process management, allowing developers to focus on technical work while ensuring proposals receive the necessary input and attention.
(Proposed April 3, 2025)
SIP Deputies
SIP Deputies are individuals designated to assist SIP authors throughout the proposal process, ensuring clarity, consistency, and efficient communication. Deputies act as supportive facilitators who may help with author-related tasks in the authors' absence or when requested by the authors.
Responsibilities of SIP Deputies
-
Supporting Authors: Provide guidance and support to authors in preparing and refining SIPs to meet the required standards for submission and review.
-
Facilitating Communication: Act as points of contact for authors, reviewers, and community members to promote effective dialogue and feedback.
-
Tracking and Advancing SIPs: Monitor authors' SIP discussion threads on the Stacks Forum and GitHub, prompt feedback, keep conversations active, and ensure timely reviews and updates in relevant repositories.
-
Maintaining Continuity: Serve as proxies to continue the progression of SIPs if authors are unavailable or unable to fulfill their responsibilities.
-
Raising Awareness & Education: Assist authors in raising awareness about their SIPs through educational efforts, community presentations, and accessible explanations to enhance understanding and engagement.
Unlike other committees, Deputies are not responsible for determining whether a SIP meets the criteria to transition between statuses. Instead, they support authors by facilitating stakeholder feedback, promoting clear communication, and helping ensure steady progress throughout the SIP process.
Each SIP will have at least one dedicated Deputy, allowing the author to work closely with a consistent point of support. Deputies’ actions can be overruled by the original authors at any time.
Current Deployment
-
Planning to assign a SIP Deputy to support Friedger’s SIP proposal: Improved stacking #211
-
The SIP Deputies model extends beyond the formal SIP process. It has already been applied in a non-SIP context—specifically BNSIP-001 (Zonefile Structure)—where it has proven valuable in facilitating discussions. For example, @dantrevino and @eriqferrari, who are leading the BNSv2 zonefile efforts, now have a dedicated coordination point of contact to help keep momentum and advance the conversation.
-
The goal is to drive shared standards and foster productive dialogue across different parts of the ecosystem. This includes leveraging public platforms like the Stacks Foundation's SIP call on X and DeOrganized Media livestreams to bring visibility and cohesion to key proposals.
-
Current SIP Deputies:
-
(1) PeaceLoveMusic
GitHub: @PerrinoProperties
X (Twitter): @PeaceLoveMusicG -
(2) Haddy
GitHub: @behaddy
LinkedIn: https://www.linkedin.com/in/brendyn-hadfield/
X (Twitter): @BrendynHadfield
-
Call To Action (CTA)
- If you're interested in joining the SIP Deputies group—or if you have a SIP in progress that you'd like support with—feel free to DM either of us!
- This trial will help us observe and refine the role for broader adoption. Feedback is welcome! 🚀
Next Step: Data gather, refine, propose adding to SIP-000
-
Will observe the effectiveness of SIP Deputies and continue engaging with SIP Authors to understand what support would improve their experience with the SIP process.
-
Once the SIP Deputies trial demonstrates clear benefits, I will lead the effort to draft a proposal for incorporating SIP Deputies into SIP-000 as a standard part of the SIP process.