-
name: dodalu
-
description: Dodalu is a desktop kanban app. The user opens any project folder on the machine. The app stores the board and card Markdown in that folder, and an MCP helper is launched by host editors (Cursor, VS Code, and others) against the same folder.
-
snapcraft: PRIVATE
-
upstream: PRIVATE
-
upstream-relation: I am the upstream author and the publisher (Pross Co). Product site: https://dodalu.com
-
supported-category: IDEs
-
reasoning: The user chooses an arbitrary project directory. That path is not known at build time and is often outside $HOME (other disks, /opt, shared project trees, a path typed in or passed by an editor). The app and its MCP helper must keep read/write access to that whole tree, including files the app creates later (dodalu.json and docs/dodalu/cards/). The home interface only covers the home directory. removable-media only covers /media and /mnt. personal-files is for named paths, not a directory the user picks at runtime. A portal file dialog does not give the MCP process, which the host editor starts later with a path argument, durable access to the tree. Editors are reviewed under IDEs for this same reason (arbitrary project folders).
-
I understand that strict confinement is generally preferred over classic.
-
I’ve tried the existing interfaces to make the snap work under strict confinement.
Not a store @reviewer, however, the given reasoning of this application falls under the following unsupported category of Reviewing classic confinement snaps - Snap documentation:
Unsupported
- access to arbitrary files on the system due to developer/user inertia (home and removable-media is almost always sufficient, though personal-files and system-files may be used under certain circumstances)
Thanks. I agree this does not fit a supported classic category. The normal case is a project under $HOME, or on a drive under /media or /mnt, and the home and removable-media interfaces cover that. I withdraw the classic request and will publish dodalu as a strict snap with those interfaces.
2 Likes
Hello @rosswright ![]()
I will mark the request as closed, if you need further assistance with the other interfaces, feel free to ping us!
Thank you @Lin-Buo-Ren for the insights and support ![]()
1 Like