Sugar on a Stick/Activity Criteria

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 (or get a package made) in Fedora. We may want to clean this up or make a Sugar-specific guide to packaging Activities in particular, or gather a team of volunteers who offer to do the packaging for Activity maintainers.

Be hosted on ASLO

Rationale: http://activities.sugarlabs.org is the Sugar Labs community's primary online mechanism for updating and installing Activities.

Test: Go to http://activities.sugarlabs.org and search for the Activity name. You should:

• be able to find the Activity
• be able to see that the Activity is properly categorized in one or more categories
• be able to see that the Activity's metadata (version number, "works with", etc.) is up to date
• be able to read an accurate and up to date summary of the Activity on its ASLO page
• be able to successfully download and install the Activity from ASLO's web interface

Instructions: I can't find clear step-by-step instructions on how to get one's Activity into ASLO - can anyone else help find (or create) them?

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.