Submissions

Differences between revisions 3 and 5 (spanning 2 versions)
⇤ ← Revision 3 as of 2011-09-28 17:58:54 →
Size: 4747
Editor: 109
Comment:
← Revision 5 as of 2012-04-01 19:55:05 → ⇥
Size: 4548
Editor: static-50-53-5-218
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 1. Prepare Your App - package your application ready for assessment.
 2. Submit For Review - send your application to the board for review.
 3. Await Feedback - the Application Review Board will provide feedback and conclusions on the review.		  1. Prepare Your App - package your application.
 2. Request Review - send your application to the board for review.
 3. Respond to Feedback - answer questions or make changes the board requests.
 4. Review Vote - the board votes on your app.
 5. Publish - your app is approved and published.
Line 13: Line 15:
== What Apps Are Eligible == == What to Expect ==
Line 15: Line 17:
 * Only new applications that are not present in an existing official Ubuntu repository (such as main/universe) are eligible in this process (e.g a new version of an application in an existing official repository is not eligible).
 * The process only applies to a specific version of an application (e.g. !MyNewApplication 1.0 or !MyNewApplication 1.2).
 * No other software can depend on the application being submitted (e.g. development libraries are not eligible).
 * Only executable applications (and content that is part of them) are eligible, and not stand-alone content, documentation or media.
 * Applications must be Open Source and available under an OSI approved license.		 The App Review Board publishes lightweight open source applications. See the [[AppReviewBoard/Review/Guidelines|review guidelines]] for full details on the kinds of apps we're looking for.
Line 21: Line 19:
As part of this process, there are the following terms and conditions: When an application is approved as part of this process, Ubuntu developers may make changes or improvements to a package before publishing it.
Line 23: Line 21:
 * When an application is approved as part of this process, Ubuntu developers reserve the right to make changes or improvements to a package when it is uploaded to the archive.
 * Security bugs and problems are expected to be resolved by the application author, but the ARB and Ubuntu Developers reserve the right to change or remove a package if there are sufficient security concerns.		 You are expected to resolve any security bugs or problems with your app, but the ARB and Ubuntu Developers may change or remove a package if there are sufficient security concerns.
Line 36: Line 33:
 * You should test your application against the Application Review Board's checklist identified below:
  * The application is well packaged using the Debian packaging system
  * All correct dependencies are met
  * Application installs cleanly
  * Application be removed cleanly
  * Includes suitable Copyright and licensing content
  * Application integrates into the Applications menu
  * Application runs correctly
  * Major features operate as expected
  * Does not perform any malicious actions
  * Content is suitable under the terms of the Ubuntu Code Of Conduct
