-
Notifications
You must be signed in to change notification settings - Fork 676
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
Transition Clementine Snap #6801
Comments
A PR including a Github action for publishing it automatically would be the first step towards this. |
You mean like this one: #5870 I'd be happy to open another but I want to get some input on the level of interest before I do it again. |
Yes, but we really need to have automated testing and deployment for it otherwise it will inevitably break in the future. |
The snapcraf.yaml is already in your repo as @jonaski assisted in updating it some time ago. This is meant to transition the snap to your team so that you can control it. |
Owning it, for us, requires automating it. I don't have the time or knowledge to do that right now, sorry. |
Okay - I'll find another route. Thanks anyway. |
I've created a PR to add a Github action to build and publish the snap, let me know if you have any questions. #6805 |
I've been maintaining (with the much welcomed assistance of others) the Clementine snap for some time now. It's been received quite well (almost 11k downloads worldwide).
It's easy enough to make the transition and I'd love to discuss with the Clementine project. Here's a link to my repo.
Here's a link to the snap in the Snap-store.
Let me know if you'd like to proceed.
The text was updated successfully, but these errors were encountered: