Hello @policy-reviewers,
I’m applying for Star Developer status at the suggestion of @yomonokio in the classic confinement
review for my snap: Classic confinement request for repobeam
I’ll be upfront: I’m new here. I publish one snap, repobeam, a desktop Git client for Linux and
Windows, and my account (baha7) started publishing this month. I know Star Developer usually
recognises a longer track record, and I’m not asking you to overlook that.
What I can show is how the snap is maintained:
- 13 revisions so far, each built and published by a CI pipeline that releases the Snap, the
GitHub releases and the website from the same commit, then checks all three are live.
- Strict confinement done carefully:
ssh-keysand the other sensitive interfaces are declared but
not auto-connected, as reviewers asked, and the app detects this with snapctl is-connected and
walks the user through granting access instead of failing silently.
- Problems found in the field are fixed at the snap level, not just in the app. For example, Git’s
credential cache daemon outlived the app and kept snapd from refreshing for hours ("currently
running"), so the snap now starts through a small launcher that ends leftover processes after the
app exits, and the app tells users when a refresh is waiting.
- I read and answer store and review requests the same day.
I’m happy to share what I’ve learned about Electron and Git under strict confinement with others
here, and to keep contributing in the forum.
If the answer is “not yet”, I’d be grateful to know what you would want to see, and I’ll work
towards it.
Thank you,
Baha