Great idea! Couple of suggestions. This declaration could be clearer by removing any risk of conflation of openness in software with openness in a community. I will distinguish the two here by using the terms libre software/design and transparent community, though the by-laws may use different terminology.
One point of difference, software is forkable, but a community, not so much. We do not want a community to which we belong to be “modified” in an opaque manner or for unannounced reasons, but we don’t care (and sometimes are happy) if a fork of our design/software is modified for whatever reason and depending on the license, whatever manner.
Another way to better understand what kind of community we want is to ask ourselves why we value openness/transparency so much. It may have been self-evident at the beginning, but it is useful for the general public and as a reminder for established members. I am surprised that there is no explanation of the value of open sourcing design and the value of a transparent community on the OSD site. So, let’s fix that and inform others of the benefits of libre design and a transparent community.
Why do we value openness so much? For me:
- fosters innovation
- allows solutions to be tailored to individual needs
- encourages collaboration (many eyeballs…), not competition
- encourages (but does not guarantee) equality among members
- provides accountability
- enables and encourages participation and collaboration
- forms the foundation for democratic process
Understanding the reasons behind our values ensures that our by-laws and actions truly are in line with our values.
May I suggest a catchy title for our By-laws:
Open source. Open community. Open mind.
I’ll leave “open mind” open for discussion.