Julien Plissonneau Duquène <sre4e...@free.fr> writes: > Le 2025-01-24 13:00, Andrea Pappacoda a écrit : >> Same for me. In addition, on the topic of making things easier for >> new >> contributors, when I first started using Salsa I felt lost in the >> myriad >> of features and options enabled by default. Not only 99% of projects >> hosted on Salsa don't need features like "Model experiments", but >> keeping them enabled makes the platform harder to use. The BTS, on >> other >> hand, might not have a modern user interface, but its simplicity has >> value. >> Another big usability improvement in my opinion would be to >> automatically enable CI when the `debian/salsa-ci.yml` file is present. >> This way, users don't have to be familiar with GitLab's web settings UI >> to enable and customize the CI jobs. Not sure if this has been >> mentioned >> before. > > Reading things like this I have the feeling that maybe a custom web UI > and service could be a worthy development to complement the stock > GitLab UI.
I think that sounds like a lot of work in order to duplicate a subset of the existing functionality -- is another bespoke system what debian needs? I do agree that the defaults on salsa should be re-thought -- i'd think that the few things that debian values, like CI, merge requests and notifications should be on, and many other things that no-one seems to use (wikis, badges, service desks etc) should be off - with the option for anyone to change things.
