Search Results: "xam"

15 October 2006

Benjamin Seidenberg: RC Bugs and how to not handle a transition

Thjis: This is the right time to automatically search for RC bugs. So was a year ago. Although we want the RC bug count to drop, an RC bug is still an RC bug regardless of whether we know about it or not. And many RC bugs didn’t exist a year ago. Take for example #392121. A package name change in a build-dependency caused my package to FTBFS. This bug would not have existed a year ago, but needed to get fixed for etch. Incidentally, when you go through a package rename for a development package, it would be nice to check what packages build-depend on the old package. A september changelog entry for cli-common says:
- Removed transition dependency for cli-common on cli-common-dev. (7 month for a package rename transition should be more than enough)
However, at no point in that seven months did anyone email me or file a bug report to tell me that the name changed. This bug wasn’t caught until someone rebuilding the archive noticed.
Actually, this might be a good idea for an infrastructural change. Would it be possible to set up a script that notices when packages are removed and sends a notice to the maintainers of any packages build depending on them?

Lucas Nussbaum: Mozilla, Debian and Iceweasel: the Mozillian point of view

During the Journ es du Logiciel Libre 2006 (an excellent event, thanks to the organizers), I had long chats with people from Mozilla Europe (in a more constructive way than what others did). This is mostly second-hand information, since the well-informed guys from Mozilla Europe I talked with got their info from other Mozilla developers, so it might be slightly inaccurate, but still help to understand the issue. More details welcomed in comments. The Mozilla Foundation goal is to prevent the web from becoming a proprietary web, by ensuring that Firefox, their product, has a big-enough market-share. I find it a bit disturbing to hear free software people speak about product and market-share, but well, OK. Of course, it’s quite difficult to achieve >20% market-share only with GNU/Linux users. :-) They put a very high emphasis on the User experience. They want Firefox to look exactly the same on all platforms, even if some features (automatic plugin installation, automatic upgrades) do not fit well on a GNU/Linux system (such features don’t work with the Debian build). They want to enforce their trademark to prevent attempts to ruin their reputation to succeed. After a question asked by Dave Neary (GNOME) to Tristan Nitot (president of Mozilla Europe), Tristan gave the example of this hacker who said he found critical security bugs in Firefox before admitting it was a joke. He also gave the example of Microsoft indirectly founding SCO. Dave Neary remarked that some people could probably be trusted (like distro maintainers). But, if I remember correctly, Tristan said that it was difficult to allow some people to use the trademark without allowing everybody to do so. Also, allowing Debian to use the trademark without allowing derivatives to do so is not possible (DFSG#8). Iceweasel is considered a good thing inside Mozilla Europe (”It’s what we have asked them to do for a long time!“). However, some people are bitter about the fact that Debian seems to have chosen to use a gnu.org-hosted fork instead of just renaming the package to iceweasel. During Tristan Nitot’s conference, I asked a question about length of security support (only 18 months for the 1.0 branch). The answer was that distros were supposed to upgrade to newer Firefox releases even on their stable releases (!) or to come and help with security support for stable releases. Also, the fact that Debian chooses to package Firefox following the FHS is considered a source of problems. Somebody claimed that Debian was the only distribution to package Firefox this way (seems strange, but I did not checked this claim). I’m not sure how this fits with other Mozilla-based browsers such as epiphany. On a more technical side, they also claimed that Debian wasn’t properly collaborating with Mozilla, sending unusable 100000-lines patches for validation just before releases (haven’t checked this claim). It’s interesting to note that the same problem exists on the other side, with Mozilla releasing “security and stability” releases instead of just providing patches for the security bugs. My personal conclusion is that Iceweasel is really a good thing, and is quite unavoidable, even if it seems that the Debian/Mozilla collaboration could maybe have been better. Let’s advertise the use of Iceweasel, Epiphany, and other Web browsers! :-) Note : comments open for people willing to fix inaccuracies or provide references, not for a stupid childish flame-war like the one in the comment of this post. Please write your own blog entry and use a trackback if you want to provide a detailed answer! Updates:

14 October 2006

Russell Coker: more about Fedora

In a comment on a previous blog entry I was described as an active Fedora advocate, I don't think that is an accurate description. I advocate it to appropriate people, which is mostly non-programmers - but as I mentioned that means a larger proportion of the population than to whom I can advocate Debian. It's not that I'm trying to advocate Fedora, just that it fills a need for many people. I believe that the term Fedora advocate means someone has an objective of increasing the use and to use Fedora, I don't have such an objective. I am a Linux advocate, a Free Software advocate, and sometimes a Unix advocate (Unix meaning the entire family of Unix-like operating systems). Merely promoting something does not make you an advocate for it. I don't think of myself as a Debian advocate at this time, but as I am a Debian developer this may change.

It seems that the people who run the Fedora Planet think that my blog has suitable Fedora content, it's been added to that planet. Also the Fedora Planet appears to be running an older version of the Planet software as it has the same problem with my blog that Debian Planet had before the upgrade.

Now on the issue of gratis vs libre: As I am not a Red Hat employee I can't maintain a kernel-xen-nopae package and give it the same status as the kernel-xen package. Even when I was a Red Hat employee I couldn't have done that - it would require some amount of management approval. I believe that this fundamentally makes Fedora less of a libre distribution. There is no room in Fedora for someone who is an upstream developer and who just wants to maintain their own package. There is Fedora-Extras, but that has a second-class status. Only Red Hat employees can maintain packages in Fedora Core. This makes Fedora fundamentally less libre than Debian. I am not trying to suggest that Red Hat change things in this regard, I believe that Fedora is meeting all it's goals and that making Fedora as libre as Debian is not possible given the goals of making a profit on selling support of RHEL.

Chris made a good point. I also believe that MP3 codecs should not be in Debian/main. But I believe that people making mistakes about some issues is not a factor in judging the entire project. I believe that Debian is more libre although some bad decisions were made - largely due to lack of overall management. Fedora has hierarchical management, so when the legal team declares that some software can not be distributed then it gets removed without debate. I guess I could propose a GR to exclude MP3 codecs from main.

Also it should be noted that RHEL Extras has some of this software that is not in Fedora (RealPlayer for example). The Red Hat legal advice was that MP3 codecs need a license, so they ship a licensed version in their commercial distribution. This is the right thing to do for their customers (it's handy to have and I'm sure that they get a good deal by paying license fees for all their customers) and removing such things from Fedora is the right way to offer a gratis product without unreasonable legal liability.

Naturally Fedora is much more libre than any secret-source OS. Every user has the option of downloading the Fedora source and recompiling it as they wish. I could compile Fedora with a Xen kernel that runs on my hardware and with SE Linux policy that is more restrictive than that which Fedora currently has. I could build custom Fedora install CDs to install things the way I want (which I considered doing when I worked for Red Hat). But the liberty to fork a project does not compare to the liberty to join it, and the liberty to create your own packages in extras does not compare to the liberty to add your own packages that do things differently to the default package.

There are of course positive and negative aspects to this. I started work on SE Linux in Debian in 2001. In 2003 I joined Red Hat to work on SE Linux, in Red Hat I was not the only person dedicated to SE Linux work and other people spent part of their time working on it. The SE Linux work in Red Hat soon eclipsed that of Debian because there was management support. There was no possibility for a package maintainer to refuse to fix a bug that affected SE Linux simply because they didn't care for it. The positive side of this is that the SE Linux work proceeded quickly and efficiently. The negative side of this is that things which don't have management support don't appear in Fedora Core. Exim is a fine MTA but is not in Fedora Core. Some people think that AppArmor is a better option than SE Linux, they are wrong - but in Debian any developer has the option to add AppArmor support and neither I nor any other DD can prevent them. The libre nature of Debian means that as long as basic technical criteria are met DDs can add any package that they wish to the distribution.

These issues however are all related to people who are actively involved in Free Software development. For a typical Free Software user it often doesn't make much difference, until of course your favourite program doesn't get management approval to appear in Fedora Core. But the counter argument is that the quality of some of the >10,000 packages in Debian is not so high. You can install a Fedora Core package and have a reasonable expectation about how well it works, but Debian packages are sometimes rather experimental.

I also don't believe that Debian is a very functional Democracy. Some of the problems of Direct Democracy are demonstrated in Debian. In many ways it is more anarchistic, anarchy gives you liberty for good and bad. Maybe we should consider a Representative Democracy model for Debian.

Joey Hess: future of DWN

Martin "Joey" Schulze posted what seems to be his last issue of DWN at the end of September. Is this the end of its 8 year run? I founded Debian Weekly News in 1999 with the intent of helping Debian developers keep up with what was going on in Debian as the volume of the project grew beyond what could be easily followed by everyone in the mailing lists. That goal later grew to encompass also keeping users informed of what was going on in Debian. By the time I left VA, I was getting burnt out writing it. Besides, I was no longer able to do it on company time. (Yes, there is a delicious irony here.) So I passed it on to Joey, who's done a great job keeping it going over the years. I've considered taking over writing DWN again. However, it's not clear to me that DWN is still relevant enough to be worth the large amount of work it takes to maintain it. A lot of communication is done on Planet Debian, wikis and in other forms that were not around when DWN was started, and that may be a better way to keep up with what's going on in Debian than DWN. If there is a gap left by DWN, I'd feel more comfortable filling it by blogging something each week about what'd going on in Debian without necessarily trying to cover parts of the project that I'm not deeply involved in. (For example, I'm ignoring everything to do with debian-vote right now.) This approach seems more scalable, modern, and likely to take much less time. We could even have a special aggregator with feeds from other people doing the same.

13 October 2006

Uwe Hermann: Bluetooth and WLAN Security Issues

A while ago, in my Towards a moderately paranoid Debian laptop setup article, I said things like
Disconnect your laptop from any kinds of networks. Pull all ethernet cables. Disable WLAN (via hardware killswitch). Disable Bluetooth. Disable/remove Firewire, USB, serial, whatever.
What might sound either paranoid, stupid, or funny to many people, was actually not a joke. Especially wireless technologies should be a security concern to everybody, as any flaws in the technology can be exploited... well, wireless, i.e. from remote. Recent examples of such flaws have been reported in Apple AirPort drivers, Intel Centrino wireless drivers (for Windows), and just today new problems were announced in Toshiba's BlueTooth stack for Windows (which is used in many places, e.g. Dell computers, Sony Vaio, ASUS computers). Granted, so far none of the flaws I know about affect the Linux drivers, but it's just a matter of time until such problems are found there, too. Hence, if you don't currently use any of the technologies, disable them. Only enable them on-demand, then turn them off again. Also, keep up with recent kernel/driver updates which might fix security issues...

Erich Schubert: Google Summer of Code mentor summit

In four hours I'll be on the airplane to San Francisco via Paris. * erich puts a flower into his hair and starts singing Saturday there is the "Google Summer of Code mentor summit", where Google invited mentors from the participating organizations to Mountain View to discuss about the Summer of Code program, how it can be improved and what else Google can do for opensource. We're all very thankful to Google for offering this great program. It's meant as an opportunity to get more students interested into opensource development, and there are many success stories. Of course the program isn't perfect, and thats what the summit is for, improving it. And I'd really appreciate your feedback, your perception of the GSoC, of the students and the mentors. I've asked for feedback before, but I've received next to nothing so far. But there is quite a lot to discuss tomorrow. For example, many projects would fit to multiple organizations. I had proposed a SELinux integration project, but most of it would be reuseable by other distributions as well. There was a project which actually meant to integrate one mentoring organizations' project with an other mentoring organization. These could benefit from some "shared mentoring"; at the same time these project could server the prupose of increasing cooperation between organizations. I myself, for example, know rather little about Fedora, or the state of SELinux in Fedora. Still this is a point (well, if I still had the time to work much on SELinux that is) where I should definitely try to cooperate more with Fedora. Another proposal that came up and will be discussed is the "Summer of Content". It's not all about code. There is also documentation, graphics, sound, ... Why shouldn't a GSoC student be working on artwork or sound for a summer? The opensource/copyleft community definitely could use some support here, and we have rather few links to artists so far. So please send me your feedback. I won't be responding to mails for the next like 15+ hours since I'm travelling (maybe even 24h, if I'm busy with real life meetings), but I'm really interested in your ideas!

10 October 2006

Matthew Garrett

So it's been pointed out that since I'm no longer terribly involved in Debian, I possibly shouldn't be on Planet Debian nowadays. So unless there's any violent objections I'll ask to be removed at the end of the week - my RSS gunk is at http://mjg59.livejournal.com/data/rss for those who want to read my delightful prose in any case.

Anyway. Some token Debian-related content. Mozilla corp are unhappy with Debian providing a package called "firefox" unless every patch provided has been approved by Mozilla in advance (there's also some stuff about the logo, but that's basically a bizarre corner aspect of the same problem). I'm not going to argue against this on philosophical grounds - it's clear that that isn't going to change anybody's mind. Instead, let's compare this to some other major applications:On the Mozilla side of things, the closest I can really come up with is cdrecord. There's some pretty strong parallels (upstream being unhappy about various patches, requiring a sufficiently different work to have a different name), but the end result in the cdrecord case was that we ended up with an application that was poorly integrated with the rest of the Linux environment for the sake of remaining consistent across different operating systems.

I'm not saying that that's going to happen to Mozilla. But we've seen numerous cases where allowing vendors to distribute derived versions has encouraged development and testing of new ideas, and I think in most cases that's resulted in benefits to the upstream project. The fundamental problem with refusing to allow patches that cause significant deviations from upstream behaviour is that it makes it impossible for anyone to actually get things like UI experiments into the hands of users. With Gnome, if upstream don't like your idea you have the opportunity to prove them wrong and possibly change their mind. With Mozilla, if upstream don't like your idea you're pretty much screwed. Most distributions are going to be unhappy about losing the magic Firefox branding, so you're unlikely to sell them on it. And you're not even allowed to provide binaries or source on your website unless you've renamed it away from Firefox.

I think the Mozilla corporation are missing something here. We shouldn't be prizing cross-platform consistency over integration and innovation, and we certainly shouldn't be doing our utmost to make it difficult for people to experiment with code. There's a reason that cd writing under Linux has been sucky for years, and it's not because people lacked the technical ability to make it better.

[1] Ok, the X.org case is slightly confused by the fact that they are upstream now. But without the ability to fork under the same name, they wouldn't have been.

Evan Prodromou: 18 Vend miaire CCXV

I've been a fan of the Open Directory Project for a long time. I finally volunteered to become an editor about a month ago, and I just started editing my first category, wiki farms , today. I hope to get the category up to good shape in the next few days. I've now got an ODP profile, too. tags:

Hudson Maj, Amita June and I went down to wt:Hudson (New York) over the weekend for the wedding reception of our friends Morgan and Kate. The trip down was fantastic -- the colors in the wt:Adirondacks were really amazing, just hitting their peak. Amita June had a good drive, too: she got to look around a lot, listened to some music, and had a nap of about an hour and a half. Hudson was a cute town, but not cutesy like other parts of the wt:Hudson Valley can be. The town is small -- 4-5 streets wide -- with big brick buildings lining the main street down to a promenade overlooking the Hudson River. There are a few gourmet restaurants and a disproportionate number of art galleries and antique stores, but it doesn't feel like the locals have been pushed out of their town... yet. We stayed at the St. Charles Hotel, as arranged by Kate's stepmom for most of the guests. It was functional and clean but otherwise unexceptional. There was a bar and a restaurant downstairs, and the hotel itself is just opposite a nice little park. Sunday morning we had breakfast at the Earth Kitchen organic market; I had a bowl of granola and fruit, Maj had a huge plate of huevos rancheros, and AJ ate whatever she could get off our plates. We walked around town and down to the waterfront, where we got a panoramic view for miles up and down the Hudson Valley. With the leaves nearing their height of color, it was an awe-inspiring view. We took a late lunch at Mexican Radio, a branch of a restaurant by the same name in Manhattan. It had good quality California-style Mexican food, with a few fusion dishes (like "Mexican spring rolls") that were probably overdoing it a bit. The margaritas were top-notch, and they have a tequila sampler option with three excellent tequilas for... $125! You won't normally lose that much money on three shots of tequila unless you pass out in the gutter in wt:Nuevo Laredo. The reception itself was at the Ca' Mea restaurant, right next to the historic Hudson Opera House. Kate and Morgan were in good form, playing goth-y music from their early days, and family and friends had a good time too. We all probably ate too much, and Maj and I both had hangovers the next morning. Amita June, however, had an excellent time running around the party and dancing with the bride. She was made for weddings. The drive home the next day was less than optimal. We did brunch in the St. Charles's restaurant, Bridges, and then stopped by the house of Kate's dad and stepmom for an afternoon get-together. They have a really nice Victorian house on a hill above town that overlooks the valley. We had to leave after only a few minutes, though, since we'd been lucky enough to get guest-listed for the Massive Attack show in Montreal that night. Trouble hit us as we were coming up the 87, though. First, the baby refused to sleep, getting more and more hysterical the longer she went awake. By 4:30PM, we'd had to stop so many times to soothe her that we were starting to get worried about the time. Then, we hit a detour on the interstate -- a huge accident had happened going through the mountains. We got into a sluggish line of cars wending its way along highway 9, and by the time we were back on the interstate we knew we were going to be late. We decided that luck was against our going to see MA, so we called and canceled our baby-sitter and sent email to our friend DJ Ghostbeard who'd asked us to come to the show (although we didn't get a call through... his voicemail box was full). We stopped at Geoffrey's Pub in wt:Plattsburgh for a late dinner of blackened salmon, broiled seafood and mashed potatoes, and then got back on the road. ...and straight into a 2-1/2-hour line at the Canadian border. This weekend was Canadian Thanksgiving, and apparently a lot of people took the opportunity to dip down into the states for a last bit of outdoorsmanship before the winter frosts settled in. Amita June, already a little frantic from not sleeping, went completely ballistic, and although we managed to keep her mellow most of the time, 2 hours in a line of cars with a crying baby is a little bit much for anyone. We didn't get back to Montreal until nearly midnight. It was great to get home, finally, and as usual travel's made me appreciate staying in one place. The Gazette this morning says the Massive Attack show was excellent, but I'm glad we didn't try to make it -- coming in 4 hours late is just too much. We're off to wt:Halifax next weekend for our wedding anniversary, and hopefully we'll be back into travel mode by then. tags:

