Looking for Maintainer
Currently, there are two maintainers for this project
- Original Authoer @riemers (not longer using Gitlab in his day job https://github.com/riemers/ansible-gitlab-runner/issues/332#issuecomment-2146733294, so there is little reason for his professional life to put a lot of effort in)
- Myself (soon, the same thing is true for me)
Because of this situation, it would be very much appreciated to get new maintainers who are willing to spend time on this project and bring it again back on track.
It is all on best effort, and I already appreciate the effort guenhter put in. He is now in the same boat too ;) so let’s see if some others want to chip in too.
Hi i would be happy to help out with maintaining the project if you're open to it. We're still using it on our side and I’d hate to see it go unmaintained (or less active maintained :D).
You have some experience in ansible on that part? as i cannot see much on you from github though. (might be private too)
In my opinion. I'm not an Ansible expert, but I've been maintaining our Ansible environment for almost three years now, which currently manages GitLab Runner VMs exclusively. As you can see from my GitHub history, I have contributed a bit to docker-ansible repo in terms of version updates. But I have also created here a PR about 2 years ago and what you cannot see is that i have also tested some PR here from guenhter and another colleague. :D
As i said i am not an expert, but I want to participate more and dive deeper into the subject.
Hi :)
I'd be open to assist as well. I've committed a few things here and there and I have a long-running branch at my company which does some self-signed TLS stuff for docker (which we had issues with in the base role). I am trying to tidy that up and submit this upstream.
LMK if that sounds like a plan.
@riemers / @guenhter first and foremost, thanks for the effort put into this repository. Certainly acted as a fantastic spring board to get going with installing and configuring the gitlab-runner across multiple VM's
I'm wondering if it would be beneficial to look to migrate this repository across the gitlab-community ? It at least makes sense to me that something empowering gitlab usage resides on gitlab and potentially under the wider gitlab-community umbrella? (checking initial thoughts before attempting to raise on gitlab)
@riemers / @guenhter first and foremost, thanks for the effort put into this repository. Certainly acted as a fantastic spring board to get going with installing and configuring the
gitlab-runneracross multiple VM'sI'm wondering if it would be beneficial to look to migrate this repository across the gitlab-community ? It at least makes sense to me that something empowering gitlab usage resides on gitlab and potentially under the wider gitlab-community umbrella? (checking initial thoughts before attempting to raise on gitlab)
I agree having gitlab-specific stuff on GitLab.com makes some sense, but it doesn't really look like to me that this space is meant to host random projects/repositories from the community, it really looks like it's dedicated to allow working on the GitLab code base, or on a very specific set of components. Or did I overlook some section containing things that would be similar to this repo?
Think you might be right there, gitlab-community might just be purely for community driven forks of upstream things (it empowers running CI without consuming the users CI minutes if they had forked things themselves)
Might still reach out to some folks at Gitlab to see if they have an idea of where this could go if it was moved to gitlab