Software, even "open" community software, is structure, no matter how we try to get around that fact. With that structure comes control, distributed in varous degrees to the stakeholder, designer, developer, tester, implementor and end-user.

The challenge here is to manage that balance between control (no matter how soft) and freedom. The only way to do that is through open communication with everyone involved.

Oftentimes, community efforts also have the burden to carry with themselves various agenda by different members, and when these agenda conflict, there is the temptation to withdraw communication, assert control and/or abuse freedom. Every member of the community should be sensitive as to whether they are promoting or stopping open communication in their activities, keeping dialogue open between stakeholder, designer, developer, implementor, tester and end-user, as they balance control and freedom, and "harmonize" the individual agendas towards fulfilling the community vision.