Destinyland Dave Cassel has an excellent list of the 100 Greatest Internet Moments. A great compendium of Stuff What Happened over the last 10 years in cyberland. I think Dave's one of the best Internet culture observers out there. I'm glad to see he's got a new podcast, Destinyland, in which he tears apart the weird media culture we live in. Example: the crazy spiral of Dana Plato. Example: Schoolhouse Rock: Behind the music. Example: Dark side of the Hampster Dance. Good stuff. tags:

9 October 2006

Biella Coleman: Trust in the Law

Trust is on the top on my list of topics of inquiry and I have made it one of my main themes in my writings on Debian. Forbes recently published a small piece on the The Economics of Trust, using trust as an example to explain why Somalias economy barely exists while many in the west, notably the US, are thriving. A little reductive but he has something there because indeed, the level of trust that consumers, investors, and everyone else in the chain has to have to make “it” happen is enormous. However, I am surprised he never mentiones the law in name, and contract law to be specific. He sort of subsumes things under formal mechanisms of trust, but it seems like without the law, there would be no trust… in which case, do we still call it trust? or trust in the law that is the condition of possibility for other mechanisms, which do exist. This topic of trust and accountability in capitalism is something that Weber actually spent a fair bit of time in General Economic History for those interested in such topics.

8 October 2006

