On 24/05/2025 12:46 am, Mario Limonciello wrote:
On 5/23/25 11:59, Andrew M.A. Cater wrote:On Fri, May 23, 2025 at 10:00:22AM -0400, Roberto C. Sánchez wrote:On Fri, May 23, 2025 at 10:59:47AM +0200, Marc Haber wrote:On Fri, 23 May 2025 08:57:36 +0100, "Jonathan Dowland" <j...@debian.org> wrote:On Thu May 22, 2025 at 4:56 PM BST, Ahmad Khalifa wrote:It's alive, not sure if sponsored by Red Hat/Mozilla, but both use it(and Kernel, KDE, the list goes on).Red Hat have transitioned almost entirely to JIRA.Thankfully that's not an option for us (not dfsg free).But it could be an option. If Atlassian offered the Debian project free (gratis) use of their platform (especially if they handle the administration), why wouldn't we accept?Three points: Having used Jira - I think I'd rather stick hot needles in my eyes.Atlassian are *EXTREMELY* unlikely to offer anyone gratis use of their software. Do remember why we have Git to replace Bitkeeper - free gifts can get withdrawn.Just my €0.02If we're at that point of "considering" having a second system to the BTS (or to augment) what would be wrong with using Gitlab issues on Salsa?I've done little research on the matter besides a quick search [1], but presumably the BTS software could be modified to build a bridge with the Gitlab issues? Then perhaps maintainers for packages that want to opt in could set a flag to have the BTS forward everything from BTS to Salsa for their packages.[1] https://docs.gitlab.com/administration/incoming_email/
Gitlab has a fully email based Service Desk feature as well, which we use at work for customer support.
https://docs.gitlab.com/user/project/service_desk/using_service_desk/
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
