Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "Used by" section to Readme/doc #15

Closed
rugk opened this issue Aug 25, 2021 · 6 comments
Closed

Add "Used by" section to Readme/doc #15

rugk opened this issue Aug 25, 2021 · 6 comments

Comments

@rugk
Copy link

rugk commented Aug 25, 2021

I have heard that the Chromium flatpak and/or things like VSCode flatpaks want to or use this library which looks awesome (without knowing the details), given it solves a fundamental problem we had with Chromium applications in flatpak.

Anyway, I miss a short list somewhere (in the Readme it is fine enough, or on a new page in the wiki e.g.), where a list of "users" of this here is presented. Like "Used by: This flatpak, and this flatpak and that one"… probably just with proper bullet points/formatting…
This is both good "advertisement"/reference and useful for users to know that proper sandboxing is in place in these apps (as far as I understood the feature), so that no sandboxes need to be disabled inside of the flatpak.

@Erick555
Copy link
Contributor

Erick555 commented Aug 25, 2021

There are many dozens of flatpaks that use this so it would be hard to list them all. Generally every chromium based flatpak should use this and if it doesn't then it's a bug (not missing feature) that may be reported in relevant repo. Therefore listing somewhere flatpaks which don't use zypak may be easier and make more sense than the other way around.

@rugk
Copy link
Author

rugk commented Aug 25, 2021

Welll… maybe the most relevant big ones would be good.

Generally every chromium based flatpak should use this and if it doesn't then it's a bug (not missing feature) that may be reported in relevant repo.

Well… in any case I also think it's very useful to use this, though integration may not be always easy.
As you can see com.visualstudio.code e.g. already works on adding it and as for another VSCode-fork (VsCodium) I've opened an issue here: flathub/com.vscodium.codium#55

@refi64
Copy link
Owner

refi64 commented Aug 26, 2021

Hmm I'm not sure how entirely useful this would be, that being said it might also inspire a bit more confidence in using what appears to be a largely random repository to run your applications 😅

@rugk
Copy link
Author

rugk commented Aug 26, 2021

Indeed, this was my point. Without such an information, I just don't see whether this is a de-facto "industry standard" for Chromium-based flatpaks or whether it is jiust a proof-of-concept side project. This is hard to judge and such a small list would indeed increase trust and foster further adoption…

@Erick555
Copy link
Contributor

Erick555 commented Sep 4, 2021

Hmm I'm not sure how entirely useful this would be, that being said it might also inspire a bit more confidence in using what appears to be a largely random repository to run your applications

I wonder if it's possible to move this repo under flatpak umbrella on github? That would increase confidence for the project even more.

@refi64 refi64 closed this as completed in 55a60d1 Apr 18, 2022
@rugk
Copy link
Author

rugk commented Jul 31, 2023

BTW seeing your solution, I'd argue even more trust can really be gained by linking and listing the applications that actually use it (and the link proves it). Because everyone can say the majority of the apps uses it, you get my point, don't you hehe? 🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants