More Contributors / Developers / Maintainers needed!

[gdubicki]

Hi Everyone!

We have a few great ideas on how to move forward but I personally just don't have the time to implement them all.

I would love to get more people cooperating on this project, especially having more Core Developers/Maintainers that would move the big things forward, like v3 design/implementation but also Feature Developers, Documentation Contributors and everyone else what wants to improve this project is very welcome to join.

Please let me know if you are interested, what you would like to do and what you need from me to get you started. A chat or a call with an introduction? - we can do it. Better docs about something specific? - can be arranged. Make some code more readable? - I will do my best. :) More permissions to the repo/project? - sure, why not.

Let me know!

[jimisola]

@gdubicki How many are there that you believe are able and willing to cooperate now?

Would it be inappropriate to have a one-liner when gitlabform runs such as "The GitLabForm project is in need of contributors to keep up with GitLab changes and features. Please see: ".

Have GitLab ever shown an interest in the project?

[grzesuav]

hi @gdubicki , I believe local testing env would be nice, so an easy way to spin up gitlab instance locally (docker/docker-compose/shell ?) and config to run gitlabform loccaly against this instance. Is this something you have somewhere ?

[gdubicki]

hi @gdubicki , I believe local testing env would be nice, so an easy way to spin up gitlab instance locally (docker/docker-compose/shell ?) and config to run gitlabform loccaly against this instance. Is this something you have somewhere ?

Hi @grzesuav! We already do have docs and a script for that, please check out https://gitlabform.github.io/gitlabform/contrib/local_development/#running-acceptance-tests-using-gitlab-instance-in-docker.

[gdubicki]

I wonder how many people would cooperate on the project if it would be using the semi-standard python-gitlab under the hood?

Of course I am referring to the effort that has already started in #442.

cc @nejch

[nejch]

Definitely @gdubicki!

At the very least I would be happy to always work on any missing endpoints in python-gitlab, and potentially integrating them in here.

Then there's also GitLab's quirks that we are all probably working around in different ways, so solving things like https://github.com/gitlabform/gitlabform/issues?q=is%3Aissue+is%3Aopen+label%3A%22%F0%9F%A6%8Agitlab+issue%22 together is another option if it affects both projects.

[adam-moss]

We are in the process of adopting this as a replacement for terraform and using python-gitlab would certainly make it much easier for us to contribute (we already have to python-gitlab itself).

[grzesuav]

@gdubicki I know it might be a long shot, have you considered re-do this project in golang using i.e. https://github.com/xanzy/go-gitlab ? Asking as recently I am writing in golang rather than in python, and type safety is a plus

[nejch]

If moving to golang, it would IMO make more sense to just extend the terraform provider than maintain another custom golang tool.

As you might have seen with the terraform provider though, go-gitlab's attribute typing means you can say goodbye to the "pass arbitrary parameters to the API" approach here, so it would always lag behind GitLab's functionality as it would need to first be implemented in the library and then bumped here.

[jimisola]

I'm for python. That said, if we are reconsidering the language what we use for gitlabform then perhaps Ruby is a better choice since GitLab is written in Ruby? I was hoping that we could piggyback of GitLabs source code but it might not be possible. Might have to use another gem library such as https://github.com/narkoz/gitlab.

[grzesuav]

it was just a long-shot, I am bit focused on golang right now. Python it is then

[amimas]

I wonder how many people would cooperate on the project if it would be using the semi-standard python-gitlab under the hood?

Hey everyone. PR #582 just got merged to implement the ability to transfer project. It's done using python-gitlab library and added a wrapper class to the python-gitlab library. Hopefully this helps and we start to see a little more help with contributing features and/or maintenance (i.e. migrate existing features to use python-gitlab library).

[TimKnight-DWP]

@gdubicki - hi I'm working with Adam, we are preparing for GL 17 changes to ci_job_token and will want a way to control allowlists via gitlab form config.

So I'm planning on picking up some of the python-gitlab tickets

[TimKnight-DWP]

@gdubicki , myself @adam-moss and team will be working on a project for migrating Saas->Dedicated gitlab and looking at building out Enterprise capabilities for gitlab form.

We would love to talk about becoming Maintainers, what would you want from us? It's important for us and the Department here to support these open source tools rather than develop something in isolation

[gdubicki]

Hey @TimKnight-DWP and @adam-moss, great to hear that you want to cooperate on the project more! <3 Let's sync on the project's Slack, it will probably be easier and faster. :) Invite link: https://join.slack.com/t/gitlabform/shared_invite/zt-2h6nhisl0-oIJ6Xm6IA2sXmMh8ocUfTA

[TimKnight-DWP]

@gdubicki unfortunately caught a-foul of daft website restrictions on the enterprise firewall - would you be able to send an invite from slack direct to our emails please? That might work around the magic link above being blocked