Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)
Pirate Praveen <email@example.com> writes:
>> Debian needs feature X but it is already in the e.nterprise version. We make
>> a patch and for commercial reasons it never gets merged (they already sell it
>> in the enterprise version). Which means we will have to fork the software and
>> keep those patches forever. Been there done that. For me, that isn't
>> I don't want another Nagios.
> I agree this is a legitimate concern. I have asked Gitlab Inc for their
> policy on merge requests to Gitlab CE for features already in Gitlab EE.
> Based on their reply, we can decide how to proceed. If their reply is
> positive, I will ask them to make it public, and we can go ahead with a
> debian.net instance of Gitlab. If their reply is negative, we can drop
> gitlab and consider Pagure (second best option).
We do patching as part of our daily packaging already: to replace (or
circumvent) non-dfsg functionality, to integrate into our environment,
and everything else that upstream is not willing or able to apply
himself but is good in our opinion. Depending on the package, you may
find huge patches for our packages
I would not see why a missing functionality of gitlab would be different