779
edits
Changes
Sugar on a Stick/Activity Criteria (view source)
Revision as of 07:50, 29 March 2010
, 07:50, 29 March 2010Created page with '<big><big><big>'''''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 (…'
<big><big><big>'''''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 2011, as per the [http://spins.fedoraproject.org Fedora Spin] release cycle).''</big></big></big>
== Introduction ==
This page is for gathering
== Proposed requirements ==
=== Be installable via a package in the Fedora repositories ===
'''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:'''
'''Instructions:'''
=== 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.
== Introduction ==
This page is for gathering
== Proposed requirements ==
=== Be installable via a package in the Fedora repositories ===
'''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:'''
'''Instructions:'''
=== 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.