Difference between revisions of "School Network/Open Build Service/Policy"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{Draft}} | {{Draft}} | ||
| − | This Policy is based on the [[Activity Library]] [[Activity_Library/Editors/Policy|one]], assuming that the Sugar [[Activity Library]] will provide software hosted on the Open Build System. | + | This Policy is based on the [[Activity Library]] [[Activity_Library/Editors/Policy|one]], assuming that the Sugar [[Activity Library]] will provide software hosted on the Open Build System, after being accepted by [[Activity Library/Editors|Activity Library Editors]]. |
=== Requirements === | === Requirements === | ||
Revision as of 07:43, 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, after being accepted by Activity Library Editors.
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.