-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Governance Process #343
Comments
As I mentioned in the call, some of this info (the stuff referring to rDAO process) will be available in the Contributors guide. |
sorry this is getting confusing when we mention rDAO and rGIV and GIVernance - are we talking about the same DAO or am I missing something here? I see this document as being a mix of contributor guide and covenant documentation |
my bad... rGIV is the token for the rDAO (Aragon DAO).... so they are one in the same in my mind. Ill try to keep my wording the same so that we are all on the same page. |
reminder that we're should mention both the GIVgarden and the rGIV/rDAO (from comms call) |
Okay let's have a first pass on this and anything that might be missing. Please some QA. |
I made some comments - thanks Mitch! |
great! I incorporated most of your feedback and created another section relating to off-chain decision making |
I think this is good - thanks for the updates Mitch! |
Ready to go live... just blocked by waiting on the GIVgarden to go live |
We need to add an explanation of our govenance process (and figure it out!) to both the docs and the forum.
The covenant already includes a lot of this information, but it's missing details on:
Here's shapeshift's for reference:
https://forum.shapeshift.com/t/fox-governance-process/55
Here's our covenant, for reference:
https://hackmd.io/fasEfiHgRKelVVxAUCya1A?view
@divine-comedian I'm thinking you might be the person for the job, but let's discuss in the comms call on Wed, I think this is also a governance task but important to get organized before we launch the GIVeconomy
The text was updated successfully, but these errors were encountered: