Establish a Formal Process for Adding/Removing DAO Committee Members This proposal has been ENACTED by a DAO Committee Member (0xbfa6d24e6a061e9aea3447163fdfe045177dd40e)

I really like this proposal. I have only a few comments/changes that I would like to suggest: 1. Committee member removal a) It looks like a "stubborn" Committee member could prevent their own removal. I would require the Committee **multisig** to add/remove a member of the Committee, with no power for other Committee members to do something in those 24 hours. b) I don't think the 24-hour security delay makes sense without the SAB veto power. c) I would keep the 24-hour security delay for the SAB to veto a change. In case they do; there might be clear evidence that this SAB member is acting against the committee's decision, and if this needs fixing, an on-chain Community vote can remove them from the SAB. 2. Committee member removal by the SAB a) I got a little confused by this. I would keep this simple: the same rules by which the SAB can do any other action (which are very strict -- they require full consensus) also apply for adding or removing a committee member. I agree that communicating the reasons and a retroactive confirmation should be expected from the SAB. b) See Annex I for details on Aragon votes and the "expedited execution" conditions. 3. Community removal Sounds good. My only note is that I would require the Committee **multisig** to propose adding/removing a member of the Committee to avoid "stubborn" members that might complicate the process. --- *How Aragon Votes work* The SAB Vote is configured for 100% of support (full consensus), 60% minimum approval, and a 24-hour voting period. * This means that: 5-of-5 can do immediate changes, and 3-of-5 can do 24-hour delayed changes, **if and only if** any of the other 2 members don't vote negatively. * Both the "Support % Threshold" and the "Minimum Approval %" conditions are required for the vote to be successful. Support is set to 100%, and Minimum Approval is set to 60%. The SAB token supply is 5. * Support is the relative percentage of tokens that are required to vote “Yes” for a proposal to be approved. For example, if “Support” is set to 50%, then more than 50% of the tokens used to vote on a proposal must vote “Yes” for it to pass. * Minimum Approval is the percentage of the total token supply that is required to vote “Yes” on a proposal before it can be approved. For example, if the “Minimum Approval” is set to 20%, then more than 20% of the token supply must vote “Yes” on a proposal for it to pass. * The "immediate" execution is a little bit of a hack on Aragon that only becomes available if there is no possible reversal of the vote. * If 3 of the 5 members voted YES, you already meet the Support and Minimum Approval conditions, but any of the other two members might show up and vote against the proposal! This would turn the "Support %" to only 75% (calculated as 3 YES out of 4 valid votes) but 100% is needed. Regardless of whether the "Minimum Approval %" condition is met, the vote won't pass. * Instead, if 5 of the 5 members vote YES, the Aragon Voting app allows for "speedy" enactment of the vote (all voters already showed up). It assumes that voters won't change their mind.

Establish a Formal Process for Adding/Removing DAO Committee Members This proposal is now in status: PASSED. Voting Results: * Yes 100% 6,654,561 VP (30 votes) * No 0% 0 VP (0 votes)