Classic Confinement Request for `processing`

store-requests classic-confinement
1

  • name: processing

  • description: Processing is a Java-based IDE for creative coding. Since 2001, Processing has promoted software literacy within the visual arts and visual literacy within technology. There are tens of thousands of students, artists, designers, researchers, and hobbyists who use Processing for learning and prototyping.

  • snapcraft: https://github.com/processing/processing4/blob/b8c0857faaaa987bd5cbfc74c0d99f36a966aad5/app/build.gradle.kts#L243-L283

  • upstream: https://github.com/processing/processing4

  • upstream-relation: Processing is published maintained by the Processing Foundation.

  • supported-category: IDE

  • reasoning: IDEs are a supported case for classic confinement.

    Processing users expect to:

    • Access arbitrary files anywhere on the system
    • Use third-party Java libraries
    • Interact with external hardware (e.g., via serial or MIDI)
    • Run shell commands or launch system executables
    • Integrate with industry-standard tools like Gradle and the system JDK
    • …

Raphaël de Courville

Processing Community Lead at Processing Foundation

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.

cc @stefterv @review-team

2

This request has been added to the queue for review by the @reviewers team.

3

As an IDE, processing fits in a supported category and has an understood requirement for classic confinement as per Process for reviewing classic confinement snaps.

But the publisher is not vetted, I will start the publisher vetting process (#approve)

1 Like
4

Thanks for the update.

@stefterv and I are maintainers of the Processing project. We’re happy to commit the token to https://github.com/processing/processing4 once it’s available.