Revisions have to be manually approved until this change is in production which should be next week.
We added support for Microsoft Edge (https://github.com/JabRef/jabref/pull/7056). Since then, we get “interface reference ‘etc-opt-edge-native-messaging-jabref’ not allowed.”. Thus, we require a human review. @jdstrand are you the right one to ask?
+1 from me for jabref to be granted write access to /etc/opt/edge/native-messaging-hosts/org.jabref.jabref.json via the etc-opt-edge-native-messaging-jabref system-files instance as per https://github.com/JabRef/jabref/pull/7056/files#diff-56759910381a014fecfd7556dd72ddd68c747d922a5b7df2044b9ce7c552f5f5 - this is in line with the previous system-files instance in this thread and the publisher has already been vetted.
Can other @reviewers please vote?
+1 for the reasons outlined with continuing to manually connect.
+2 votes for, 0 votes against, granting use of system-files with write access to /etc/opt/edge/native-messaging-hosts/org.jabref.jabref.json with the interface reference of etc-opt-edge-native-messaging-jabref.
Still, It is my understanding that this grant also requires a review-tools update (https://git.launchpad.net/review-tools/tree/reviewtools/overrides.py#n835) since re-running the review-tools on the store after granting the declaration failed with:
interface reference ‘etc-opt-edge-native-messaging-jabref’ not allowed
In the meantime, we should be able to manually approve this. I will wait for @alexmurray ack to manually approve it meanwhile preparing the review-tools merge proposal.