4 ms·
I don't think it necessarily needs a monorepo, but having every package on Salsa (Debian's GitLab installation) would help.
by JoshTriplett 8y ago
I don't think it necessarily needs a monorepo, but having every package on Salsa (Debian's GitLab installation) would help.
- thiscommuni 8y agothiscomm ent juat for this comment this account password is cator but they needed 8 lettera so I added a F U C K at the tail Like country Joe at Woodstock live added It on the Head with trhee hundred thousans you fuckers out there eehhha! woodstock!!! whatever forgot what I was going to say againnn thata rhw problem with explanatioua offtopics going and with iphone fckn5 fckn typing shit (sont call it a aystem nor a keyboard fuck) anaway... id is a public open aource repo or repos or whatever you put it all in neaby place for easiness and selfcompletion righ but a private business is fucked anyway, even separaring all in diferent repos like the ancient naval fighting weapon named greek fire anyfuckingway they see everyfuckingahit and anyshit ans anyfuckingthing you fucking programm my friend So qhats the fuxking point of givimg fuxking free away fucking texhnology ??? if you know what I fucking mean righ... thanks
- andrewharvey 8y agoThe move to GitLab was a glimmer of hope that one day I'll be able to help contribute to the project which I'm a heavy user. I wish they went all in and used GitLab Issues for bugs and GitLab CI/CD to auto-build packages for both validation and pushing new packages into the Debian repositories.
- h1d 8y agoI'm not following the situation but what's stopping them from improving their packaging system, except for being complicated?
- genghizkhan 8y agoIf the systemd discussion has taught me anything about Debian governance, getting everyone to agree is going to be a pain. Far easier to let it be.
- debiandev 8y agoLoud minorities and trolls on public mailing lists are not representative of the community of DDs and DMs.
- JoshTriplett 8y agoNo, but they're representative of the decision process. "Should we do A or B" results in people popping up supporting A, B, C, D, and E, and the decision tends to be "let's support them all". And as the original article we're commenting on discusses, that "support" comes in the form of "hey package maintainers, here's what you have to deal with".
- debiandev 8y agoThis is a misunderstanding of how Debian works.
- JoshTriplett 8y agoI've participated in the Debian community for 18 years, since Potato (2.2). I have a fairly good practical idea of how Debian operates. The above description was based on many, many, many decisions over the years. On the rare occasions that Debian has to actually decide something rather than answering "X or Y" with "yes" (and the decision doesn't fall solely to a small number of developers responsible for the packages in question), it results in painful institutional friction. I love using Debian, I care deeply about Debian Policy and Debian's procedures, I enjoy many aspects of the Debian community, and I'm also well aware of where Debian has difficulties.