Erich Schubert: On Google Reader

First of all, I havn't really used Google reader yet. I think I tried it a long long time ago once, and they apparently did a UI redesign. However, it doesn't work for me anymoe, all I get is "Loading..." (and a Javascript error). I'm using liferea, and I'm quite happy with it. Some of the things I do like: Because of these I can't imagine using an online reader. P.S. If you fold your blog entries or don't do full-text RSS, I likely won't read your entries, either. It doesn't work with offline reading habits.

Ian Murdock: Google Reader gets it right

Google Reader relaunched a few weeks ago, and for the first time since my initial foray into blogging with Radio Userland in 2003, I’m actually enjoying using an RSS reader. Why? River of news. Most feed readers inexplicably model the email workflow, presenting feeds like folders and feed items like messages. Given the state of most peoples’ inboxes, why on earth would you model email when you’re writing one of these things? Google Reader does river of news right. Simply click on “All items” and scroll through the items with the mouse wheel, clicking on the interesting stories (or reading them inline when the feed is full text). Google Reader takes care of marking the items read as they scroll past. Automatically. The praise doesn’t stop there. There are handy keyboard shortcuts (”n” for next item, “r” to refresh, etc.). Performance is excellent, as feed items are loaded on demand using AJAXy techniques. The look and feel is clean and simple, reminiscent of Gmail, down to easy to read timestamps like “9:53 AM (7 minutes ago)”; and, also like Gmail, there’s a mobile version. Intriguingly, you can sort by “auto” in addition to by newest, which presumably applies some sort of relevance algorithm to the feed items. However, it isn’t clear how it determines relevance (does it track my clicks as I scroll through the feeds, examine my broader search history, what?). Google Reader is a good platform citizen too. There’s a gadget you can add to your personalized Google home page, and gadgets, in case you missed it, are becoming full fledged web components as of last week. Oh, there’s an API too. Finally, in concert with Mozilla Firefox 2, subscribing to feeds finally no longer involves configuring a bookmarklet or, worse, the complex gymnastics of right click/copy link location/go to the appropriate URL/paste/subscribe. With Firefox 2, you can configure the feed subscriber to use Google Reader. As a result, you can now click on the feed icon in the address bar to subscribe to the site’s feed. In most cases, you can even click on a link to an RSS/Atom feed, for those sites that don’t have autodiscovery configured properly. My only complaint here is that it doesn’t remember that I want to subscribe in Google Reader; rather, it asks whether I want to “Add to Google Homepage” or “Add to Google Reader” every time. Ideally, it would show me a preview of the feed instead. I’ve seen Google Reader do that before, so perhaps it’s just a matter of configuring it to go to a different URL, though I’m not sure how to do that. So, what’s not to like here? As with most Google products, it’s not particularly well integrated with the Google platform. Indeed, in that particular post, I complained that there were three different ways of creating a bookmark in the Google platform. Well, there now appear to be four. If all of these mechanisms were integrated, that would be enormously powerful. See something interesting in the Google Reader? Click on the star and, optionally, add tags. See something interesting on the search results page? Ditto. See something interesting on a random webpage? Pull down a menu on the Google Toolbar and do the same thing that way. Want to add free form notes to any of the above bookmarks? Pop into Google Notebook. Naturally, all of these actions should result in the bookmarks/tags/notes/etc. being added to a single stream that can be shared with other users, with all of the resulting social network functionality. Etc. etc. etc. Sigh. I guess I have to be patient a little bit longer. Fortunately, Google sees the problem and is finally doing something about it.

Biella Coleman: My Reading

