# Implementing \`simplify-governance\` **URL:** \ **Category:** Governance\ **Created:** [October 14, 2020, 5:24pm UTC](https://forum.grin.mw/t/implementing-simplify-governance/7897 "2020-10-14T17:24:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![lehnberg](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/lehnberg/32/159_2.png) [@lehnberg](https://forum.grin.mw/u/lehnberg)\ **Post date:** [October 14, 2020, 5:24pm UTC](https://forum.grin.mw/t/implementing-simplify-governance/7897/1 "2020-10-14T17:24:57Z")
Now that the [`simplify-governance` RFC](https://github.com/mimblewimble/grin-rfcs/blob/master/text/0016-simplify-governance.md) has been accepted, I’m putting together a check list of steps to take to implement the changes. What are the necessary steps to: 1. Make clear there is only the council now, no core team, and that all other teams are self-organizing; 2. Make clear that the forum, keybase, repos, website, etc that we are not speaking on behalf of “wider Grin” and instead are centred around the **MW/Grin** (Rust) implementation. Anything we need to do on keybase? Anything on the forum we should do? Should we create a specific “Grin++” forum category perhaps? On RFCs, I was thinking of making sure RFC0002 is deprecated and clearly marked as replaced by this new RFC. On [grin.mw](https://grin.mw), what should we do? I was thinking of: - Mention on the front page somehow that the website specifically relates to the rust implementation. - Remove the core team from [/governance](https://grin.mw/governance) and put a smaller text based mention of the technocratic council, without mentioning members. Maybe also link to the new RFC and some text about how everyone is supposed to self organise. - Update [/funding](https://grin.mw/funding) to make it explicit that donations go to the benefit of the rust implementation, but that we may consider funding other projects as well as per the fund spending guidelines RFC. - Do we need to do anything on [/download](https://grin.mw/download)? Should we make a clearer distinction between MW/Grin and Grin++ downloads? - Anything else we need to do on website? Anything else we need to do anywhere else for that matter? Please share your thoughts. (cc: @paouky) ---
**Author:** ![Paouky](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/paouky/32/513_2.png) [@Paouky](https://forum.grin.mw/u/Paouky)\ **Post date:** [October 14, 2020, 9:38pm UTC](https://forum.grin.mw/t/implementing-simplify-governance/7897/3 "2020-10-14T21:38:04Z")
I’d say we should completely remove the _Governance_ page from [grin.mw](https://grin.mw/) (it looks cluttered anyway) and instead add a short description of the technocratic council to the _Funding_ page, in addition to what you mentioned should be added there. Also, how about we give Grin++ more attention on the _Download_ page? Considering it’s an entire implementation of the protocol and wallet, and is very widely used, it certainly deserves it. - Add a title (between the two existing ones) named “Other Implementations”, or something along those lines, which displays Grin++ in a more focused and attention grabbing manner. - “Community Projects” title can then be changed to just “Wallets”, which is more fitting of the spirit that every grin related project should be equal in essence, including the rust implementations, so no need to name a project as “community” stuff. Although a note could say that these are projects outside of the rust implementation jurisdiction. > [@lehnberg](#): > > Anything we need to do on keybase? > > Anything on the forum we should do? Should we create a specific “Grin++” forum category perhaps? I think the current state is fine in regards to those, no need for changes. ---
**Author:** ![lehnberg](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/lehnberg/32/159_2.png) [@lehnberg](https://forum.grin.mw/u/lehnberg)\ **Post date:** [October 19, 2020, 1:15pm UTC](https://forum.grin.mw/t/implementing-simplify-governance/7897/4 "2020-10-19T13:15:58Z")
> > I’ve let the download page be as is for now.