Search Results: "ag"

17 November 2006

Biella Coleman: The Politics of (lyme) bacteria

Recently I read an amazing review of patient advocacy and health (counter)movements by Steven Epstein from the STS program at UCSD. It is still a draft but bound to be published in the New Handbook of Science and Technology Studies and when it is, anyone who works in this area will gain so much from reading the review. It was stunningly broad yet highly specific. He is able to synthesize an enormous literature on patient advocacy, a field that has seen a blizzard of activity, especially in the last twenty years. Along with providing points of entry and departure into the field, he also examines who the burgeoning interest in the field of STS. What I found interesting is that there is very little work being done on a topic I happen to know a lot about, lyme disease and whose politics I have been following since at least 1999. I am not sure why the lacuna but it is an odd disease dripping and screaming with controversy and seems to stand apart from many illnesses, in part because of its odd dual existence. On the one hand, it is an illness that the medical establishment totally recognize as real (and thus in some respects is unlike the class of syndromes from MCS to chronic fatigue, which another STS researcher, Joe Dumit provocatively describes as illnesses you have to fight to get ). But that is only half the picture because mainstream medicine tends think that lyme is not only easy to diagnose but also to treat, so much so that if a person thinks they have lyme (even after a round of antibiotics or lacking diagnostic markers), the are either seen as suffering from something else (and usually then told they have one of those highly contested syndromes), or more often just crazy. So it exists dually: at once recognized but only narrowly, so that in another form, that of chronicty, lyme cannot exist. It is this dual quality of lyme that defines and shapes its politics and just recently, new developments have fueled the controversy. Namely it follows from the Infectious Diseases Society of America new guidelines for the diagnosis and treatment of lyme, published last month. In a nutshell, they basically re-reduce lyme to a very easily diagnosable and treatable illness, calling for even more strict guidelines for its diagnosis than now exist. They sanction a small range of blood tests and thus totally nullify the role for clinical diagnosis, which even the CDC had acknowledged as vital in times past. Unsurprisingly this has thrown the chronic lyme community in a total tizzy and they have not taken this sitting down. A petition has been launched and protests have been planned. And amid the controversy, politicians have already heard the call to arms. In the state where lyme is a famous entity for it was first discovered there, Connecticut, its Attorney General is calling for an anti-trust investigation into the Infectious Diseases Society of America, in essence for using their clout and prestige to legitimate a gold standard in diagnosis and treatment, when it seems far from obvious that this should be the standard. According to the LDA press release:
The national non-profit Lyme Disease Association (LDA), representing more Lyme disease patients than any organization in the United States, applauds Connecticut State Attorney General Richard Blumenthal for beginning an investigation into the Infectious Diseases Society of America (IDSA) Lyme disease guidelines development process. In an unprecedented move, the Attorney General’s office filed a Civil Investigative Demand (CID) to look into possible anti-trust violations by the IDSA in connection with exclusionary conduct and monopolization in the development of the Lyme guidelines
What I find so interesting is that this latest chapter in the grungy and torrid politics of lyme encapsulates the very nature of the politics of lyme, which really is about the agency of bacteria and in the Latourian sense. If Pasteur had to put a lot of effort into making credible the bacteriological model of disease as Brunto Latour covers in The Pasteurization of France and if there was plenty of future prostelyzing needed to bring credibility to the bacteria to more general publics, as Nancy Tomes illustrates in The Gospel of Germs, well now, I think we are in an era where we think we have such intimacy with the biological ins and outs of bacteria, it is almost impossible for the scientific community to imagine bacteria as such complex organisms that they can be in fact very difficult to diagnose, eradicate and treat. It is just no longer part of the basic conceptual universe of most doctors and medical researchers to think of bacteria in this way. The LDA press release acknowledges this very fact in the following way:
The October 2006 guidelines do not acknowledge that a complex bacterium such as the Lyme disease spirochete could possibly survive in the body and the brain, evading the immune system and short-term courses of antibiotics.
For many lyme researchers and doctors, since lyme is a bacteria and we know how to treat those pesky critters, it is frivolous to even imagine or contemplate otherwise. I would call this a hubris that arises not from the arrogance of doctors and the medical establishment but following the heels of success that medicine has indeed had with conquering the bacteria with antibiotics. Even new forms of poweful and highly resistanant TB are still treatable with a potent cocktail. That is, at a cultural level, I understand the blinders. At a political level, however, because people are suffering and because it is plausible that lyme can exist chronically, it is imperative to unseat this cultural comfort borne from past success to get the ball of research rolling anew. I think bacteria (and parasites for that matter as a recent smattering of articles demonstrate) are a lot more savvy creatures that should be treated as novel, wondorous creatures, once again. I would dare say the medical establishment, by refocusing energies on that which they think they have solved, would find themselves quite surprised. updateHere is an article discussing the issues.

Joey Schulze: Version 0.3 of GUI APT Key nearly finished

Now that version 0.2 of the graphical APT key manager has been migrated into Debian testing the work an update has been nearly finished as well. The code is stable and a final call for translation updates has been sent out to the translators. The new version is expected to be released on Sunday. Hopefully it'll migrate into etch as well. This version should be usable even more intuitively. A context-sensitive menu will pop up in the key listing and enable the user to display key details or to remove a key. This key-specific functionality has also been moved into its own menu and should therefore be a lot easier to reach. Deletion of a key can only be achieved by using one of these menus. Hence, it should be more difficult to delete a key by accident. The other buttons have been converted to stock buttons which come with nice graphics and hence should be easier to understand as well.

Erich Schubert: Apple spam

One more reason not to buy Apple: they spam. Yesterday and today I received Spam from "insideapple.apple.com". The same mail twice I think; and to the same old old email address. I can even trace back that they bought the email address from the old uni.de student portal site (which has since been sold or relaunched, I don't know). I unsubscribed yesterday, but received the same mail again today. Apple, thats NOT the way to go.

Alexis Sukrieh: Logger::Syslog, my first CPAN-candidate Perl module

I wrote a Perl module a couple of years ago, and got used to it, I just cannot code without that module now. It’s called Logger::Syslog and is a wrapper over Sys::Syslog that lets you deal with syslog in a very simple manner. Use the module and enjoy the easiness of calling info(), warning(), error() or whichever Syslog message level you like, there is a function wrapping it. It also works properly under a mod_perl environment an logs your message with additional information coming from the Perl stack (module, function name, line number, …). I use that module quite everywhere I use Perl : at work but also in my Free Software projects, like Backup Manager. It’s really time to release an “official” version that I can rely on in the future. Next step is submitting the module to the CPAN (it’s pending) and then, debianize it so backup-manager can depend on it. Todo: set up a public SVN repo to handle the sources. Updates

Steve Langasek: On setting and meeting goals, and statistical fun

While NMUing plays an important part in getting us to a release, as shown by the thousand or so fixed-in-NMU RC bugs that we recently cleaned up the BTS state on, it's evident after doing this whole release-managing thing for a while that there is a very high (non-linear) correlation between the age of an open RC bug and the likelihood that a release manager is going to have to touch it at some point in order to get it fixed. By and large, maintainers really do a good job of fixing their own packages, which is probably something we don't say enough - maybe 75% of all RC bugs, I'd guess, will (or would) get fixed by maintainers in the first week without anyone needing to poke them about it, and of the remainder, probably another 80-90% get taken care of by BSPers and serial-NMUers like bug-a-day mascot Steinar Gunderson. That's why I'm not bothered overly much by the idea of full-archive searches for hidden RC bugs, like Lucas's piuparts tests, affecting the release timeline, because I know that 95-98% of those bugs are going to be gone two weeks after they're filed anyway, especially when they're no-brainer fixes to maintainer scripts or dependencies. But then that leaves the other 2-5%, which are the ones nobody else has fixed. And why hasn't anyone fixed them? Because they're the hard ones, of course... So although I follow the debian-bugs-rc list and occasionally swat a few non-bugs closed to save the maintainers time, and also provide some nudges when it looks like a package is causing RC bugs to be filed on other packages, my goal for the last full week of my Dunc-Tank contract was to get the count of etch RC bugs unfixed in unstable that are 20 days old or older down from around 50 to under 30. This seemed a reasonable goal, since it had been at 80 the week before, and it would go a long way towards helping the real blockers on the release. Initially I was aiming to bring down the count of RC bugs unfixed in testing that are 20 days old or older to this number, but quickly realized that this wasn't going to be realistic because it depended too much on the autobuilders all operating optimally and there wasn't time to both help fix 20 of the hardest RC bugs and handhold 60 RC bugfixes into testing in one week. In the end, we did miss this lesser target by a day or two. Still not a bad week's work, given that I'm pretty sure I fixed about 20 of these bugs myself in that time period (through NMUs, removals, and analysis+downgrades) and they seem to average 3 hours of work for a fix. And we've been holding at or below 30 on this list of bugs since then, so we're successfully keeping up with new bugs aging past the 20-day mark, which is also a good sign. Unfortunately, I seem to have left myself to fix the alpha Xorg 7.1 bugs on my own time. :) By now the announcement has made the rounds that the release team doesn't think we can hit the Dec. 4 target date because more time is needed for a final release candidate of the installer. Does that mean that RC bugs were the wrong thing to be focusing on for the past weeks? Well, no; if you want one place in Debian where Brooks' Law holds, I think you'll find that getting a d-i release out is it, and we still have a hard road ahead to make sure we do get our other RC issues sorted out in the same time frame. The installer just happens to put a lower limit on a release date, we still have an opportunity to screw it up from there. ;) At least the statistics suggest that we're going in the right direction. Only 13% of RC bugs fall into the "20 days or older and unfixed" category. Half of all RC bugs over 10 days old have a fix of some kind in unstable, and 64% of all reported RC bugs are less than 10 days old. We'll see whether this graph backs me up on this in a couple more days.