So people may be wondering, How does Biella pass her time in the vast, desolate Canadian north? Thankfully there are many things to do in Edmonton proper, but I have delved quite a bit into reading so I thought I would take a break and give small reviews of the books I have read or am reading as they are all quite good. I am trying to be more systematic about my reading habits so I am back to using citeulike. I am adding anything new I read and then as I go back to I have already read (for articles), I am adding them to the list also. I hope this pays off in the future! I started the reading bash with a book that was recommended to me over a year ago while I was still in Chicago: The Fugitive’s Property: Law and the Poetics of Personhood as it deals with the bread and butter of my own work, intellectual property, liberalism, market capitalism, and American history. I found the introduction enlivening and was sufficiently interested to continue on. I think there is not a lot of innovative work in the field of intellectual property (only because it has been covered very well) and to bring together slavery/the fugitive person and intellectual property under the same analytical lens, seems productive. Best looks at how the legal treatment of the slave and that of IP, hold striking parallels for their highly fugitive (formal) nature, driven and intensified by the legal/market framework that makes personhood into property. There is a lot of good stuff in there (including a fantastic discussion on legal positivism) but in the end, the labor it took to sift through some really obtuse prose was too much for me. I can’t remember the last time I languished under the heavy weight of language that was far too ornate and under sentences that just lacked clarity. This was compounded by the fact that he assumed you knew a fair bit about slave history, which I did not. My drive also escaped me and while I hope to return to it later, I took a break and turned to more readbale material. After such heavy linguistic ornateness, I needed an antidote, QUICK, and I knew exactly where to go: William Sewell and his book I had on my shelf also nearly for a year: The Logics of History. Along with being a first rate historian he is like that black instrument popularized in the 1980s by the likes of Herbie Hancock, and Brian Eno, he is a synthesizer with an amazing ability to write clearly. Being the synthesizer that he is, he is skilled at connecting the dots between various theoretical topics like event, structure, and agency, making the theoretical implications so crystal clear you feel happy to have entered into a field (the social sciences that is) that feels awfully arcane and pointless at times. I left Stehpen Best, which was like leaving a cluttered medieval castle and into a simply decorated room filled nothing with good theoretical feng shui (I think about writing in spatial terms more than ever). He just makes reading fun, even when the topics can be less than enthralling. Many of the essays were published previously and I had read a number of them, such as his famous essay on structure and agency. What I appreciated along with the great writing, was that he takes serious the question of plurality of social life within the net of various social, economic, political determinants. So while he assumes the existence of structure (and turns Marshall Sahlins to establish), he also is quick to show that structure, like a cultural system, can only act as partial (and unexpected determinants of social life) because of the existence and presence of events (which is really Sahlins great masterful point) but more importantly because of the plurality of structures… This was perhaps on the the central motifs in my dissertation; while I placed hacking within the cultural lineage of liberalism, in no way is this the only cultural system that hackers operate through and with; they move through a cultural domain more intrinsic to their own praxis, not to mention other systems of value that reverberate more widely among the digerati… And it is this movement between social positions that allows for forms of reflexivity and social change. I primarily used Bakhtin to make this point but now I got Sewell to add to this mix. Here is a nice passage from the book that makes this point:
I would argue that a multiple conception of structures would make subjects cultural creativity easier to explain. If the cultural structures by which subjectivities are formed are multiple, then so are the subjectivities… Because persons, symbols, and objects of cultural reference overlap between structural realms, structurally generated rules, emotions, categories, and senses of self can potentially be transposed from one situation to another. Indeed, if actors commonly have the experience of negotiating and renegotiating the relationships between noncongruent cultural structures, it follows they should have some intellectual distance on the structural categories themselves, that they should be able to view one set of cultural categories from the point of view of others that are differently organized, to compare and critizise categories and categorical logics, to work out ways of harmonization or odering the seemingly contradictory demands of different cultural schemes. A multiple conception of structure, consequently makes human creativity and reflection an integral element in the theory of history, not a philosophically prior metaphysical assumption. p. 213
And here is a more engaged review that is a little more critical than my very short comments. As part of a reading group organized by my tireless supervisor, I am also reading The Cultural Locations of Disability written by two of the most prolific scholars in the field, Sharon Snyder and David Mitchell. Since I am a novice in field it is hard for me to judge the two chapters we have so far read but it is a total total total treat reading a book slowly with a group of other folks from a vast range of departments. So far I appreciate the larger arguments presented in the introduction. For example, they point to two broad categories—capitalism and modernity/enlightenment– as driving forces in a new wave of obsession with the disabled. So while capitalism’s insistence on measuring the worth of humans through an abstract and actual ability to labor, marginalizes those who cannot offer their constant labor power (and makes them an “odd” cultural object), modernity–in its desire to march forward to the mysterious plane of progress, offers a technological promise to eradicate what it designates as deviant or primitive. As they nicely sum up: In a culture that endlessly assures itself that it is on the verge of conquering Nature once and for all, along with its own primitive instincts and the persistent domains of have-nots, disability is referenced with respect to these idealized visions. As a vector of human variability, disabled bodies both represent a throwback to human prehistory and serve as the barometer of a future without deviancy. p. 31 I, think, however, they should have also included some discussion of liberalism, which in many ways, was the legal and philosophical engine that helped to naturalize capitalism not to mention it also offered a vision of person, in which self-development, expression, and discrete autonomy was deeply cherished. Seen in this liberal light, disability becomes also a type of tragedy that can be resolved though new technological interventions they discuss under the guise of modernity. I have just started Michelle Murphy’s Sick Building Syndrome and the Problem of Uncertainty: Environmental Politics, Technoscience, and Women Workers, which promises to be quite a tour de force into the contentious politics of uncertainty and the play of perceptibility and imperceptibility that surround one of many many syndromes sick building syndrome that now are part and parcel of the medical and patient advocacy field. Along with this I read and finished Andrew Lakoff’s Pharmaceutical Reason: Knowledge and Value in Global Psychiatry, which will make for great teaching, and has one of the nicest discussions on the way in which psychiatry’s insecure status among the other medical science was one of the driving forces toward embracing the new scientism of the 1980s that coincided with new more general neoliberal trends. Another nice move about the ethnography is that he was able to clarify some of the trends and rationalities of American and European psychiatry by examining how it was received and resisted among more psychoanalytical Argentinian therapists. Very classicial anthropological lens in that sesne. Finally I am in the middle of Play Money: Or, How I Quit My Day Job and Made Millions Trading Virtual Loop and I will say more about it when I am done, which should be soon as I am tearing through it evern night. I have been waiting for this book for a long while now because Dibbell is part of that trinity (Steven Levy, Bruce Sterling, Julian Dibbell) that offers some of the best writing on hackers, the internet, and virtual worlds. And this book continues in that tradition of providing a fantastic read, a vivid ethnographic picture of the topic at hand, along with key insights into the nature of economies, money, and plau within (and outside of) virtual landscapes. What I respect about Julian Dibbell is that he took a long time to get this book out. He started the research in 2003 and then spent a few years writing up. I think there is a lot of pressure to get any material or book on “virtual whatever” out there as quick as possible but for the most part I think that is a mistake. You need to let these things brew a long while or else they won’t acquire that taste of a finished product.

