AppReviewBoard

Differences between revisions 9 and 13 (spanning 4 versions)
⇤ ← Revision 9 as of 2011-10-30 13:43:06 →
Size: 1982
Editor: 71
Comment:
← Revision 13 as of 2012-07-20 23:55:47 → ⇥
Size: 2293
Editor: static-50-53-5-218
Comment:
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
  * Review proposals
Line 29: Line 28:
== Board members guides == == Guides for board members and contributing reviewers ==
 * [[AppReviewBoard/Charter|Board charter]]
 * [[AppReviewBoard/Responsibilities|Member responsibilities]]
 * [[AppReviewBoard/Restaffing|Recruiting new members]]
Line 31: Line 33:
 * [[AppReviewBoard/Responsibilities|Member responsibilities]]
Line 33: Line 34:
 * [[AppReviewBoard/Review/Responses|Common responses to submissions]]


== Guides for app developers ==
 * [[AppReviewBoard/Submissions|How to submit an app]]
 * [[AppReviewBoard/Review/Guidelines|Guidelines for app submissions]]
Line 37: Line 45:

== Process ==

 * PostReleaseApps

The Ubuntu Application Review Board is responsible for reviewing and approving proposals for lightweight applications to be distributed in Ubuntu.

The Application Review Board operates on the following basis:

  • The Board meets at least every two weeks, on IRC. See the Agenda for more details.

  • You can submit an application for review through developer.ubuntu.com.

  • The Board can be reached at app-review-board@lists.ubuntu.com. This list is publicly archived; if you wish to raise confidential issues, please mail the members of the Board directly.

  • Board meetings are open to all interested parties, but only Board members vote on applications.
  • Board members vote +1, -1, or 0 (abstain). Three or more +1 votes mean the application is approved, three or more -1 votes mean the application is rejected.

  • Minutes of the meeting will be published immediately after the meeting.

Agenda

The agenda for the upcoming meeting is kept at AppReviewBoard/Agenda.

Meeting Chair Duties

  • Review Agenda for this meeting.

  • Facilitate meeting
    • Send a reminder email 1 day before the meeting
    • Round up people needed for the meeting as necessary

    • Drive MootBot

    • Review actions from last meeting
    • Follow Agenda

  • Write TeamReports for the meeting.

  • Update Agenda for next meeting.

Guides for board members and contributing reviewers

Guides for app developers

Members

AppReviewBoard (last edited 2012-07-20 23:55:47 by static-50-53-5-218)