Michael Janssen: I work hard, every day of my life

Most of my fitness transition plan has been focused on exercise. Get more exercise and eat the same as you did before, and you will lose weight. This has to be true, based simply on physics. Back when I was using the Hacker's Diet, it worked like a charm. Then it was all about eating less calories, because I wasn't really keen on doing exercise in my olden days. It worked for a while. Unfortunately I got stressed and stopped countign calories, and weighing every day. I've started the weighing again, and maybe I can actually fire up gnuplot again and produce some pretty graphs like the one on the left.


I've had an iPod for approximately 5 years now. That puts me a bit ahead of the curve. I still remember seeing the original iPod commercial, and looking literally seconds later for how much it was, and seeing how much I could sell my old player on eBay for. Having been in the mp3 scene for a while at that point, I knew that it would turn everything on it's head. I got it and replaced my normal player for walking to and from class and listening while coding. Now I have a new iPod video, and it is the chief entertainment while I'm in the exercise room. At first I was just listening to my fairly large music collection. Then I started listening to podcasts again - they are about the right length, and I enjoyed them. Now I've harnessed the power of the video iPod to kill two birds with one stone: I'm watching my large collection of Anime at an hour a day. This means about 3 episodes if I skip the openings and endings. I also watch Heroes on Tuesday nights, after I transfer it from the TiVo. The only problem I'm having with this setup is that the screen is small, so I need to hold it fairly close to my face in order to read the subtitles.

Today marks one month on the diet and exercise regimen. I started on the scale at 344 and this week's average was 337, 7 pounds lighter. I'm going a little slower than my goal of 2 pounds per week, but I seem to be hitting the right buttons at least.

This week (Nov 10 - Nov 16):
Minimum: 335.5 (-2.5) (Nov 14)
Maximum: 339.5 (-0.5) (Nov 16)
Average: 337.2 (-2.05) (137.2 to goal)
Exercise Calories: 2563 on 5 days
Average Calories per session: 512.16

Tollef Fog Heen: A replacement for screen. Ish.

Adrian von Bidder writes about retty, a tool to make processes reattach to your terminal. While useful, it seems mostly like a limited version of cryopid which seems even more insane and crackful, but quite cool nevertheless. I have not had a chance to actually try cryopid yet though, so if any of you have, please blog about your experiences with it. Oh, and please package it, somebody.

Joerg Jaspert: Call for Papers for DebConf7

So, after a lot of work to get the system up and running (and then changing it until others from the team liked it) we finally sent out the Call for Papers and Registration informations for DebConf7. Now, only about one hour later we already have 37 registered users in that system. Thats fast. A nice detail about the new system we use (except the complete change it means for everyone :) ) is that accounts you create now get re-used for all future DebConfs. No need to reenter your data every year. Additionally we (as in DebConf) can offer other Debian related events the ability to use this system for their stuff. That means - if you organize a Debian related conference and want to keep track of attendees, events/talks, manage a schedule, or just parts of this - contact me, it can be arranged easily. The advantage for your attendees/speakers is that they only need one account at one system, not one for every conference. And you as organizer get a fully running system for free. :)

Simon Richter: Ow.

After eating approximately 1 kilogram of Salmiakki, I now feel sick. Please remind me to not do that again.

