Enable users to skip package upload on app registration

[Stuart Metcalfe]

On the form to register a new app, we currently block the user from completing the form until they've uploaded a valid package. I think we should add a checkbox by this field which says something like "[ ] I'll do this later" to enable users who aren't familiar with packaging to easily register their app and then go and spend some time preparing the package. The rationale for this is that a user would seem to be more invested in the process and more likely to find out how to create a package if they've already registered their app and just need to upload the package to complete the process, rather than having to learn how to package *before* they can start the process.

This is only a suggestion. It's probably worth discuss with UX/design before we code this.

QA Notes:
1) Create a new app, but leave the package upload field blank and click 'Next' - validation should prompt you to upload the file (note, the field help indicates to you that you can alternatively check the checkbox)
2) Check the checkbox and click 'Next' again - you should be moved to the next stage (displaying your app),
3) Continue through until you see 'Submit for review' and click it - you'll be taken back to the 'about your app' form with the validation again indicating that you need to upload a package.

[Michael Nelson (michael.nelson)]

Hi Stuart!

I just landed a branch earlier today which adds config option to switch off all package validation. If you like, I can extend that config option so that it also makes the package upload itself optional? Let me know what you would prefer.

[Michael Nelson (michael.nelson)]

The related bug is bug 757587

[Stuart Metcalfe (stuartmetcalfe)]

I think the validation we have is fine - It's a basic sanity check to avoid people uploading stupid stuff and is probably a good idea on production. The point of my suggestion is to make it an explicit step for the user to say "I want to register the app but I need to do a bit of work before the package will be ready so I'll do that part later". I guess the field could be optional for the registration form but we should explicitly state that we won't be able to moderate or publish their app *until* they've uploaded the package. I don't see it as simply making the field optional because it is *required* - just not necessarily at the same time as the rest of the form. I assume there will also need to be associated work around indicating in the web UI to the user that their registration is incomplete pending the upload and providing a simple way to upload the file plus a link to appropriate instructions.

This is definitely something we should discuss with UX/design before implementing, even if we prototype something and ask them for review.

[Anthony Lenton (elachuni)]

Ivanka comments (slightly abridged version):
"""
    ivanka-train: I think the recommendation is a good one
    ivanka-train: I'll do this later check box is better
    ivanka-train: they need to acknowledge that they are missing something important out
"""