[Blueprint community-q-upstream-myapps] MyApps submission experience and expectations for upstreams

[Michael Hall]

Blueprint changed by Michael Hall:

Whiteboard set to:
What do we need to improve in terms of documentation/workflow for
developers to submit their apps to MyApps?

There is some confusion in some areas of the submission process:

What to submit
How to submit web apps

Alot of developers already have packaging. How can we make it easier to get their apps into MyApps.
 -- their packaging is probably wrong for myapps though (eg not install into /opt)

If they already have a PPA and can submit the PPA on the first line we can shortcut all the other required fields.
 - still need images, video

Issues:
 - We are seeing "free" apps go to ARB that connect to proprietary web sites and need to be manually reshuffled back to Canonical Commercial team.
 - May be able to make the interface clearer in how to choose between ARB/commercial reviews (free? price? ads? paid service?)
 - Large uploads fail, we need to solve this problem

Desired experience:
 - generate pkgme json file based on data they enter into the website
 - when pkgme generates a package automake a PPA with it in it, owned by myapps (dev doesn't need to go through PPA creation process etc)
 - Two classes of developers: the ones who have already done packaging will be knowledgeable enough to create a PPA, Quickly developers will have a PPA created for them.

-- 
MyApps submission experience and expectations for upstreams
https://blueprints.launchpad.net/ubuntu/+spec/community-q-upstream-myapps