RFC-106: Future of Forge versioning - Permissions

[nathanwaters]

Overly complicated solution that doesn’t address the problem or fix the current mess. You’re forcing unnecessary and infinite complexity onto developers.

Copying the structure from iOS/Android doesn’t make any sense in the context of the Atlassian Marketplace. iOS apps are obviously 1:1 approved and managed by an individual user. Atlassian apps are approved and managed by org admins.

Please think about how much complexity this will entail for developers who will need to check and handle EVERY single possible on/off permission scope within their apps.

Opt-out automatic updates is the correct solution:

@nathanwaters

I think the best solution is opt-out automatic updates, eg…

Minor versions: instantly auto-update.

Major versions:

1. Devs push a new major app version.
2. Admins are given X months of system notifications.
3. They can either one-click update the app or uninstall.
4. If no action is taken the app automatically updates.
5. Atlassian can auto/manual review the app just before step #4 happens.

Same for converting free>>paid apps but you simply use or extend the existing refund policy if the admin takes no action, and Y months later they decide don’t want to pay for it.

If you think through all possible ways to solve the problem I can’t think of any better:

• simple solution with very few moving parts or complexity.
• all installed marketplace apps will be at most X months out of date.
• the current mess of 90-99% of installs being old/broken will auto fix itself.
• moves complexity away from devs who shouldn’t need to handle this.
• avoids in-code handling of infinite optional permission scopes (Forge current plan ).
• gives admins ample opportunity to take action on their own terms.
• includes a final review step to prevent bad actors stuffing scope changes.