Hello @policy-reviewers,
I would like to request Verified Publisher status for our Snap Store publisher account, Seneboy Ventures Inc. (username: aviatorarchive).
Snaps
* aviator-archive — snapcraft / aviator-archive
Published and installable now on latest/edge.
Company
Seneboy Ventures Inc. — seneboyventures<.ca>
App website
Aviator Archive — aviatorarchive<.com>
We publish Aviator Archive, a pilot logbook for professional and private pilots. It is offline-first and keeps no server-side copy of a user’s data: a pilot’s flights live on their own devices and sync directly between other devices over the local network. It is proprietary/commercial software (license: Proprietary), free to install, with licensing handled by our own backend. The software is largely unlocked for 100 hours of a pilot’s career, with a few paywalled features. This allows a pilot to have free access to this software tool at a time when they are still paying for their flight training. The app hits a paywall only when they are on their way to becoming a working commercial pilot. Once the app is purchased, the user owns the software, with no subscription for the remainder of their career. This is in stark contrast to nearly every other pilot logbook option currently available, which rely on subscription payments from their users.
My role:
Founder and Lead Developer
I am the developer of the application and the maintainer of its snap packaging and releases.
Group email
support@aviatorarchive<.com>
Reason for the request
I have been a linux user since 2017, and since then it has been my goal to bring world-class software to the linux platform. Professional pilots around the world are linux users without a first-class logbook solution.
We publish and maintain Aviator Archive in the Snap Store, and Linux is a first-class target for the desktop app rather than an afterthought — the snap is built strictly confined, with no classic-confinement request.
Our upstream source is private, so publisher vetting has to proceed via the Verified Accounts process rather than the usual token-in-repository route — per the snap publisher vetting policy: “When the upstream source code is private, the publisher is vetted through the Verified Accounts process.”
This is currently blocking an auto-connect request for avahi-observe and avahi-control:
@jslarraz has indicated the two avahi interfaces make sense for our use case, and would prefer the verification to complete before granting them. LAN peer discovery is the app’s primary feature, so without those connections a Linux user has to run `snap connect` by hand before their logbook will sync.
Seneboy Ventures Inc. is both the publisher and the upstream developer of this software. We maintain the application, the snap packaging and the releases.
Relationship with Canonical
We have not formally partnered with Canonical. Aviator Archive is a small independent commercial project and this is our first snap.
Happy to provide any further verification that we are the legitimate upstream publisher, through a non-public channel if that is easier.
Thanks,
Daniel — Seneboy Ventures Inc.