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

transfer of maintainership #103

Open
christian-rauch opened this issue Aug 19, 2024 · 2 comments
Open

transfer of maintainership #103

christian-rauch opened this issue Aug 19, 2024 · 2 comments

Comments

@christian-rauch
Copy link
Collaborator

@rjanvier I would like to pass on the maintainership of the org.cloudcompare.CloudCompare flatpak to you. I am not using CloudCompare that much anymore and you are the one most active in the flatpak repo anyway.

If you are fine with this, I would essentially unsubscribe from this repo and let you handle "everything". I believe you already have the same access rights as me, so you should be able to manage PRs and issues as I do.

Please let me know if this is ok with you.

@rjanvier
Copy link
Collaborator

rjanvier commented Sep 1, 2024

Hi @christian-rauch, it's ok on my side if the current situation turned to be a burden for you, but feel free to continue if you want !
Thank you for kickstarting this package and for all the time and effort you’ve put in maintaining it over the years (especially during the two years I was away from CC).

@christian-rauch
Copy link
Collaborator Author

Yes, it kind of became a burden since the build process failed quite often from automatic dependency updates and I had to spend more time on this than I was initially willing to. Essentially, you are fixing these issues anyway and managing new versions.

@nedrichards @bilelmoussaoui Is there something that needs to be done to turn over the maintainership of a flatpak to someone else?

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

2 participants