Andree Leidenfrost: Debian Voting Galore

I've crawled out from underneath my Mondo Rescue stone and looked in bewilderment at the various vote messages in my inbox. (It's not quite as bad, I've followed things to some detail passively on private and planet.)

The main questions seem to be:
  • Is it good or bad to collect money to pay people for getting specific tasks done in Debian? Does involvement of the DPL in such an initiative constitute a conflict of interest?
Here is how I've voted and why:

a65763d3-b1e2-4530-8ff8-aa5915274eb4
[ 1 ] Choice 1: Re-affirm DPL, wish success to unofficial Dunc Tank
[ 2 ] Choice 2: Re-affirm DPL, do not endorse nor support his other projects
[ ] Choice 3: Further discussion

49a98df6-2bd4-40c8-a559-7e15212dbd26
[ ] Choice 1: Recall the project leader
[ 1 ] Choice 2: Further discussion

I think AJ is trying to improve things in Debian and that Dunc Tank is one attempt to do so. I believe it is a worthwhile attempt and can understand that he wants to be involved. While I also understand the concerns raised by other people, I believe that only time will tell whether Dunc Tank is in fact good or bad for Debian (I hope it's good). As far as the conflict of interest issue goes, I think it's less than ideal but the smaller evil to keep AJ as DPL whilst he's involved with Dunc Tank. I don't think AJ should run again if he stays involved in Dunc Tank as he is at the moment. I think that we need to consider integrating Dunc Tank into Debian if it is still alive and kicking in 12 months time. (Or to set up something similar as part of the project.)

c2d43675-9efa-4809-a4aa-af042b62786e
[ 1 ] Choice 1: Release Etch even with kernel firmware issues
[ 2 ] Choice 2: Special exception to DFSG2 for firmware as long as required [3:1]
[ ] Choice 3: Further discussion

22fc4edd-1f6c-454f-b204-6aa0bad0ce1d
[ ] Choice 1: DFSG #2 applies to all programmatic works
[ 1 ] Choice 2: Further discussion

I believe that we should indeed release Etch as planned even if that means shipping a number of firmware blobs. I do not think that an ongoing exception is appropriate here. If this is still not resolved by the time we want to release Etch+1, let's have an other GR.

I am not sure what "program" really means in DFSG #2 - I've always taken it to mean the software, documentation, fonts and artwork that we ship as part of Debian. It likely has to comprise more than that, but I am convinced there have to be some exceptions:
  • It defeats the purpose and very nature to modify licence texts. If people can change a licence at will, there is not much point having one in the first place.
  • It equally defeats the purpose to modify logos (and thus their representations as files of whatever format). Logos allow users to recognise more easily what content is available. It does not make sense to allow modification or use in a different context of such a logo as it would then be more confusing than helpful.*
I believe that these are just two examples of potentially many where 'free' versus 'non-free' are inadequate categories to think in.

Finally, the DFSG are part of the Social Contract and not the other way round. I like this because I value doing the best for our users higher than some rules. The DFSG exist to empower our users - I don't believe that removing firmware blobs from the kernel serves this purpose. That said, we should by all means strive towards free firmware, but I view this as more of an incremental, ongoing task of convincing vendors over time.

* I believe for example that the dispute over Firefox would be best resolved by Debian using the Firefox logo (and name) and the Mozilla folks dropping there requirement for patch review.

7 October 2006

Ian Murdock: Pot. Kettle. Black.

Steven Vaughan-Nichols: “The Debian community sees Mozilla as being unreasonable about its trademarks. I find that more than a little curious, since Debian has long been just as protective and possessive of its own Debian name and logo. For example, the DCC Alliance, which is made up of nothing but Debian companies and was led by the founder of Debian, was forced to drop Debian from its name because of the Debian community’s hostility.”

6 October 2006

Jordi Mallach: Debian etch will ship with GNOME 2.14

This is already old news, but I haven't commented here yet. We already hinted this possibility in my previous blog entry on this topic, but sometime last week, we made it official. After speaking to some people upstream, we got the impression that the GTK situation was way too risky to do a GTK 2.10 migration, with no hints on when the file selector problems would be solved. As of today, and two GTK 2.10 releases later, not all of the issues appear to have been resolved in this branch, so we may have chosen the right path. So, with this information in our hands, we described the whole situation to the release managers, explaining what the options were, and they, of course, had no doubt on what was better for etch. The last two months before the release, we'll try to polish the last few bits that we'd like to improve in the current 2.14 packages. For example, Joss just made a change to the session manager, to make it possible to save the user's session easily, a feature which was present until GNOME 2.12, then removed in 2.14 with apparently no sane replacement of saving sessions available for the user. I must admit I'm a bit disappointed about not being to ship all the work we've been doing with GNOME 2.16 in experimental, although I believe it was the right choice. If the etch release is delayed for some major reason, and let's hope it's not, that might open a window to see a transition going on, if the fixes are finally in and we consider our packages release quality. If not, we're sorry, but we won't be able to sell the latest GNOME version argument in our release PR. ;) The Debian GNOME team has already been talking about doing a semi-official 2.16 backport for etch though, so people can use stable with the current GNOME, at least for a few months. We'll see how it goes...

