-
Notifications
You must be signed in to change notification settings - Fork 58
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 #218
Comments
Re: #221 @dooglus The intent was to express that a core principle of the CLAM project is, and should remain, decentralization. i.e. Design decisions which necessitate a centralized server to maintain throughput do not embody the principles of the project. Better an expensive network that anyone can join without permission on common hardware than a cheap network that is centralized. If we wanted a centralized solution we should have forked Redis or memcache - they are more efficient. Is there some qualifying or different language that you can suggest that might better encompass that ideal? If I can get some agreement on principles, I would like to add the resulting document to the website and close the issue. |
Closing this issue and posting the above language to the website. If there are additional suggested changes to the language of the above; it can be dealt with separately. |
Meta issues, such as governance, while not existing as a matter of technical consensus, do have the potential to negatively affect the network and software. We are, after all, developing ultimately for a wet-ware interface.
It might make sense to delineate very specific laws concerning what exactly this adventure means.
Making promises concerning priorities and core beliefs to users can only help to apply Occam's razor to any future debates - a CLAM network with fewer assumptions is more secure.
Thoughts? Additions? Deletions?
The CLAM Constitution
Equally important is to establish an efficient methodology to review and implement changes - similar to the Bitcoin BIP process.
The text was updated successfully, but these errors were encountered: