I agree with Michael this is a great start. Also, am I correct that the governance guidelines, mission, and goals are not yet on the wiki itself?<br><br>Besides adding more detail about mission and goals, I think this would be good publish on the wiki sooner than later, to help Commotion better identify itself (both to 'insiders' and 'outsiders') as a project based on participation. Likewise, perhaps add a conspicuous link to the governance guidelines to the bug reporting form, in case a casual bug reporter would like to become more involved?<br>
<br>Presumably, these guidelines would also help establish the process one goes through in transitioning from 'outsider' to 'insider.'<br><br><div class="gmail_quote">On Mon, Nov 5, 2012 at 2:39 PM, Seamus Tuohy <span dir="ltr"><<a href="mailto:s2e@opentechinstitute.org" target="_blank">s2e@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello All,<br>
<br>
We have been working on the following draft of Commotion's Community<br>
Governance Guidelines. The first is a proposal for the overarching<br>
Commotion project guidelines. The second is a proposed individual<br>
project guideline for code submission and review. Now that we have a<br>
rough sketch of what we think we should include we would like to see<br>
what the active community wants added, removed, reworded, etc.<br>
<br>
<br>
<br>
Commotion Community Governance Guidelines<br>
<br>
* The Commotion project is an open source, free software toolkit. The<br>
community welcomes all contributions and conversations that help the<br>
project grow and improve in accordance with its mission.<br>
* Commotion’s Mission and Goals are guided by the active developers<br>
and community stakeholders who contribute to the project community.<br>
Active developers of Commotion projects will guide the development<br>
of their individual project.<br>
* The Commotion project team encourages communities to customize the<br>
software to better meet local needs. We request that all<br>
customizations be contributed or communicated back to the Commotion<br>
community so that improvements can be reused without undue<br>
duplication of effort.<br>
* Work on Commotion should do no harm to existing projects. Projects<br>
that implement new code that breaks the existing functionality of<br>
other Commotion projects should work with the community of the<br>
existing project in order to provide support for the existing<br>
functions.<br>
<br>
* New members may contribute to existing Commotion projects by<br>
collaborating with active developers. Each Commotion subproject will<br>
maintain an active version-controlled code repository. Guidelines<br>
for contribution will be managed by each project’s active<br>
developers, and will be posted on each project’s development page.<br>
<br>
<br>
Commotion Project Governance Guidelines<br>
<br>
To contribute to the (___________) project’s code repository you must<br>
post contributions to the development list for review. When the<br>
community has reviewed them you will be asked to submit a request to<br>
submit code so that the community can add your code to the project. At<br>
the point when repository administrators believe that you have a strong<br>
grasp of your contributed code’s effect on the rest of the code base,<br>
and that your intentions are to further the goals of the project with<br>
all of your contributions, you may be granted access to submit code<br>
directly to the code base without review. Malicious or damaging code<br>
that is submitted will cause those privileges to be revoked immediately.<br>
<br>
<br>
<br>
Thanks,<br>
Seamus 2e<br>
_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="http://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">http://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br>
</div><br>