Classic Confinement Request for winIDEA

store-requests classic-confinement
1
  • name: winIDEA
  • description: TASKING winIDEA - IDE, Debug and Trace Tool.
  • snapcraft: /
  • upstream: PRIVATE
  • upstream-relation: the upstream developer and publisher of this snap
  • supported-category: Debug tools / IDEs
  • reasoning:
    • Access to the full filesystem (including device files, system files, project folders outside $HOME)
    • Access to the files in hidden directories inside $HOME
    • Execution of developer tools (Python)
    • Enabling available snap interfaces does not open access enough to cover the all use cases

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

2

WinIDEA fits in the supported category of IDEs and fits the use of classic (#approve). Given that the application is closed source, we will need you to complete this process to verify your account in order to make the changes live.

Thanks!

3

Hi @cav , we’ve submitted a request for a Verified Account and got one approval, but we seem to be having issues getting another reviewer to take a look at our request. Do you know who we could turn to for this review? Any help would be appreciated.

4

I have just tagged the store in the other post hopefully get a follow up soon. Apologies for the delay

1 Like
5

I tried to upload a new version using a classic confinement and failed with an explanation: Issues while processing snap:

- (NEEDS REVIEW) confinement ‘classic’ not allowed. If your snap needs classic confinement to function, please make a request for this snap to use classic by creating a new topic in the forum using the ‘classic-confinement’ category (classic-confinement - snapcraft.io) and detail the technical reasons why classic is required.

Can you approve the request for classic confinement please, since our account has a status of “Verified Account” (Request for Verified Account - TASKING)?

6

Hi @review-team @alexmurray @jdstrand, can anybody check regarding the classic-confinement completion? It’s taking so long and I have no idea where it got stuck. Thanks.

7

I’ve just pinged the @store team in the other thread to get it moving.

8

Apologies for the late response – we actioned the verification request last month, but this one slipped through since it was marked solved. Classic confinement has been enabled