Call for developers
alanfranz opened this issue · comments
Are you a (hopefully happy) docker-rpm-builder user? Would you like to level up and become contributor with full commit access?
Write a short description of who you are in this thread, most probably then I'll ask you for a PR/any kind of work you'd like to do on docker-rpm-builder. If the work is good (not perfect, I don't strive for perfection) I'll give you direct commit access to the development branch.
Amazingly, I'm in need of a patch which emerged today, might as well put it down here: #52.
In general, I'm probably in the same space as you currently are: I'm building RPMs for work, but I'm hoping that the need for them disappears in the near future. I can still help here and there, but I'd like to wait and see whether someone with more time and need appears.
@rassie if you just need RPMs for work and you can build without rpmbuild, check https://github.com/alanfranz/fpm-within-docker - I plan to maintain that myself for the foreseeable future.
Good to know, thanks. Never used FPM so far, must check whether it's enough for our use-case.
Hello.
I am Python developer, (Fedora/RHEL) RPM packager and Docker user so it seems that I know everything I need to become a developer of Docker RPM build. Moreover, my work is mostly related to Python 2/3 compatibility in applications so I can add Python 3 compatibility to DRB.
Unfortunately, I am quite busy and therefore I cannot promise that I'll spend much time on DRM. Moreover, it seems so complicated to me on the first look. For example, I wanted to add support for Fedora 27 but I cannot find any specfile or guide how to build DRB RPM for Fedora 27.
These are the reasons I cannot surely say that I am the right person to be a developer of DRB. What do you think?
BTW DRB seems to be a good project with a lot of supported OSs and great docs. Good job!
Okay, introduction phase is over 😄 Could you please share some guide how to build DRB RPM for Fedora 27. If so, I can install it and try to use it and then I can take a look how to fix some issues, review PRs and add Python 3 compatibility.
BTW I found this project when I was trying to find a way how to build RPM packages in parallel because you cannot do it with mock.
@frenzymadness checkout the git source on fedora 27, enter make. Admittedly, I don't have extensive developer documentation.
@frenzymadness I have just released 1.41 with Fedora 27 support. I've added a build image to docker-rpm-builder-configurations as well.
If you'd still like to help developing docker-rpm-builder, keep in touch. I'll need updating developer documentation, admittedly.
One note: I don't think python3 support is a must-do at this time. drb is not meant to be used as a library so, as long as distros offer python2.7 support, even as an optional, installable package, it won't be really needed.
@alanfranz I think I can be useful here like on the docker-rpm-builder-configurations project as a collaborator. Probably also @mnencia is interested.
Hello everybody, especially @gcalacoci and @mnencia .... so, in a quite epic screwup, I had misconfigured github notifications and I had read almost no github notification email in the last 12 months. Including those in this thread.
If anybody is still interested in maintaining and docker-rpm-builder, I'll transfer the project to a separate organization and give you full access rights, and help you transition the CI/package build system as well, if needed.
@alanfranz yes, @mnencia and I are still available to help here.
@gcalacoci @mnencia would you like me to create a separate organization, or would you simply like to transfer this project to 2nd quadrant or any of you?
@alanfranz sorry for the late response. This time I'm the one that missed a reply :) I would say an "ad hoc" organisation.
Very good, I'll setup that quickly, this time!
@gcalacoci @mnencia I have created the org and I should have given you full permissions, let me know if you've got full access to the repo.
Nex step would be migrating the continuous integration / publishing infrastructure. It currently runs on my private (and quite messy) Jenkins. Have you got any preference? Did you think about integrating with some systems you're already comfortable with?
What about GitLab? As long as we make a public project (and it should be public as its open source) we can use all features for free. I'm quite comfortable with GitLab (already manging two GitLab instances at work and also having a few automated builds here and there).