New 'Community App' badge for App Wishlist ?
-
App Wishlist topics have been marked as
Solvedwhen they are packaged for the official App Store.I was glancing through the category, and noticed that lots of items have been published as Community Apps, and wondered if a new badge/label
Community Appwould be helpful.No idea if this forum software allows the admins to create extra ones.
Just a thought.
No worries if not possible / does not find favour with Cloudron team. -
App Wishlist topics have been marked as
Solvedwhen they are packaged for the official App Store.I was glancing through the category, and noticed that lots of items have been published as Community Apps, and wondered if a new badge/label
Community Appwould be helpful.No idea if this forum software allows the admins to create extra ones.
Just a thought.
No worries if not possible / does not find favour with Cloudron team.Hello @timconsidine
No idea if this forum software allows the admins to create extra ones.
By default, no.
We could use the default tagging system to tag such topic with e.g.:
community appthat could be a good indicator. -
On this topic:
How do we mark „one-off“ packaging that is not regularly maintained (e.g. see the Tachyon package)?
And as discussed at various stages: How do we avoid this whole Yunohost mess of gazillion apps, most of them now working? Maybe require CI tooling, at least? Maybe a „code of conduct“ that packaging come with a certain responsibility?
Is the topic of grandfathering in packages into the official app store resolved? -
On this topic:
How do we mark „one-off“ packaging that is not regularly maintained (e.g. see the Tachyon package)?
And as discussed at various stages: How do we avoid this whole Yunohost mess of gazillion apps, most of them now working? Maybe require CI tooling, at least? Maybe a „code of conduct“ that packaging come with a certain responsibility?
Is the topic of grandfathering in packages into the official app store resolved?@necrevistonnezr good points
I think simplest approach is that adding to ca.cloudron.io should be accompanied by a commitment to maintain. Otherwise just post the link to CloudronVersions.json in the forum.
I’ve not promoted some app packages into ca.cloudron.io that I’m not going to maintain (e.g. Windmill).
My guess is that in practice 90% or more of apps on ca.cloudron.io will not make it into the AppStore, only happening when Cloudron team see a strategic gain from doing that. And that’s ok by me.
-
On this topic:
How do we mark „one-off“ packaging that is not regularly maintained (e.g. see the Tachyon package)?
And as discussed at various stages: How do we avoid this whole Yunohost mess of gazillion apps, most of them now working? Maybe require CI tooling, at least? Maybe a „code of conduct“ that packaging come with a certain responsibility?
Is the topic of grandfathering in packages into the official app store resolved?@necrevistonnezr my own approach at present is to mostly not use Community Apps yet.
If/ when I do so, I like to check e.g.
- When the user reg'd on this forum (as a proxy of how long they've been using Cloudron)
- The users "reputation" score on the forum
- If the user has an "App Dev" or other (e.g. Partner, Translator) badge on the forum
- How often the Community App gets updated (which I'd then compare to how often the upstream up gets updated)
Ideally, I'd like http://ca.cloudron.io/ to help surface this info in one place to inform my decision-making.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login