Verified Publisher Request for `gimp`

Hi there!

I’d like to request Verified Publisher status on behalf of the GIMP project.

For the past few weeks, we (Snapcrafters) have been working with two upstream GIMP developers on how they can take ownership of the snap in the upstream project.

On Github, you can see the original request and resulting Pull Request

  • A list of the snaps that you have, that should have a verified publisher associated with them:
    • gimp
  • The institution, foundation or company that you are a member of or work for:
    • This is official account for the GIMP project
  • Your role within that institution, foundation or company Release Engineer
    • I work for Canonical as VP Engineering, and serve as one of the Snapcrafters admins. I’m requesting this verified status on behalf of @brunvonlope and @jehan on Github, one of whom will comment here to +1.
  • The group email address that should be tied to the Verified Account::
    • Please use the address associated with the account: snap@gimp.org

Cheers, Jon

6 Likes

+1 (#voteFor) from me, great to see upstream taking this. This request meets the requirements as per Verified Accounts.

4 Likes

Hi!

We made an account in here and we were asked to comment to be verified. I’m not sure, do we have to fill the various fields as above? I guess this is the only field which can be updated:

Your role within that institution, foundation or company Release Engineer

I am Jehan, maintainer of the GIMP project.

The other person who will be behind this account right now is Bruno (we are sharing access), our main packager and CI warrior.

And I do hope that the GIMP Snap maintainers until now will continue to help us maintaining this package! :hugs:

one of whom will comment here to +1.

+1

4 Likes

May I also add to this request an ownership transfer from Snapcrafters → GIMP. They are already added as a collaborator.

1 Like

Hello! :wave: that’s fantastic - it’s a definite +1 from me :slight_smile:

2 Likes

Hello! +1 from me too, the snap has been transferred and the account has been set to “verified”.

1 Like

Thank you very much! :slightly_smiling_face:

@miloslu Hi. Indeed, can confirm on url_to_snapcraft_io/snaps that we are now the onwers of the snap, thank you and everyone involed! But on the public page url_to_snapcraft_io/gimp there are two separate entities being displayed “GIMP” developer and “GIMP team” publisher. On other pages like Kdenlive and Inkscape, for example, only the publisher is displayed.

So, we followed the procedure of “Verify onwership” button on https://snapcraft.io/gimp/listing by adding the DNS txt record on our server: https://github.com/gnome-infra/dns/pull/75. More than 24 hours passed but no success so far. We still see two entities and the “Verify onwership” button still is displayed.

By the way, we are not being able to attach screenshots and Discourse says we can only add up to two links :sweat_smile:

1 Like

This is now fixed. The issue was that the DNS record applied to the hostname but not with the www. subdomain. I’ve updated this so that will be taken into account.

Thanks for that, @steverydz

I think the other thing that @GIMP is referring to, is that in the header of the snap’s listing page, the “GIMP” team is repeated twice for them:

But not for others, it seems?

@Lukewh perhaps you know?

Yes, that seems strange. I’ll look into that.

Looking at this, the first item (GIMP) is the developer and the second (GIMP team) is the publisher, so we will show both if both are available which is the case for GIMP but not Inkscape

we will show both if both are available which is the case for GIMP but not Inkscape

@steverydz Could you be more clear about where this “Developer” info come from?

I don’t see anything on the app listing page (https://snapcraft.io/gimp/listing) nor in the legacy dashboard (https://dashboard.snapcraft.io/snaps/gimp/).

Knowing where it is, I will remove it since this makes gimp snap feel dubious, unlike all other snaps.

I’ve managed to remove the developer entry so only the publisher will show now. We have a list of verified developers within the site itself, but the GIMP team is also a verified publisher so in this case I removed the developer entry. This fix is live now. Apologies.

1 Like

Thank you very much :handshake:

Thank you @steverydz!

@steverydz Not sure if our GIMP server is doing some cron job that makes the DNS records disappear from time to time but the “Verify ownership” feature is behaving wreidly:

(Also, I noticed while the feature was working that it says “It is not guaranteed that this snap is trustful just because the site is verified”, something like that, which does not make much sense to me since we are a verified publisher and have the website domain in our hands)

The listing page checks the DNS record in real time so if it isn’t present when the page has loaded we can’t show the domain as verified.

In regards to the text, I agree it sends a mixed message. It is intended to cover the case of a publisher who isn’t necessarily verified but they have verified their domain, so we could definitely be smarter about it. I’ve made a ticket for us to look at this so should have a solution shortly.

Asked to GNOME Infra team: domains: add a TXT field for Snap package ownership verification. by Jehan · Pull Request #75 · gnome-infra/dns · GitHub

I’ve updated the tooltip so if a publisher is verified, and the domain is verified then it won’t show the second sentence. That will now only be shown when a non-verified publisher has a verified domain.

1 Like