Be more explicit about what the License text will be used for

[Anthony Lenton]

If a license text is entered during application submission, this will be displayed to the user during purchase, so that the license needs to be accepted before the app can be purchased. We should make this explicit to the developer by either:
 - Initially providing just the current License type dropdown and a checkbox saying "I want users to agree a license during the purchase", and if this checkbox is selected then display the whole License text area, or
 - Keep the current behaviour but add a bit of copy below the License text area saying "If provided, this license text will need to be accepted by the user during the purchase".

[Michael Nelson (michael.nelson)]

With both options mentioned in the description, is it not possible that we'll require people to enter their license (especially if it's commercial), even though they *don't* want users to have to agree during the purchase process?

If this is the case, would a third option of:
 - Provide an extra check "I want users to agree to this license during purchase" which is checked by default
and if this is not checked, either:

1) the license won't appear in the API (so that the purchase behaviour doesn't require agreement), or
2) we additionally include the include_license_during_purchase attribute in the api so the client can be updated to use it.

[Michael Nelson (michael.nelson)]

Just in answer to my own pre-imp questions above, spoke with achuni and no, there's no use-case where we'd require the license text to be entered in the UI when the dev doesn't want users to have to accept it (we can grab it from the package/ensure it is included in the package).