Difference between revisions of "Sugar on a Stick/Activity Criteria"

From Sugar Labs
Jump to navigation Jump to search
m
Line 11: Line 11:
 
'''Rationale:''' Since SoaS is a [http://spins.fedoraproject.org Fedora Spin], everything that ships on the default image must be a package in Fedora. This is an upstream requirement.
 
'''Rationale:''' Since SoaS is a [http://spins.fedoraproject.org Fedora Spin], everything that ships on the default image must be a package in Fedora. This is an upstream requirement.
  
'''Test:'''  
+
'''Test:''' The version desired for inclusion should be in the [https://admin.fedoraproject.org/pkgdb/ Fedora repository] for the current Fedora version under development (in this case, F14).
  
'''Instructions:'''
+
'''Instructions:''' See https://fedoraproject.org/wiki/PackageMaintainers for more information on how to make a package in Fedora.
  
 
=== Be hosted on ASLO ===
 
=== Be hosted on ASLO ===

Revision as of 08:54, 29 March 2010

This is a draft discussion. It does not reflect policy (yet) - it is our attempt to define a clear policy for inclusion for the 4th release of SoaS (October 2010, as per the Fedora Spin release cycle).

Introduction

This page is for gathering requirements for Activity inclusion on the default Sugar on a Stick image. These are the criteria we will be using to begin discussion on Activity inclusion in v.4.0, due for release at the end of October 2010.

Proposed requirements

Be installable via a package in the Fedora repositories

Rationale: Since SoaS is a Fedora Spin, everything that ships on the default image must be a package in Fedora. This is an upstream requirement.

Test: The version desired for inclusion should be in the Fedora repository for the current Fedora version under development (in this case, F14).

Instructions: See https://fedoraproject.org/wiki/PackageMaintainers for more information on how to make a package in Fedora.

Be hosted on ASLO

Be translated in Pootle

Have a usage frontpage

Have a development frontpage

Have a ticket queue

Have and pass a smoke test

Add your own idea here

Be sure to describe:

  • the rationale behind the requirement
  • how we can make sure that the requirement is met (what sort of testing needs to be done to verify this?)
  • links to instructions on how Activity authors and maintainers can fulfill the requirement, if possible.