Difference between revisions of "School Network/Open Build Service/Policy"

From Sugar Labs
Jump to navigation Jump to search
Line 21: Line 21:
 
=== Tools ===
 
=== Tools ===
  
−
Most, conforming to this Policy, checks for particular software will be made automatically by {{Code|sweets}} command while uploading sources to the Open Build Service. These checks will be reproduced on a server side.
+
Some, such checking software license, conforming to this Policy, checks for particular software will be made automatically while uploading sources to the Open Build Service. In other cases, e.g., inappropriate content, we rely on community feedback.

Revision as of 10:40, 29 October 2011

This Policy is based on the Activity Library one assuming that Activity Library will provide software hosted on the Open Build System.

Requirements

The software that conform following rules is not permitted:

  • Inappropriate (violent, sexual, subversive) content.
  • Inappropriate license, see Oversight Board meeting notes for details.

Top level project naming rules:

  • Project with names directly associated with particular software can be created only by this software upstream developers.
  • Names inherited from the Activity Library has a priority.

Special cases

Cases that requires special treatment involving all concerned parts. The final decision will be made by Open Build System administration.

  • Names confusion between top level projects.

Tools

Some, such checking software license, conforming to this Policy, checks for particular software will be made automatically while uploading sources to the Open Build Service. In other cases, e.g., inappropriate content, we rely on community feedback.

Retrieved from "https://wiki.sugarlabs.org/index.php?title=School_Network/Open_Build_Service/Policy&oldid=70504"