-
Notifications
You must be signed in to change notification settings - Fork 10
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
Migrate this to nix-community? #69
Comments
Hey @JohnRTitor, thanks for the pointer. I'll looking into what's required for joining the org. Def interested in migrating, if the project is a fit. |
@gmodena @Mic92 thoughts |
Sure. Looks like a useful project. Just open an discussion topic there and we handle the onboarding. |
I had a look at nix-community, but as the sole developer of this project, I'm not looking to transfer ownership of the nix-flatpak repo right now. I have the time to maintain it and welcome bug reports, feature requests, PRs, and other contributions at the project's home. Also, there are some ideas I'm still exploring before I consider this project mature enough for incubation or upstreaming. If more people want to contribute (and do so), and if I were to become a bottleneck, I would certainly consider extending maintainership rights and sharing ownership. |
Hi! I was searching for a way to better manage flatpaks on NixOS and found this.
NixOS upstream does not have a module for declaratively installing flatpaks. So this project is very handy.
Useful project like this can be migrated to
nix-community
, while retaining full maintainership to your project. nix-community incubates these projects by providing them access to cache and other tools with more visibility.If you are interested, you can start a discussion here.
The text was updated successfully, but these errors were encountered: