<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This is a good start Seamus.<br>
<br>
I think you should specify what the <b>Mission</b> and <b>Goals</b>
are so readers have a clear understanding of the project. If they
are included here, it could become easy to evaluate proposals and
decisions using the Mission and Goals.<br>
<br>
Best,<br>
<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/5/12 3:39 p.m., Seamus Tuohy
wrote:<br>
</div>
<blockquote cite="mid:50982405.7030001@opentechinstitute.org"
type="cite">
<pre wrap="">Hello All,
We have been working on the following draft of Commotion's Community
Governance Guidelines. The first is a proposal for the overarching
Commotion project guidelines. The second is a proposed individual
project guideline for code submission and review. Now that we have a
rough sketch of what we think we should include we would like to see
what the active community wants added, removed, reworded, etc.
Commotion Community Governance Guidelines
* The Commotion project is an open source, free software toolkit. The
community welcomes all contributions and conversations that help the
project grow and improve in accordance with its mission.
* Commotion’s Mission and Goals are guided by the active developers
and community stakeholders who contribute to the project community.
Active developers of Commotion projects will guide the development
of their individual project.
* The Commotion project team encourages communities to customize the
software to better meet local needs. We request that all
customizations be contributed or communicated back to the Commotion
community so that improvements can be reused without undue
duplication of effort.
* Work on Commotion should do no harm to existing projects. Projects
that implement new code that breaks the existing functionality of
other Commotion projects should work with the community of the
existing project in order to provide support for the existing
functions.
* New members may contribute to existing Commotion projects by
collaborating with active developers. Each Commotion subproject will
maintain an active version-controlled code repository. Guidelines
for contribution will be managed by each project’s active
developers, and will be posted on each project’s development page.
Commotion Project Governance Guidelines
To contribute to the (___________) project’s code repository you must
post contributions to the development list for review. When the
community has reviewed them you will be asked to submit a request to
submit code so that the community can add your code to the project. At
the point when repository administrators believe that you have a strong
grasp of your contributed code’s effect on the rest of the code base,
and that your intentions are to further the goals of the project with
all of your contributions, you may be granted access to submit code
directly to the code base without review. Malicious or damaging code
that is submitted will cause those privileges to be revoked immediately.
Thanks,
Seamus 2e
_______________________________________________
Commotion-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a>
<a class="moz-txt-link-freetext" href="http://lists.chambana.net/mailman/listinfo/commotion-dev">http://lists.chambana.net/mailman/listinfo/commotion-dev</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<b>Michael Gregor</b><br>
Strategy Consultant<br>
313.437.1244<br>
theworkdept.com<br>
<br>
<br>
<i>This email message and any attached files are confidential and
are intended solely for the use of the addressee(s) named above.
If you are not the intended recipient, any review, use,
dissemination, forwarding, printing, copying, or other
distribution of this email message and any attached files is
strictly prohibited.</i></div>
</body>
</html>