Coalition Operating Procedures

The SchoolForge website is a product of the SchoolForge Coalition. Coalition membership is by groups whose efforts extend beyond this website, not by individuals. The website serves to provide individuals a starting point towards learning about educational efforts within FLOSS and an opportunity for non-technical/non-programmers users to become involved in projects that share FLOSS principles. Through these interactions, individuals are encouraged to learn about, apply, and become active participants in Coalition member efforts.

To be a Schoolforge member, a group must be furthering the advancement of free resources into the educational field in some way. That could be by providing educational software that runs on Linux, providing discussion for a for educators and techies on using free software and other resources in the schools, providing documentation on using such resources, providing support services for such resources, etc.

Member groups agree to post an agreed-upon logo and the text, "A member of the Schoolforge coalition" prominently on their website and promotional literature. They also agree to post a press release to Linux PR or the equivalent announcing their joining SchoolForge.

Member groups will post a list of links to the major coalition areas on their websites, in some non-obscure area. This could be on the front page, or on some linked page, or could be just a front page link to the coalition website.

Groups in the coalition would need to be active, defined as having their website/CVS/documents/whatever-their-primary-project-is
updated at least once every 6 months. Groups not meeting this requirement will be declared inactive members, with no vote in coalition management until they do begin updating things again. After a similar period as inactive members, groups would be removed from the coalition.


Each member group will designate one person to be its representative to the coalition. At least that one person (and any more who desire) from the group must subscribe to the coalition management mailing list and monitor it regularly. When questions about managing the coalition arise, these people would be expected to take part in the discussion of the question. In most cases agreement on questions will likely be reached casually and consensually, but there may be occasions when formal votes are called for to resolve issues. At some point these questions will be put to votes, with the designated person from each group having one vote. Majority of votes would determine the answer to each question. The designated person would be expected to keep his or her group informed of the questions and the discussions, but would be under no hard and fast rules about that.

The person responsible for calling for votes on the various questions will be one of the group representatives, selected for a period of one month from the list of groups. After one representative's period ends, the representative of the next group on the list will assume the responsibility.

Management of the coalition website itself will be the responsibility of one of the member groups, which might be its contribution to the coalition.

Each member group will be expected to join a coalition mailing list devoted to its primary purpose and subscribed to by similar groups. Again, at least one but potentially as many as would like to may subscribe from each group. These mailing lists would be the primary means of inter-group communication. They may be augmented by IRC channels, weblogs, etc., but the mailing list will be a minimum requirement.

Each group will be expected to consult with other coalition members before starting a new effort that might impact an already-existing effort. For example, if group X decided to set up a public weblog about using free software in teaching the sciences, it will first ask other coalition members if they already had anything like this. If so, the first priority ought to go to sharing resources with the existing effort. If not, other interested groups ought to be invited to help with the development and deployment of the new feature. Again, no hard and fast rules, but an expectation of courtesy.