blaede.family is one of the many independent Mastodon servers you can use to participate in the fediverse.
Private Mastodon server for members of the Blaede family.

Administered by:

Server stats:

5
active users

Cassidy James :eos: :gg: :fh:

I’ve been thinking through a lot of the feedback on (and things I've learned about peoples' perception of) @flathub's MetaInfo quality guidelines. I think I'd like to iterate a bit on how we present/talk about them; it could be helpful to make them more "branded" in a way to help make it more clear that they're really more of an opinionated, almost editorial thing.

I'm still brainstorming, but rather than inconsistently using "quality guidelines," "quality checks," and "high quality app data," I think I'd like to align on something more specific—plus some sort of consistent iconography. Even consistently using "Flathub Quality Guidelines" and e.g. a ★ icon would be an improvement, but I think people are still tripped up by "guidelines" and it still doesn't convey that these are criteria to be featured as an app of the day or in the weekly banner rotation.

I'm thinking something along the lines of "Exemplar" but that sounds maybe a bit *too* fancy/out there. Paired with a laurels icon, though… it could work. 🤔

Any thoughts?

For context, these are the guidelines: docs.flathub.org/docs/for-app-

Apps that meet them make Flathub look better and are also eligible to be featured in the big weekly rotating banner and as the "app of the day" on the flathub.org home page (among a few other things).

docs.flathub.orgQuality guidelines | Flathub DocumentationPlease open an issue using the Quality Guidelines template for support

@cassidy It seems like there is a list of requirements to meet a certain standard and become featured. Do you think it would be a good idea to use more assertive/direct language like “featured requirements” or “app checklist” Sure they may be optional but it sounds like what you’re truly saying is something along the lines of: “hey these are the minimum standards we think you should meet to publish your app”. In which case it might be good to use stronger language?

@gianni you're right that these "guidelines" are a list of prerequisites for getting your app "featured". In a perfect world we'd love for all apps to meet them because that would give Flathub a more consistent feel (and give us more apps to pick from to feature), but an app can choose to ignore them and still come to Flathub as long as they meet the minimum requirements.

So it's hard to separate, "we would like you to do this" and "you must do this." Maybe we can be even more clear about that.

@gianni but yeah, maybe the premise should be more clear: Here's how to get featured. You must do these things, first.

@cassidy @flathub The issue I see is that many apps have the same icon/name they had for ages and both are major brand identifiers. I understand the guidelines in regards to those from a desingers perspective but I feel like there should be limits to how much you want to interfere as an app distribution platform and especially uneven treatment like exceptions just because the app is big (E.g. GIMP) seem like a bad idea to me too.