autonomousorganization
/
ao-manual
2
0
Fork 0
Code Issues Pull Requests Releases Activity
User manual for the AO. The same text is intended to be displayed in both the command line (ao-cli) and the web browser (ao-svelte or ao-3).
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1 Commit
1 Branch
0 Tags
389 KiB
 
Branch: main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
ao-manual/14_philosophy/index.md

1.0 KiB
Raw Permalink Blame History

title
Philosophy

The AO, ultimately, is a collection of principles about how to develop sofware communally and how to talk about cooperation.

These principles are meant to be modified by the community that uses them, so please take these ideas as evolving and in-discussion. Please propose or make changes to this manual.

Dissensus-driven development means that the AO is ultimately a conversation between the AO developers and AO users / user community. The AO ought to be designed with ongoing conversation amongst everybody who will come to the table and join the design process. The goal is to integrate the design process with the community's goals and the individual self-expression of users, by continuing the conversation. Consensus-driven development is good, but dissensus-driven development goes beyond that to include negotation across and through differences and conflict in the design process. By continuing the conversation, we can all gradually agree more about how to organize the AO to meet the needs of an ever-boader audience.