I submitted a package around three weeks ago, and so far it's status is still "Pending"
Summarising the IRC classroom (transcribed as the lesson unfolded hence the brevity and that it reflects the order of the lesson!):
- In future, just like paid for applications, free/libre apps will be submitted through the MyApps portal (see blueprint below)
- The ARB is a 4 community member group responsible to allow small standalone apps into a stable distro (i.e. has been released)
- Board offers assistance for packaging and ensures apps meets standard ubuntu packaging rules.
- Two apps have gone through the process - 'News' and 'Suspended Sentence' - both made available to Maverick (10.10)
- Confirmed that Launchpad will be dropped in favour of the MyApps portal.
- Ways to get free/libre apps into ubuntu - through debian and sync to ubuntu before feature freeze, via a backport or through the ARB
- Ways to get paid for apps into ubuntu - Canonical partner apps (case be case basis) or via Purchase Apps through Software Center
- If submitted via ARB - you are the maintainer and are responsible for submitting for every new release of Ubuntu. Hence the preference for packages from upstream since they are automatically sync'd.
- ARB accepted apps are added to
- If there is a critical bug or security issue in an ARB package a board member will attempt to fix on a best effort basis - then contact the maintainer. Where the maintainer is not responsive - app will be removed and an empty package is pushed.
- ARB members recognise the length review process. Looking to use
Arkoseto containerise apps - similar to Android app with a list of actions that an app is allowed to perform. Should allow faster review without having to do a full code-review (this is the key reason for the current length delay). It is also the reason cannot accept complex apps or apps written in certain languages
- Also looking to produce a debhelper script to automatically package a app to meet ARB rules.
- Long-term - submission via MyApps as tarball of source code with a build recipe. This will generate a Arkose or Apparmor profile etc. ARB process should be then reviewed in hours (rather than as now weeks) before being pushed to Software Center.
The Oneiric ARB blueprint was raised in May this year and is targeted for Oneiric.
The review tag-line is "We want to socialize how people can get their apps in Ubuntu, and we want to review how well the ARB is working.
- Which things work well?
- Which are the areas that need improvement?"
Some progress has been made in achieving the blue-print's goals:
- New app-review mailing list (email@example.com)
- checklist of steps for uploading apps to the live extras repository
- Progress towards talking towards stakeholders on how to simplify the process on merging and incorporating changes
- Preparing and article for publishing on Ubuntu Planet
- New beta web-page for developers to guide through the process of submitting (although currently for commercial developers)
As the notes in the blue-print indicate - Canonical's own developers need "motivating" to get the ARB process working. There is talk of recruiting someone to primarily to move the process forward.
So to answer the question - the ARB is working for Commercial developers (just), with plans for the ARB to be fully working within Oneiric timeframes.
You could however speculate, given the number of outstanding items in the blueprint - maybe 12.04 would be a more safer bet.
There are two "queues" ARB and "commercial/paid". For both the review pending stage takes the longest. This is where the submission is made into a package. If you submitted debian package source (the output of dpkg-buildpackage -S) then this stage will take a very short time. If you didn't follow instructions and submitted a binary deb the process takes MUCH longer as we have to deconstruct and subsequently reconstruct the .deb. If you submit a simple tarball, the packaging process is completely dependent on the complexity of the package.
The stages post review pending are quick. Once the app is packaged it goes to QA and once through QA (usually 24/36 hours max) then back to the developer to be listed.
I hope that helps...