School Network/Open Build Service/Policy: Difference between revisions

Line 1:

This Policy is based on the [[Activity Library]] [[Activity_Library/Editors/Policy|one]] assuming that [[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.

=== Requirements ===

The software that ~~conform following rules~~ is not permitted:

The software that is not permitted:

* Inappropriate (violent, sexual, subversive) content.

* Inappropriate (violent, sexual, subversive) content

* Inappropriate license~~, see~~ Oversight Board [[Oversight_Board/2009/Meeting_Log-2009-12-11#non-FOSS content|meeting notes]] for details.

* Inappropriate license

See these Oversight Board [[Oversight_Board/2009/Meeting_Log-2009-12-11#non-FOSS content|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.

* 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]] ~~has~~ a priority.

* Names inherited from the [[Activity Library]] have a priority.

=== Special cases ===

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

Cases that requires 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.

=== 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.

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 library editors and community feedback.

@@ Line 1: / Line 1: @@
 {{Draft}}
-This Policy is based on the [[Activity Library]] [[Activity_Library/Editors/Policy|one]] assuming that [[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.
 === Requirements ===
-The software that conform following rules is not permitted:
+The software that is not permitted:
-* Inappropriate (violent, sexual, subversive) content.
+* Inappropriate (violent, sexual, subversive) content
-* Inappropriate license, see Oversight Board [[Oversight_Board/2009/Meeting_Log-2009-12-11#non-FOSS content|meeting notes]] for details.
+* Inappropriate license
+See these Oversight Board [[Oversight_Board/2009/Meeting_Log-2009-12-11#non-FOSS content|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.
+* 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]] has a priority.
+* Names inherited from the [[Activity Library]] have a priority.
 === Special cases ===
-Cases that requires special treatment involving all concerned parts. The final decision will be made by Open Build System administration.
+Cases that requires 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.
 === 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.
+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 library editors and community feedback.