What pre-upload review are you talking about? I read through the steps, and I don't see anything other than the web form to generate an AppArmor policy, which seems completely automated.
EDIT: You're probably talking about the "APPLYING FOR ACCESS" section:
To ensure that we are giving upload access only to the original
author or a proper representative of the upstream project, we
will require that person to request upload access for their
application. The author or representative must first create an
account and user profile in the MyApps portal as it currently
exists.
Once their profile is created, they will need to be able to
request upload access for a package, providing details about
their association with the upstream project. If the submitter is
not the owner or representative of the project, they will be
required to provide a URL to a webpage, blog post or mailing list
archive showing that the owner or representative of the project
is endorsing their effort upload the application to the Ubuntu
Software Center.
This is an interesting requirement in our open-source world of forks, clones, and mods/patches. The concept of "ownership" in OSS is intentionally very loose, and ensuring only the owner can upload to the app center makes sense in a brand-focused business/product point of view, but seems kind of strange from a software developer point of view.
How could an app store like this work with users trusting developers' GPG keyrings, or something similar?
EDIT: You're probably talking about the "APPLYING FOR ACCESS" section:
This is an interesting requirement in our open-source world of forks, clones, and mods/patches. The concept of "ownership" in OSS is intentionally very loose, and ensuring only the owner can upload to the app center makes sense in a brand-focused business/product point of view, but seems kind of strange from a software developer point of view.How could an app store like this work with users trusting developers' GPG keyrings, or something similar?