SoylentNews is people
SoylentNews
The Debian project has suffered from a long string of negative events recently, ranging from severe discontent over the inclusion of systemd, to talk of forking the project, to a grave bug affecting the important 'wine' package, to the resignation and reduced involvement of long time contributors.
The latest strife affecting Debian revolves around a request for a Debian package of the GPC-Slots 2 software. This request has been rejected with little more than an ad hominem attack against the software's author.
In response to the request, Stephen Gran wrote,
This is code by someone who routinely trolls Debian. I doubt we want any more poisonous upstreams in Debian, so I at least would prefer this never get packaged.
Jonathan Wiltshire proceeded to mark the request as 'wontfix', and closed it.
While Debian does strive to maintain high standards regarding the software it packages, the negative and personal nature of this rejection, without any apparent technical or licensing concerns, appears to conflict with Debian's own Code of Conduct. Such a personal attack could be seen as contradictory to the Code of Conduct's mandate that Debian participants "Be respectful", "Be collaborative", and most importantly, "Assume good faith".
Given its recent troubles as of late, many of them concerning the poor treatment of Debian developers and users alike, can Debian really afford to get embroiled in yet another negative incident?
(Score: 2) by Bot on Monday November 24 2014, @11:06AM
It is a grave bug because the question whether it prevents running the software is yes, while much more difficult to pin down bugs like racee conditions would be classified not grave. This bug is not proof of carelessness either cause the maintainer might have run the test suite without discovering the problem, in a chroot. If all the bugs in debian were as serious as this jessie would be released tomorrow afternoon and it would be the best OS plus apps stack ever released in the history of mankind even if you hated systemd. The ssh key debacle was incomparably worse.
Account abandoned.
(Score: 0) by Anonymous Coward on Monday November 24 2014, @12:59PM
If the testing procedure was so flawed that such an obvious bug wasn't detected, then I think it is a sign of carelessness.
Not only was the bug itself careless, but the fact that it wasn't caught is careless, too.
Everything about that bug screams "failure", "low standards", and obviously "carelessness".