sips
sips copied to clipboard
stacksgov
First step towards submitting a SIP
The README should provide a reasonable first step in the process of submitting a SIP, such as suggesting starting by posting a new issue here with an initial proposal for the SIP.
SIP 000 provides an high-level overview of the SIP process but not a practical first step. The SIPS README in the sips directory suggests that New SIPs may be submitted via pull request. Having to submit a pull request as a first step sets the bar high for engaging with the SIP process, which @GinaAbrams argues in issue #73 already has a high barrier to entry for folks that don't use GitHub day in and day out.
Posting a brief proposal for a new SIP in the issue tracker will lower the barrier to entry and open for further onboarding and hand-holding (if required).
The README should provide a reasonable first step in the process of submitting a SIP, such as suggesting starting by posting a new issue here with an initial proposal for the SIP.
SIP 000 provides an high-level overview of the SIP process but not a practical first step. The SIPS README in the sips directory suggests that New SIPs may be submitted via pull request. Having to submit a pull request as a first step sets the bar high for engaging with the SIP process, which @GinaAbrams argues in issue #73 already has a high barrier to entry for folks that don't use GitHub day in and day out.
Posting a brief proposal for a new SIP in the issue tracker will lower the barrier to entry and open for further onboarding and hand-holding (if required).
Hi @njordhov, I agree with you. And you can see my comments in Gina's thread as well.
-
There should be simpler process to pitch in your SIP ideas & SIP proposals.
-
I've recently submitted a Residency for SIP under Stacks Foundation. And I plan to tackle exactly the type of thing you mentioned above.
-
If I am lucky enough to be a SIP Resident, I will be facilitating the SIP proposal process and clarify & update the documentations accordingly, plus gathering valuable feedback like yours.
This Friday 11am EST, there is a SIP Community call, anybody is welcome to join and voice your comments. Please join us!
Here you can add this weekly SIP chat to your Google (or others) calendar: https://community.stacks.org/events#event=72322254;instance=20220701110000?popup=1
Let me know anything else you feel the process need to improve!
There should be a process in place to handle incoming SIP proposals on the issue tracker, such as having a SIP editor respond to the proposal in a timely manner.
Do we have a way to consistently tag SIPs with the consideration boards they pertain to or that the author maybe provides as an opener - "technical," "economic," "governance" etc - is it possible e.g. to build a filter for this maybe via an external system?
For brief SIP proposals posted in the issue tracker, the responding editor could use github's tagging system to suggest a classification, making it listed as a card on the matching project table.
@radicleart Do we have a way to consistently tag SIPs with the consideration boards they pertain to or that the author maybe provides as an opener - "technical," "economic," "governance" etc - is it possible e.g. to build a filter for this maybe via an external system?
Why not just tag them with github tags? Then, each CAB member can just filter PRs by their respective tag.
Per today's weekly SIP call, a very first step should be announcing the proposed SIP in a new #sip channel on the Stacks discord messaging system.