16 November 2006

Russell Coker: biometrics and passwords

In a comment on my post more about securing an office someone suggested using biometrics. The positive aspect of biometrics is that they can't be lost, no-one is accidentally going to leave a finger or an eye in their car while they go to a party while other authentication devices are regularly lost in such a manner.

The down-side is that having your finger or eye stolen would be a lot less pleasant than having a USB device, swipe-card, key, or other security device stolen. I think that it's good to have an option of surrendering your key when under threat (for the person who might be attacked at least).

Rumor has it that some biometric sensors look for signs of life (EG temperature and pulse), but I believe that these could be faked with a suitable amount of effort. A finger attached to a mini heart/lung machine should make it possible to pass the temperature and pulse checks (although I don't think that I have access to any data that is important enough to justify such effort on the part of an attacker).

One thing that biometrics could be useful for is screen-blankers. It would be good to be able to have a screen-blanker for your computer that operates when you go to get a coffee. For a period of 10 minutes after leaving a biometric method could be used to re-enable access. After that time a different method would ave to be used. This gives the convenience of biometrics for when you need it most (the many short trips away from your computer that you make during the day) but removes the benefit for an attacker who might consider removing part of your body. Also I am not convinced in the general security of biometrics. There are claims that you can make a finger based on a fingerprint which can fool a biometric sensor. If those claims are correct then a biometric sensor would still work for a coffee break (presumably you are not far away and will be back soon, and other people are in the area). The coffee break security is usually to prevent casual snooping such as colleagues who want to see what was on your screen but not actually do anything invasive to get it. Another benefit of biometrics for a screen saver is that although I trust people in the same office as me (whichever office that may be) not to try anything when they might get caught I still don't want them shoulder-surfing my password. Replacing the trivial authentication cases with a fingerprint reader would prevent that.

In the KDE 1.x days I had a shell script launched when the lid closed on my laptop which would lock the screen (the screen-saver ran in the background and a signal could make it lock the screen). This meant that I could merely close the lid of my laptop to lock the screen, this is fast and easy and also is not immediately recognised as locking the screen. Some people get offended if you lock your laptop screen when in their presence as they think that you should trust them enough to leave your most secret data open to them (generally people who aren't serious about computers - I'm sure that the same people would happily lock their diary if I was ever in the same room as it). Being able to lock the screen in a non-obvious way is a security benefit.

Regarding the comment about using a USB device to store passwords, there are two problems with this, one is that all passwords will be available all the time, this means a program that is permitted to access password A would also be given access to password B. The other is that the passwords can be accessed easily. The ideal solution is to have an encryption device that uses public key cryptography and stores the private keys on the device with no way of removing them. It would also permit the user to authorise each transaction.

I would like to see a USB device that stores multiple GPG keys and implements the GPG algorithm (with no way for anyone with less resources than the NSA to extract the keys). The device would have a display and a couple of buttons. When it is accessed it would display messages such as "signing attempt on key 1" and allow me to press a button to authorise or reject that operation.

This means that if I insert the key to sign an email I won't have a background trojan start issuing sign and decrypt commands. The only viable attack that would be permitted is the case where I want to sign a message and my message is sent to /dev/null and a message from an attacker is signed again. The non-arrival of my original message would hopefully alert me to this problem. I am not aware of any hardware which supports these functions.

Also I have just received a couple of RSA SecurID tokens as a sample. An RSA representative phoned me to ask about my use of the tokens, I said that I am an independent consultant and I have been having trouble getting my clients to accept my recommendations to use such devices and that I want to implement them on a test network so that I can give more detailed advice to my clients and hopefully get them to improve their security. For some reason the RSA rep found that funny, but I got my sample hardware so it's fine.

David Moreno Garza: On Jordi s arrival to DebConf7

I simply loved this; on the ways of arriving and reaching Edinburgh, to get to DebConf7 :D
Swimming
Jordi, please tell us when you’ll arrive at Leith, and we can arrange for someone to come and pick you up with a towel and some whisky.
Heh, that’s our ironman. ;-)


Jordi working out to get to DebConf7.

Gunnar Wolf: Of broken promises and fixed websites