Line 50: Line 36:
=== Step 2: Submit For Review === === Step 2: Request Review ===
Line 52: Line 38:
You should now file your application for your application to be reviewed. To do this, follow these instructions: You should now submit your application for review to the [[https://myapps.developer.ubuntu.com/dev/|developer portal]]. You can follow along through the [[AppReviewBoard/Submissions/Request|step-by-step instructions]], but if you've submitted before, the most important things to remember are:
Line 54: Line 40:
 1. Go to [[https://bugs.launchpad.net/ubuntu-app-review-board/+filebug|this page]].
 2. In the ''Summary'' enter: `Application Review Request: <Your App> <Version>` (e.g. `Application Review Request: PyJunior 1.0`). Click the Next button.
 3. In the ''Further Information'' box, add the template below with all information filled in:		  * Select "Free" for the Price and choose an open source license. (If your app is paid or proprietary, it will go through a different review process for commercial apps.)
 * Don't upload any package files or code with your submission, just submit a simple text file named ''ppa-info.txt'' that includes links to your PPA and source code.
 * We need at least one PNG icon image and a screenshot with your submission.
Line 58: Line 44:
=== Step 3: Respond to Feedback ===
Line 59: Line 46:
{{{
Application Review For <application name> <version>		 When you have filed your application the Application Review Board will assess the application and provide feedback through the developer portal or by emailing you directly. The feedback may be simple questions for more information, or it may be requests for changes to the code or packaging to meet the ARB requirements. The reviewers will apply the following general checklist:
Line 62: Line 48:
== About You ==  * The application is well packaged using the Debian packaging system
 * All correct dependencies are met
 * Application installs cleanly
 * Application is removed cleanly
 * Includes suitable copyright and licensing content
 * Application integrates into the Dash and Launcher
 * Application runs correctly
 * Major features operate as expected
 * Does not perform any malicious actions
 * Content is suitable under the terms of the Ubuntu Code Of Conduct
Line 64: Line 59:
 * NAME:
 * EMAIL ADDRESS: 		For more details, see the [[AppReviewBoard/Review/Guidelines|review guidelines]].
Line 67: Line 61:
The Application: === Step 4: Review Vote ===
Line 69: Line 63:
 * APPLICATION NAME:
 * LICENSE:
 * PPA URL:
 * SUPPORT RESOURCE (URL to forum / mailing list etc)
 * KNOWN ISSUES:
  * Issue.
  * Issue.		 After you've made all requested changes, one of the reviewers will send a call for vote to the ARB members. If you get at least 3 positive votes, it will be approved for publishing.
Line 77: Line 65:
}}} === Step 5: Publish ===
Line 79: Line 67:
== Step 3: Await Feedback ==

When you have filed your application the Application Review Board will assess the application and provide feedback as comments in on the same page. When the majority of the Application Review Board have approved the application, it will be imported into the Ubuntu Software Center.

You should be sure to click the 'Subscribe' link in the right of the page to ensure that you get emailed with updates and feedback from the Application Review Board.		 Once your app is approved, it will be published in the Software Center. One of the reviewers will notify you when this is complete. At the moment, there is a bug in the developer portal so your app will continue to appear as "Pending QA" even after it is published.

Application Review Process

A key goal in the Ubuntu community is to deliver secure and reliable software to our users. As part of this goal we have developed a process designed for application authors in which you can request an application to be reviewed by our community Application Review Board. The board will review the application, and if it meets our quality expectations, the application will appear in the Ubuntu Software Center.

How It Works

The process works like this (each of these is explained in detail below):

  1. Prepare Your App - package your application.
  2. Request Review - send your application to the board for review.
  3. Respond to Feedback - answer questions or make changes the board requests.
  4. Review Vote - the board votes on your app.
  5. Publish - your app is approved and published.

What to Expect

The App Review Board publishes lightweight open source applications. See the review guidelines for full details on the kinds of apps we're looking for.

When an application is approved as part of this process, Ubuntu developers may make changes or improvements to a package before publishing it.

You are expected to resolve any security bugs or problems with your app, but the ARB and Ubuntu Developers may change or remove a package if there are sufficient security concerns.

How To Submit An App For Review

Step 1: Prepare Your App

In this stage you should package your application and upload it to your Personal Package Archive. See this page for help on how to create a package and this page for how to upload to a PPA. If your application is written with Quickly, run quickly tutorial for details of how to release to your PPA with a single command.

When packaging please follow these guidelines:

  • The application and its files should be packaged under /opt.

  • Make sure your package doesn't use root privileges (by sudo, gksu, pkexec, suid/sgid, etc.) or custom maintainer scripts (maintainer scripts that are automatically generated by debhelper and similar tools are fine).

At the end of this process you should have your application packaged and available in your PPA.

Step 2: Request Review

You should now submit your application for review to the developer portal. You can follow along through the step-by-step instructions, but if you've submitted before, the most important things to remember are:

  • Select "Free" for the Price and choose an open source license. (If your app is paid or proprietary, it will go through a different review process for commercial apps.)

  • Don't upload any package files or code with your submission, just submit a simple text file named ppa-info.txt that includes links to your PPA and source code.

  • We need at least one PNG icon image and a screenshot with your submission.

Step 3: Respond to Feedback

When you have filed your application the Application Review Board will assess the application and provide feedback through the developer portal or by emailing you directly. The feedback may be simple questions for more information, or it may be requests for changes to the code or packaging to meet the ARB requirements. The reviewers will apply the following general checklist:

  • The application is well packaged using the Debian packaging system
  • All correct dependencies are met
  • Application installs cleanly
  • Application is removed cleanly
  • Includes suitable copyright and licensing content
  • Application integrates into the Dash and Launcher
  • Application runs correctly
  • Major features operate as expected
  • Does not perform any malicious actions
  • Content is suitable under the terms of the Ubuntu Code Of Conduct

For more details, see the review guidelines.

Step 4: Review Vote

After you've made all requested changes, one of the reviewers will send a call for vote to the ARB members. If you get at least 3 positive votes, it will be approved for publishing.

Step 5: Publish

Once your app is approved, it will be published in the Software Center. One of the reviewers will notify you when this is complete. At the moment, there is a bug in the developer portal so your app will continue to appear as "Pending QA" even after it is published.

AppReviewBoard/Submissions (last edited 2012-04-02 21:18:10 by static-50-53-5-218)