4 October 2006

Evan Prodromou: 12 Vend miaire CCXV

Hey, somebody used a photo I took of the Papineau mural in Papineau metro station in a discussion of the prison Pied-du-Courant. They even gave me proper attribution, per the license under which the photo was published. As an American I have a shamefully bad understanding of Canadian history. Example: when I first moved to Montreal, I had to get my local land-line phone service set up. When I was asked for my address (in English -- I didn't even try doing this stuff in French back then), I answered: "Avenue Papineau. That's P-A-P-I-N--" the operator cut me off. "I know perfectly well how to spell 'Papineau', sir," he said, icily. Oops. I'm trying to get caught up. I've been reading a ton of wp:Pierre Berton books, but I still don't have the whole story as integrated into my own mental processes the way I know, say, American history almost instinctively. Like, even though I know the story, I continue to boggle that wp:Louis Riel keeps popping up in various apparently unconnected historical contexts and era. It's like, "Wha? Louis Riel again? Didn't they shoot him four or five chapters ago? Why is he still here?" I guess it just takes time. Or maybe it's something I'm never going to understand, like why there were two teams called "Roughriders" in the CFL for so long. I dunno. tags:

Talk about your busy days Busy, busy day today. Alain Desilets, a researcher at the National Research Council and a really smart person when it comes to wiki, came to Montreal today for Wiki Wednesday. We had lunch with Alain and fellow researcher Julie at nearby Ty Breiz restaurant, a neighborhood landmark that makes fine crepes and cider and good garlicky salads. We talked about improving wiki interfaces to make it easier to translate between multiple language versions of a page (like you see on Wikipedia and Wikitravel), and came up with some interesting solutions. Then it was off to Wiki Wednesday proper, at which Alain presented his translation projects and also some collaborative fiction ideas for children. Very cool stuff! It was a real celebrity event: Sunir Shah of MeatballWiki, Sebastien Paquet of SocialText, Marc Laporte of Tiki CMS/Groupware, Anne and Antoine, organizing the RoCoCo 2007 event, and lots of other folks too. Anne and Antoine also presented their brilliant image-only wiki, Wikigraphe. It lets people upload images as a replacement for pages, then build "hotspots" on the images that link to other pages -- which are in themselves images. It's a destruction of the tyranny of text in the wiki world -- and fun to watch. Sylvain Carle compared it to drawball, but I think they're different. Much followup talk on RoCoCo 2007. It's going to be an exciting event -- so glad to have wiki friends around the world coming here, to my favorite city. Lots to do between now and May, but I think we can get it done and have a fantastic wiki (and wiki-like) event. Wiki Wednesdays are such excellent events -- kudos to Seb Paquet for organizing them in Montreal, and also to SocialText for such a good idea, and Robin Millette and gang for hosting. tags:

CC Salon Montreal On top of that, we had the Creative Commons Salon Montreal tonight at Am re de boire on rue St. Denis. The Salon is developing internationally as a way for CC-related people to interact, chat, and have fun in cities around the world, and Montreal has too many CC folks to be left out. Tina Pipers, co-chair of Creative Commons Canada, is on the faculty at McGill, so we're lucky to have such a heavy hitter in the area to chat with us. (Also, I found out tonight she's Greek! Good for us.) Tonight was expecially great since Maj and I talked about Wikitravel and our new project, Crossroads, to create Open Content travel opinion, stories, blogs, photos, etc. It's just getting off the ground, but it was great to share our vision with some people who really understand the idea of content sharing and an information commons. The discussion after our talk was great. I couldn't drag myself to YULblog, though, after 6 hours of talking... I had wanted to go to get people interested in BarCampMontreal, but Sylvain (one of the event organizers) was already going, so I felt justified in sitting it out. But when am I going to get to another Yulblog? I just don't know. tags:

Searls ha ha Searls's 4th Law: No matter what car you want to rent, what you'll get is a Chevy Cavalier. Man, I love the wp:Chevrolet Cavalier. It's a fun car to drive, and it just says "rental car". Which mean, y'know, "vacation" and "distant lands" and "irresponsibility". How can you not love that car? Not to mention that someone has to straighten out Doc Searls on Elements of Style Rule #1: Form the possessive singular of nouns with 's. This includes singular names that end with s... like "Searls". There are a few exceptions for ancient names ending in -is/-us/-es, but those are few. To paraphrase: I knew Achilles; I served with Achilles; Doc Searls, you are no Achilles. tags:

UFO Beliefs Hey! I'm back on Technorati. Rockin'! After like 3 months complaining to their customer service Web form and getting 0 (= zero) response, I finally canceled my blog claim and started a new one. The software picked up on my site right away. Problem solved! It would have been nice to hear, you know, one tiny peep out of Technorati about my 8-10 bug reports, but I guess they're pretty busy. tags:

3 October 2006

Lars Wirzenius: Debian: Joey Schulze is wrong

Martin "Joey" Schulze is interpreting my decision to spend some less time on Debian as being due to dunc-tank. He's wrong. Joey, you're spreading false rumors. You could easily have checked the facts with me, but you chose not to. That is malicious. Kindly do not ever use my name to further your hate campaigns, thank you. I'm reducing time spent on Debian rather than reducing time spent on other things so I could still do Debian things. One of the reasons for this is that it seems to me that a number of very vocal people in the project have collectively gone insane over the past few months. As an example, proposing a GR as a reaction to dunc-tank was so much out of proportion that I can't understand how those who supported are capable of acting in a constructive manner at all. Either that or they seriously need a life. I have some years ago developed an aversion to conflict. Rather than butting my head with insane people, I'll withdraw from mailing lists and reduce my participation in the project to maintaining the package that I care most about. That's right, Joey, dunc-tank didn't drive me to this. You did. I don't know if dunc-tank is a good thing or not, in the long run. I think it's a worthwhile experiment, and its future should be decided when the experiment has been done. Another reason to reduce time spent on Debian is that I'm looking into starting a business. That can be quite time consuming.

