This is a good, levelheaded response. But it makes it seem as if the process of becoming a sponsored maintainer was straightforward.<p>It's not.<p>A number of months ago, I tried getting trimage (a gui image optimizer, <a href="http://trimage.org" rel="nofollow">http://trimage.org</a>) into debian. Since I already had a working Ubuntu PPA, I figured it wouldn't be too hard. Packaging instructions for debian are available at various official websites, but contradictionary and they all seem to presume you have packaged for Debian before. Jargon like RFP (request for packaging) and ITP (intent to package) is thrown around frequently without explanation.<p>Luckily, there is debian-mentors, meant to help upstream developers with becoming a sponsored maintainer. Most of the debian-mentors site links to outdated packaging instructions, using which will mean you will be ridiculed on the way-too-hostile mailinglist. Trying to do 'the right thing' is almost impossible, as most of the feedback will depend on the personal opinion of the person responding. I suspect this is because they, too, don't know which packaging instructions to use or point to.<p>Trying to get my application into debian has been nothing but a massive, timesinking frustration, and I wish that wasn't the case.
This significantly increases my respect for Zed Shaw.<p>Yes, he wrote an offensive post crying for blood, but after he had a chance to cool down, he used his own fame and audience to exhibit a well-reasoned response from someone who disagreed. That's a very adult thing to do. In some ways, it's actually better than an apology.
I am Debian Developer with upload rights.<p>If HN people want to get involved with Debian, packaging and so on email me and I'll do my best to help you.<p>Probably the best way to fix whatever you believe is wrong is by getting involved.
Coincidentally, I just happened to see a link on Reddit leading to a post by the same Ersek: <a href="http://groups.google.com/group/comp.lang.c/msg/22e3473f80eec512" rel="nofollow">http://groups.google.com/group/comp.lang.c/msg/22e3473f80eec...</a><p>Like his message to Zed, it's clear, concise, and seemingly accurate. It also includes a wonderful and well commented example program in expert idiomatic C showing signal handling. I hadn't even known comp.lang.c was a going concern!<p>It's exactly the sort of quality code I'd expect from someone who writes such good prose. While I'm sure there are some examples of good prose writers who can't code, are there any definitive examples of good C programmers who can't write? Or is this just a "true Scotsman" problem?
I still think my point at <a href="http://news.ycombinator.com/item?id=1735344" rel="nofollow">http://news.ycombinator.com/item?id=1735344</a> is important. If Debian didn't throw away unit tests, a lot of these integration errors could get caught automatically.
This is a reply to <a href="http://sheddingbikes.com/posts/1285659877.html" rel="nofollow">http://sheddingbikes.com/posts/1285659877.html</a> which was discussed here <a href="http://news.ycombinator.com/item?id=1734936" rel="nofollow">http://news.ycombinator.com/item?id=1734936</a>