search

stacksgov / sips

Community-submitted Stacks Improvement Proposals (SIPs)
135 stars 81 forks source link

Stacks Improvement Proposal Process #73

Open GinaAbrams opened 2 years ago

GinaAbrams commented 2 years ago

Hey Stacks fam! I wanted to start a discussion around the governance process and specifically a high barrier to entry for folks that don't use GitHub day in and day out. A core part of any community's governance is access to information and clear paths for engaging. Recent experiences in exploring the SIP posting process have highlighted the nuances of posting SIPs that make it difficult for the broader community to participate, and I wanted to start this discussion to propose that the current process should be reconsidered.

See the instructions listed here:

Submitting a Pull Request Pull requests are welcomed and encouraged! Please follow this general procedure: Fork/clone the repository Create a new branch related to the PR: git checkout -b my-branch-name Make changes and push to your fork Submit a pull request for review

While this may be straightforward to some, for the rest of us it creates extra friction right off the bat where research is needed before even considering posting a SIP. When Ethereum Improvement Proposals and Helium Improvement Proposals are in the discussion and discovery phase, discussions happen in real time (added to meeting agendas) and not through PRs on GitHub.

My proposal to the community is that formal communications on SIPs should be able to happen on the Stacks Forum and in meetings (maybe the Weekly Stacks Blockchain Engineering Calls) ahead of SIPs being formally posted as PRs to GitHub. This would make it a lot easier to engage with and digest content without the barrier to entry.

What do others think?

jcnelson commented 2 years ago

That all sounds good to me for draft SIPs, since they're still being punched up.

But I do believe that once a SIP is accepted -- i.e. it's ready for review and has a SIP number assigned -- it should be available on Github. This is because unlike a forum, Github will preserve both contextualized comments and the edit history -- both of which are valuable for CAB members to submit feedback and audit a SIP's evolution in response to it.

GinaAbrams commented 2 years ago

Thanks for the input @jcnelson! Think we're aligned 🙂

joberding commented 2 years ago

While this may be straightforward to some, for the rest of us it creates extra friction right off the bat where research is needed before even considering posting a SIP. When Ethereum Improvement Proposals and Helium Improvement Proposals are in the discussion and discovery phase, discussions happen in real time (added to meeting agendas) and not through PRs on GitHub.

Gina, Thanks for bringing this up.

Your post is in line with a recent discussion in the Governance working group and an issue raised by @Hero-Gamer. I agree that there should be general meetings on draft SIPs (as well as an option for async discussion IMO) but adding it to the developers/miners/builders meetings may not be the answer for meaningful community SIP education. My suggestion is a monthly SIP meeting with an opportunity for Q&A and post-meeting async discussion in the Stacks Discord Web3gov channel.

Hero-Gamer commented 2 years ago

Hi Gina,

Love you are also thinking about this topic! I agree barrier to participate or even be aware of what's going on for an average non dev end user of Stacks is just too high if things were just happening on Github.

I've been super into the process of BIP lately due to the BIP-119, and feeling very inspired that we can take a lot of learning from Bitcoin's decentralization ethos and activation process over to SIP given the context of Stacks is still at early stage.

Thanks

jcnelson commented 2 years ago

One opportunity that might be a very appropriate get together time, is maybe around Thursday 1pm EST Gov Lab Working Group call

I think we'd want to get their permission first, since they have a pretty full agenda as-is. This one filled the hour, for example. I kinda see that meeting as meant to capture issues related to the governance CAB more than the general SIP process.

What if we had a SIPs call right after it? As in, every other Thursday at 2pm-3pm EST? I can host it.

diwakergupta commented 2 years ago

@GinaAbrams this feedback from @kantai in a recent forum thread is relevant to your proposal:

This forum thread is hard to follow, and it’s hard to figure what is specifically being proposed. In responding to various comments, there seem to be changes suggested, and it ends up not being clear exactly what the final design would be. Some of that may just be because a forum thread isn’t a great tool for these kinds of discussions. I prefer github discussion posts for this reason: you can create threads within the thread.

Thoughts?