Difference between revisions of "School Network/Open Build Service/Policy"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
Software that is not permitted contains: | Software that is not permitted contains: | ||
− | * Inappropriate (violent, sexual, subversive) content, or | + | <!--* Inappropriate (violent, sexual, subversive) content, or |
− | * Inappropriate license | + | |
− | + | This topic might be too ambiguous (and too hard to write it in sentences) after having a synergy between Sugar and Zero Install (that is not only about software for education) communities. Since we don't have such thorough policy, e.g., for the SL Wiki (for Activity Library it is mostly obvious what kind of content should be hosted there), and since OBS software needs to go though ASLO editors, it would be better to avoid needles bureaucratic procedures and rely on people saneness. | |
+ | |||
+ | --> | ||
+ | * Inappropriate license, all licenses should conform Sugar Labs' [[Licensing]] policy. | ||
Top level project naming rules: | Top level project naming rules: |
Revision as of 06:40, 31 October 2011
NOTICE: This page is a draft in active flux... Please contribute to these contents and discuss issues on the discussion page. |
This Policy is based on the Activity Library one, assuming that the Sugar Activity Library will provide software hosted on the Open Build System.
Requirements
Software that is not permitted contains:
- Inappropriate license, all licenses should conform Sugar Labs' Licensing policy.
Top level project naming rules:
- Projects with names directly associated with a particular software line can be created only by the software upstream developers.
- Names inherited from the Activity Library have a priority.
Special cases
These cases require special treatment involving all concerned parties:
- Names confusion between top level projects.
The final decision will be made by the Open Build System administration team.
Audit
Some checks, such as checking software license & conforming to this Policy, will be made automatically while uploading sources to the Open Build Service. In other cases, e.g., inappropriate content, we rely on Activity Library Editors and community feedback.