Hello,
I'm currently working on a tool called the Mass pre-builder. This is a set of tools aimed to help developers to create mass rebuilds around a limited set of packages, in order to assess the stability of a given update.
The basic idea is: given an engineering version of a component, build its reverse dependencies against it, and compare the result with the pristine version of the component.
This tooling make use of existing infrastructure (COPR so far), and is available under GPLv2 at the following address: https://gitlab.com/fberat/mass-prebuild
The request would be to be able to migrate the source within Fedora space in Gitlab, preferably under a sub-project. I don't have strict request on the sub-project name, Miro Hrončok suggested 'packager-tools' (https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RMTSUI6VTUBRHYKW7BMTWOYTKBEQ6VOD/).
I'd also like to have full access rights on the created repository, GitLab account: @fberat
No deadline, but preferably before the end of time :D
Thanks !
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
So, you just want this so that the source is at a more role based area rather than being under your specific space?
We can do that, but I wonder... would it make more sense to add this into the existing fedora-packager package? https://pagure.io/fedora-packager/ it's not gitlab, but I would think that would be a good place to put it?
Thoughts?
The mass pre-builder is more than a small script. For now it is accumulating about 2k lines of code and is expending, both in term of code size and contributor's role. I believe it needs its own space. For reference the scope of the tool is covered here: https://gitlab.com/fberat/mass-prebuild/-/blob/main/README.md
The main reason for the move would be to have it in a more "public" space. We considered 2 options so far, the Red Hat space, and the Fedora one, but my team and I thought Fedora would be better for visibility and openness. The collaboration with Fedora is important for us, as we believe it can increase confidence in packaging "higher risk" changes.
ok, fair enough.
I've created the sub-project... and invited you as owner. :)
Let me know if you need anything further there.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@kevin That looks good, thanks for your support !
Login to comment on this ticket.