Installation request for personal-files interface: ainfovac

store-requests privileged-interfaces
1

name: ainfovac

description: AinfoVac is a desktop ERP application for the technical and economic management of livestock and agricultural farms. It manages accounting, livestock records, crop records, reports, backups and Android device synchronisation.

snapcraft: https://github.com/kampos/ainfovac/blob/master/snapcraft.yaml

upstream: PRIVATE

upstream-relation: I am the original author, upstream developer, maintainer and official publisher of AinfoVac.

interfaces:

personal-files:

request-type: installation

reasoning: AinfoVac has historically stored its user data in $HOME/.ainfovac, before the Snap package existed.

This directory contains the application databases, configuration, reports, backups and livestock/farm data. Existing users need access to the same directory when migrating to the strictly confined Snap package.

The requested access is limited exclusively to:

dot-ainfovac:
  interface: personal-files
  write:
    - $HOME/.ainfovac

No access to other hidden files or directories is requested.

This request is for permission to upload and publish the snap using the personal-files interface. Manual connection of the interface is acceptable.

2

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

3

Hello @ainfogra,

This is a +1 from me for granting auto-connection for the specified personal-files interface with write access to the ~/.ainfovac path for the ainfovac snap. We highly appreciate that you are open to manual connection, but I do believe this request very clearly meets all requirements for auto-connection: clear ownership of the requested path, as well as the need for establishing backwards compatibility for existing users. What do other reviewers think?

If this request is approved by additional reviewers it will then require you to successfully complete the publisher verification process. For private snaps that information can be found here. Please feel free to begin the verification process early. Thank you!

4

+1 from me to grant write access to $HOME/.ainfovac using personal-files interface.

7

+2 votes for, 0 votes against granting personal-files auto-connection to the ainfovac snap. @ainfogra please proceed with submitting a Verified Publisher. Let us know here when it is complete and I will proceed with granting this request.

Thank you!

8

Hello @elisehdy,

Thank you for reviewing the request.

When I originally submitted this request, the upstream source code was private. Since then, I have published the complete source code and the Snap packaging files in the official public GitHub repository:

https://github.com/kampos/ainfovac

Relevant information:

I am the original author, upstream developer, maintainer and Snap Store publisher of AinfoVac.

The repository contains the application source code and the files used to build the snap, including snapcraft.yaml.

Since the upstream source code is now publicly available, could the publisher verification be completed through the standard GitHub publisher-vetting process, rather than through an institutional Verified Publisher application?

I am available to receive a verification token through the Snap Store Dashboard and commit it to a branch in the official upstream repository, or to complete any other verification procedure required.

Please let me know what the next step is so that the approved personal-files auto-connection request can be completed.

Thank you.