Over five years ago, I wrote a very simple web-based system. This system, however, did some basic client-side (Javascript, of course) validations before sending the data off to the server. And it worked nicely. On Linux, of course.
The system went live.
It worked correctly less than 1/10th of the time. Yes, somewhat strangely, quite close to the ratio of Netscape/MSIE users.
Yes, a Javascript coding bug.
The embarassment made me swear not to get close to Javascript ever, ever again.
Of course, we live in a world where idle loops get optimized and where infinite loops have an ETA, this had to change at some point. Earlier this week, I decided to unfuck a web layout that worked (again) correctly in Mozilla and KHTML, but horribly in MSIE. I didn't care before, because this layout was used on a production system at work, but its users were only two colleagues and myself - Only I'm about to put a public module up. I re-did the site layout and CSS (I cannot believe Dreamweaver code is that ugly!)... The only problem was, I now know, quite common: I needed equal height CSS-made columns. And although I had come to several pseudo-solutions, they all appeared pseudo-b0rked in one or more pseudo-browsers. The only way I found to get it working was to free myself from prejudices and go back to Javascript. BTW, the Javascript X library looks quite handy - but at over 50k, it's not something I'm terribly happy about including in a website.
What's next? Am I going to fall for coding over-AJAXy sites? I hope to maintain at least partial sanity.

Andreas Barth: Release update sent, and upgrade testing

On Thursday, the release update we have been busy preparing was finally sent out by Steve. This has clarified some of the questions people have been asking for some time. Also, more comments on the release notes have been merged. We are now at an state where I'm happy to let users work with the release notes - though one large section still needs work: What is the appropriate order for upgrades of kernel and packages. After that was done, I started myself with some upgrade tests to see how the packages really behave. More on that on one of the next days ...

Joachim Breitner: Kofi-Annan Center for Excellence in ICT

Until now, I always had to tell the not very joyful story of the motivated volunteer who came to Ghana to run against a wall of disinterest and misunderstandings. Luckily, things will change:Yesterday, I had an appointment with the Director of the Ghana-India Kofi-Annan Center for Excellence in ICT (KACE), where I asked, with little hope, if they might make more use of me in the next weeks, until I will most likely return to Europe. To my surprise, She found that an excellent idea and immediately referred me to the techies to discuss the details. Today I saw the principal of the SOSHGIC and my current employer, trying to find out if this would be possible. She agreed that it makes more sense for me to work at KACE instead of the school, and would lend me to them while still being empoyed by SOSHGIC. I will be around the school a few times, to finish some reports and two more club meetings and luckily I am still allowed to live in the flat. I think I ll spend another one or two weeks in January at KACE (as a real volunteer then), before I head back to my boring standard safe study life.The first, smaller, project at KACE came up spontaniously during the meeting yesterday: I mentioned the game infon (see my last blog entry), and she was very interested in that as a programming teaching aid. My idea is now to polish it a bit, make it a bit easier to use for beginners, improve documentation, create debian packages and maybe work on some lessen plan suggestions. The author of infon, dividuum, is also quite happy about the news and the attention that his work might get now.The other project is my idea about an internet caf distribution. It happens that the team at KACE is working on a very similar thing (called Community Information Center ) for the government, and they will start a Linux version in very few weeks, so I think I can help there as well. I expect that a lot of work for Skolelinux can be used here, so I m looking forward to work with the DebianEDU team a bit.

I m also looking forward to work with my future collegues at KACE. All of them qualify as geeks, in my opinion, most are Free Software advocates (or at least approvers), and the work athmosphere is very relaxed. Seven weeks of (almost) DebCamp! I ll keep you up to date...

Jordi Mallach: Debconf7 travel options

The Debconf team just announced that registration is now open for next year's Debconf7, to be held in Edinburgh next June. The preparations seem to go at good pace, and they already have a Travel wiki page with information so attendees can start looking for the best option for them. I am delighted to see they have been thinking about every case out there and it will be possible to swim all the way over to Leith, not even getting a bad cold. Thanks! This of course is yet another reason to plan ahead so I don't miss out, like last year in Mexico. Erinn, remind me about it in late May or so, mkay?

MJ Ray: An Uneasy Multilingualism

In the past, I have suggested that it was a mistake to make a state-based fsfe-uk mailing list instead of a language-based fsfe-en list. The discussion resulting from a call for Welsh and Irish help is a pretty sad example of some reasons why.

Michael Janssen: Quickie Hack: Online X-mas list