2 October 2006

Erich Schubert: Release asynchronity

When release draws near, more and more difficult decisions arise. Like: should I still upgrade the package to a newer upstream version? Enigma is a great puzzle game, very similar to Oxyd. Back when still using my trusty old Atari ST, I was a fan of oxyd. Debian unstable currenlty has Enigma 0.92, the latest released version. Experimental contains recent SVN snapshots of the game. Version 0.92 was released in 2005, and there have been huge improvements to Enigma in the mean time, including a new level form (XML-based, while the levels used to be lua scripts), a reorganization of the levels into level packs with increasing difficulty, tons of new levels and graphics for 1024x768. While the new versions are running quite stable, and a new release is expected for end of the year, it will probably be not on time for etch. So should I upload a SVN checkout to unstable (and eventuall etch) - I didn't receive bug reports for the experimental version so far, and enigma has shown before to be of high code quality - or stay with the latest released version? "Life" would be easier if enigma released a new version just in time for etch. ;-) Just kidding. I'd certainly prefer the new version; and while there are some known issues with it (a conflict between C++ exception handling and lua when nesting), these might as well apply to the current version. (For example, the screensaver tends to turn on while playing enigma, but upstream said this is actually a SDL issue, and it should apply to both versions) Maybe some people can test the enigma package from experimental and send me feedback reports. But don't blame me if you lose valueable hours of sleeping time by playing enigma. It can be quite addictive.

Erich Schubert: SELinux and package install scripts

The horror of providing full SELinux support out of the box are install scripts. Installing files of a package is rather easy. Install them, relabel them. This can be added to the package manager. (And I believe dpkg already does that). However, package install scripts are becoming more and more complex, and they aren't SELinux aware. And there is a lot of stuff that can go wrong here. For example, a package might want to generate a configuration file for the service you just installed. If this configuration file is to have the same context as the directory containing the configuration file, there won't be a problem - but if it's to have a different context, the generated file will be incorrectly labeled. I see two basic solutions to this: Any other smart solution for these problems? Sometimes I wish we could do without turing-complete postinst scripts...

Andrew Pollock: [opinion] On Linux Australia futures

I've been a bit busy lately, so I've only now skimmed through my linux-aus backlog, as well has had time to put some thoughts together on the whole AUUG/LA thing. I will point out that I had a similar rant back in July last year, and a lot of what I said then still holds true. So one of the problems is we seem to have too many organisations. OSIA, AUUG, LA, SAGE-AU, ACS, to name a few. They've all got a bit of overlap. They've all got different names (well duh) that imply different things. So AUUG, as the Australian Unix Users Group, is losing is relevance. So much so, that the "About AUUG" page doesn't even discuss what the hell the acronym stands for. Somewhere along the line, they've adopting the tag line of "the Organisation for Unix, Linux and Open Source professionals". So they're clearing still trying to remain a "professional" body. As is SAGE-AU. Clearly with a name like the System Administrator's Guild of Australia, it's obvious what demographic this organisation is for. Now of course a lot this organisation's members are going to be administering Linux. You could also argue they're using it as well. SAGE-AU is operating-system agnostic though, and doesn't really get all community about the operating systems its members administer. Which leads us to Linux Australia. An organisation that (at least in my opinion) that is more about the community around the operating system than anything else. And in this case, by operating system, I'm talking about a lot more than just the kernel. OSIA, on the other hand, is an organisation I haven't heard a lot about, and know even less about. The name though, pretty clearly suggests what they're on about. If OSIA didn't look like it was more about corporate members than individuals, I'd be saying that this is where a large chunk of AUUG members should go, if AUUG were to fold. It does leave a certain demographic out in the cold: ISVs that make closed-source software for Unix and Linux. Since, for example, CheckPoint seem to be sponsoring the AUUG conference, they obviously feel that they have some sort of affinity with the organisation. Finally, there's ACS. Another organisation I don't know a lot about. I would think that maybe this could be another potential destination for AUUG members if it were to fold. Back to Linux Australia, and whether that name is the best thing for the organisation. I personally think it is not. Linux Australia is way more about F/LOSS evangelisation and the community that exists around that, than anything else. To a lesser degree, it tries to act as the "mother LUG" of all the Linux User Groups around the country, but given the loose structure of the LUGs, this is more of an assumed position than anything else. So what to call LA instead? Steal AUUG's tag line? "The Australian Linux and Open Source Community Group (ALOSCG)"? "The Australian Linux and Free Software Community Organisation (ALFSCO)"? Hmm, the second one could be mutated in "Alfresco". Cute. Funnily enough, the same arguments apply to renaming linux.conf.au, however I'm not in favour of that. I agree with what Maddog said on the linux-aus list, about it being easier for sponsors to identify with something more specific like "Linux" than something more amorphous like "Free and Open Source software". I also think linux.conf.au has a pretty strong brand associated with it. Finally, I want to bang the drum for organisational change. There was some discussion about membership tiers. I think this is a good idea. I think having paid members (and some member services) would be good. It would provide Linux Australia with an additional revenue stream, and it would allow it to provide something to its members. If there was a membership structure like "student" (which would be free), "associate" (paid, but cheap) and "professional" (paid, but slightly more expensive), you could allow all categories to vote, but give the paid members some additional services like a sticky email address, dynamic DNS hostname, maybe if LA got direct sponsors, the sponsor organisations could provide discounts to members like what SAGE-AU does. I also think that if LA were to employ a full or part-time administrative person (like SAGE-AU did until recently) would also be beneficial. This person could do heaps of administrative stuff and coordination for the organisation, as well as be a resource for the linux.conf.au organisers, and be cheaper than having to pay an Executive President or something like that. it would allow for the organisation to go to the next level, and be a little less amorphous and have a tangible existence.

Next.

Previous.