It's getting around that time of year when kids start singing little annoying songs and thinking of the toys that they will be getting in slightly more than a month. In my family, when everyone gathered for thanksgiving, the younguns were expected to have a list which could be disseminated throughout the family with everything they wanted. This avoided some of the more clich gifts such as sweaters and socks. But who's to say that grownups can't have a little fun as well? It's rather easy to use del.icio.us as a holder for your whole Christmas list. If you find something you want, just add it to your del.icio.us bookmarks with a special tag - I'm using “xmaslist2006”. Using del.icio.us gives you a few advantages over the traditional list: Things on the list need not be completely techie - if you're just looking for a nice sweater, you can add a general page or a representative item with a comment on it. Perhaps include your sizes as well, especially for items which come in a large number of sizes like pants. With any luck, you'll get just what you want this year.

Adrian von Bidder: A replacement for screen

ITP: retty says:
retty is a tiny tool that lets you attach processes running on other terminals. So you were running that mutt outside of screen at your home machine and now wanna check your mail? Attach it with retty, do whatever you want, detach it again and everything is as it was before. You don't have to run them all in screen just in case.
Daniel Jacobowitz analyzed the tool a bit:
What it seems to be doing is injecting code onto the stack which causes the target process to open your terminal and dup2 it onto stdout, stderr, et cetera. Interesting.
Interesting isn't really the word I'd use here. More like Eek! Incredibly ugly, but incredibly useful if it works reliably.

Evan Prodromou: 24 Brumaire CCXV

Interesting Techcrunch article about aboutus.org, the wiki about every domain on the Internet. It was started by Ray King, an extremely nice guy that we've met at a couple of Wiki events, and it seems to be doing really well. I guess he just closed an initial round of investments, which is great. There was an article about Aboutus in the Portland Business Journal. Although I don't think it's a "potential Google" (!), as the reporter does (gotta love the home town crowd), Aboutus is a neat idea and it's a good group of people, too. tags:

Puck Quebecois Speaking of things that are rocking, I just got an invite to Le Puck Quebecois. It's the Montreal tournament of the Hocky Association of the Arts, a group of artists and musicians nationwide who love to play hockey against each other. The organizer is Jeff Waye of Ninjatune, who combines in one person an unhealthy obsession with music with an unhealthy addiction to hockey. It should be a really fun amateur hockey tournament. All proceeds go to charity, of course. tags:

Not only but also Next week, 30 Brumaire, (or 22 November for those of you who need some math help) there's a meeting of MSLUG, the Montreal Scheme/Lisp Users Group. I have get to get out to an MSLUG meeting, but I think this one will be my first. It's admirable that the group has pulled off so many meetings in the last 3 years. tags:

Lenny So, at the bottom of this release message, we get the name of the post-etch Debian release: Lenny. Is Debian now using codenames from The Simpsons? I think Lenny Leonard is as nice as the next guy, but we're still going through the minor characters in Toy Story. I've scoured the Toy Story credits and Toy Story 2 credits, and "Lenny" is the name of the little binoculars character, which gets about 12 seconds of screen time, if I remember correctly. Man, we're really scraping the bottom of the barrel on this naming convention. tags:

Hey Doc! Don Marti's intro to OpenID for Doc Searls is cracking me up. I'd mentioned in my articles for LinuxWorld last week that I'd written an OpenID extension for MediaWiki, and I guess now Doc wants to know how to use it. tags:

Stefano Zacchiroli: cdbs relevance

/me on the Relevance of CDBS Whoa, people discussing about CDBS, I can't help joining them. My position: I love CDBS. I started switching my packages to CDBS an year ago or so and nowadays I've almost finished. I understand that people not knowing CDBS might have trouble fixing bugs in my packages, but that's life and it's the same as having to fix a bug in a software written in a programming language you are not fond of. It's just a matter of setting a minimal standard: today people in the NM have to learn debhelper, tomorrow they will have to learn CDBS too. I think it's worth the effort, because CDBS, if used extensively in our archive, has the benefit of providing a single place where to massively make changes to potentially all packages of the archive. That's a huge win for QA in Debian. The same does debhelper, but it only takes care of technical aspects in the packaging process while CDBS also takes care of behavioural aspects. Of course CDBS has drawbacks and nuisances (the available hooks for examples are not properly standardized nor documented IMO), but I think it's a step in the right direction. In Debian we should push more and more toward the possibility of making changes in a centralized/batch manner, so that when maintainers tend to get MIA we have a quick and easy way to take over their unfulfilled duties. Collaborative maintenance is a social step in that direction, CDBS is a technical one.

Next.

Previous.