Search Results: "pm"

25 October 2006

Sven Mueller: New to planet.debian.org

Since I just started my blog and added it to planet.d.o, I thought I should introduce myself a little. I’m in my mid 30s (ouch), working as a sys/net admin (Linux based, mostly Debian these days) in a nice little company. I first encountered Linux back in the 1990s, before the 1.0 kernel got released. Back then, I used Slackware (which, surprisingly, seems to still be around), later switching to Mandrake. About 5 years ago, I got introduced to Debian and immediately liked it for the ease and clearness of administrating it (apt+dpkg+dselect was so much better than rpm used to be at that time). For about two years now, I’m contributing to Debian, including some involvement in the earliest pre-implementation phases of the volatile repository (mainly advocating a few ideas that actually led to it’s implementation, BTW thanks to those who did the work in the end), some small packages I maintain and involvement in some small teams. Mainly the cyrus-imapd packaging team, but also (to a much smaller degree) in the cyrus-sasl, initscripts-ng and (extremely little, since noone bothered to add me to the alioth group for it yet) the php packaging teams.
Letting computers aside, my interests are quite diverse, they range from wheelchair-basketball to books (SciFi and Fantasy mainly) and RC helicopters, among others.
More interesting posts will probably follow later.

Evan Prodromou: 3 Brumaire CCXV

I&aposve been dawdling and delaying writing about our trip to wt:Halifax (Nova Scotia) two weeks ago for some reason, but I&aposm bound and determined to get some info down on, uh, electrons about it right now.

Hella facts about Halifax We flew out of Trudeau airport eeeeearly on a Friday morning; I&aposd shopped a bit on the Air Canada site and got $99 each-way tickets from Montreal on their wp:Air Canada Tango program, but they required that we be on the 7:50AM flight. Air Canada used to be one of my favorite airlines, but they have been getting continuously disproportionately high prices and conversely worse amenities (pillows and blankets now cost extra, thank you very much). Discount flights in Canada are pretty sparse these days, with the collapse of Jetsgo in 2005 and the recent repositioning of CanJet for charters only. So, you just have to take what you can get. The flight to Halifax was quick and painless; Amita June slept most of the way there. The airport there is pretty small (yay small airports), so we buzzed through baggage claim. Cabs into town were a pricey flat-fee of $52, which got our hackles up, so instead we waited half an hour and took the Airporter shuttle ($16/person) into Halifax proper. We got to see a lot of the Nova Scotia countryside from the shuttle -- lots of leaves turning and conifer forests. We had reservations at the pretty and historic Lord Nelson Hotel, well away from the waterfront, but still in the downtown area, near Dalhousie University. The Lord Nelson is in the "Splurge" section of Halifax hotels on Wikitravel, but since this trip was for my birthday and our 2nd wedding anniversary I thought it&aposd be nice to stay there for one of the 4 nights we were in town. But when I called to make a reservation, I was able to get a very competitive rate, mostly due to a healthy 40% CAA discount, and I booked us for all 4 nights. I&aposd asked for early check-in, but our room wasn&apost ready at noon, so we tried the Lord Nelson Pub for lunch and a beer. The food was tasty and the atmosphere was, uh, pubby. We pawed through the stack of tourist-info documentation that we&aposd picked up at the info desk at the airport, then went up to our big and well-lit room for a mid-afternoon nap. Yes, all three of us. When we woke up, Maj and Amita June went for a walk across the street to the pretty wp:Halifax Public Gardens. It&aposs a very nice Victorian-era public park with disturbingly large geese roaming about. When they got back, the three of us headed down to the waterfront for an early dinner. Halifax&aposs streets are very steep -- they virtually plummet into the water. But we walked straight down to Water Street then meandered along looking at the sights. Our intention was to eat at the Privateer&aposs Warehouse, a building with a bar and two restaurants stacked on top of each other. It&aposs part of the Historic Properties on Upper Water Street, a collection of restored buildings with shopping and food. But the Warehouse turned out to be too rambunctious for us on a Friday night, so we instead went around the corner to Salty&aposs for a slightly more sedate meal on the water. We had good food; Maj had some very nice crab cakes and I took on a large seafood salad. Amita June chomped on really tasty fish and chips. The walk back up the hill was a bit tough, so we stopped in the Rogue&aposs Roost brewpub on the way home for a little strengthener. Unfortunately, as it was after 8:30PM, the baby wasn&apost allowed into the pub. So, we had to leave her tied to a parking meter while we had a... just kidding. We retired to bed after a long day, all three. tags:

California Dreamin&apos All the leaves are brown, red, orange, chartreuse and saffron here in Montreal, yet we&aposre off to wt:San Francisco tomorrow morning (early) to visit friends and family. I love going to see my parents and brothers and sister-in-law and nieces, but I also like going back to see the wt:Bay Area (California). It hasn&apost always been like this. It used to be that when I went back, it felt like I&aposd never left, and that the life that we&aposve made here in Quebec was just a story I told myself. San Francisco seemed real; Montreal seemed distant. San Francisco was where I was supposed to be; Montreal was where I stubbornly and irrationally insisted on staying. (The fact that I stayed in a room in my parents&apos house didn&apost help with the stepping-backwards feeling.) But it&aposs been a few years, and Maj and I have been married here, had a baby, and made a business for ourselves. Even though we don&apost own a house (yet), we&aposre putting down roots. Now when I return to California, it feels like a visit -- like traveling to just another destination. And you know what? California is a fabulous place to visit. Northern California even more so. San Francisco is a spectacular place on the edge of the ocean with music, art, redwood trees, organic food, and a sense of humor about itself that no other town quite has. It will be good to get back to SF for a while. It will be nice to take the baby around to see people and things that she hasn&apost ever seen before. We&aposll be in wt:Palo Alto to stay with my folks, visit my brothers in wt:San Francisco, up to wt:Petaluma and wt:Oakland to visit friends, and maybe even down to wt:Big Sur for a campout next weekend. I&aposve got the Web 2.0 Conference that I&aposm covering for LinuxWorld. And I&aposm sure there&aposll be more in there; we need ot dip the baby&aposs toes in the Pacific sometime soon. tags:

Ben Hutchings: While Planet Debian is talking about money...

Julien Blache: "You ll be pleased to learn that a release manager needs $6000 USD to cover for living expenses for a month." Sounds high, right? But we're talking about contractors, not employees. Contractors have to cover certain expenses that are generally paid for by employers, such as (depending on jurisdiction): and in this case, their own equipment. (But they save on transport!) Besides which, you have little idea how much Steve or Andi might need to pay in mortgage repayments or rent, or how many dependents they have. Nor should we pry into these personal circumstances.

24 October 2006

Anthony Towns: Todo Lists

A while ago I read Steve Yegge’s rant about Agile development, though I’ve forgotten who linked to it. The thing that struck me as interesting was the bit about “work queues”:
With a priority queue, you have a dumping-ground for any and all ideas (and bugs) that people suggest as the project unfolds. No engineer is ever idle, unless the queue is empty, which by definition means the project has launched. Tasks can be suspended and resumed simply by putting them back in the queue with appropriate notes or documentation. You always know how much work is left, and if you like, you can make time estimates based on the remaining tasks. You can examine closed work items to infer anything from bug regression rates to (if you like) individual productivity. You can see which tasks are often passed over, which can help you discover root causes of pain in the organization. A work queue is completely transparent, so there is minimal risk of accidental duplication of work.
Sadly, googling for “work queue” doesn’t come up with any sort of todo list stuff, but rather a multiprocessing scheduling tool which is cool, but not immediately relevant for me. As far as I can see, whatever was actually being talked about either isn’t public, or is more of a concept than an actual tool. The only Google Todo thing I could find was an applet thing for the personalised google homepage, which just lets you make todo items and set them as high/medium/low priority. And while that might be all that Steve Yegge was talking about, it doesn’t really feel terribly inspiring to me. I guess what I’d really like is to have todo items get assigned to a project (so that I can ignore all the todos for projects I don’t want to worry about atm), and also to be able to give them a deadline (so I can treat them with a bit more urgency when necessary) and a priority (so that I can easily spot things I’m willing to defer or ignore completely when I find I don’t have time to do everything I’d like). I suspect I’ll probably just stick with writing notes in vi to keep track of things, though, same as I have been for years.

Ian Murdock: LSB Developer Network launched

Last week, the Free Standards Group launched the LSB Developer Network, a community resource for developers building portable Linux applications via the LSB (read the press release and the introduction from LDN editor Martin Streicher). The LSB Developer Network (or LDN for short) aims to provide a well known starting point for developers looking to target the variety of Linux distributions available today without requiring a separate version for each distribution. It is the perfect complement to the LSB, which already provides a “highest common denominator” across the major distributions; and LSB Certification, which allows ISVs to indicate that their products will work with LSB Certified distributions. The big themes of LDN are “decentralized” and “bottom up”—to paraphrase Darrin Thompson, it’s a developer network that’s actually a network. In other words, we’re not taking the usual path of hiring a bunch of people to construct a centralized “network” from the top down—after all, Linux is a fundamentally decentralized phenomenon so shouldn’t a developer network for Linux be decentralized as well? Like the LSB, we see LDN as essential to the ultimate success of the Linux platform, an answer to similar programs for the centralized, proprietary platforms Linux competes with but built using the very techniques that make Linux what it is. Our fundamental belief is that “decentralized” doesn’t have to mean “fragmented”, and LSB and LDN are both key steps toward that end goal. We’re off to a good start too: LDN has the backing of a broad range of Linux platform stakeholders ranging from distribution vendors (Novell, Red Hat, Ubuntu) to OEMs (HP, IBM) and ISVs (MySQL, RealNetworks) to tools and content providers (O’Reilly, SlickEdit). One upcoming feature I’m particularly excited about is the integration of Safari Books Online. Soon, you’ll be able to type, for example, a function name into the LDN search box and get not just results from the link directory but also results from O’Reilly titles and others you know and love. We’re moving rapidly to add community content as well, including man pages and canonical reference documentation; and we’ll be hooking LDN into the LSB database, so you’ll be able to query the status of interfaces too, including whether or not those interfaces are in the LSB and what their status is in each of the major Linux distributions, to help make your applications as portable as possible. If you’re a Linux developer, and particularly if you use del.icio.us to bookmark resources on the web related to software development on Linux, I urge you to contribute to the LSB Developer Network. It’s easy: Simply create an account and link your account to your del.icio.us account (you don’t need to provide your del.icio.us password, just your username), and as you bookmark, tag, and annotate pages, your bookmarks, tags, and annotations will be pulled into the LDN directory. Help us build a developer network for Linux, bottom-up style!

Uwe Hermann: Drupal vs. Joomla! - Code Metrics

The blog post Drupal vs. Joomla - Fight! pointed me to a discussion on the drupal-devel mailing list about the ohloh.net website which tries to gather some statistics/metrics about the code of Free Software projects. Their slogan:
Explore Open Source Mapping the open source world by collecting
objective information on open source projects.
You might want to read their Terms of Use, though, which don't sound very open... Anyway, their stats about Drupal and about Joomla! are flawed (for example) because they seem to include the whole contrib CVS tree of Drupal (not just the core Drupal), which is huuuge. But there's no need to use any fancy website anyway, there are Free Software tools out there which can produce some metrics, too. The following data is generated using David A. Wheeler's SLOCCount (for the respective tarballs of the current stable releases): Drupal 4.7.4
Total Physical Source Lines of Code (SLOC)                = 8,012
Development Effort Estimate, Person-Years (Person-Months) = 1.78 (21.34)
 (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months)                         = 0.67 (8.00)
 (Basic COCOMO model, Months = 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule)  = 2.67
Total Estimated Cost to Develop                           = $ 240,198
 (average salary = $56,286/year, overhead = 2.40).
Joomla 1.0.11
Total Physical Source Lines of Code (SLOC)                = 65,880
Development Effort Estimate, Person-Years (Person-Months) = 16.25 (194.94)
 (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months)                         = 1.54 (18.54)
 (Basic COCOMO model, Months = 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule)  = 10.51
Total Estimated Cost to Develop                           = $ 2,194,486
 (average salary = $56,286/year, overhead = 2.40).
Not that I think these numbers mean anything ;-) Lines of Code is a very, very unreliable indicator for code quality (or anything else, for that matter)...

23 October 2006

Evan Prodromou: 1 Brumaire CCXV

First day of Brumaire -- the foggy month -- today, and the Montreal weather seems bound and determined to fulfill the promise of that gray name. The day of pomme (apple), which reminds me that we&aposve wanted to go apple-picking in the Autumn since we arrived in Quebec a few years ago. But something seems to push us inside on October and November days. Locals say that the best way to confront Winter is face-first, getting outside and being active in the snow. I&aposm not sure; it&aposs never worked out that way for me. We had snowfall a couple of days ago; in the middle of a rainstorm big wet clumps of snow started falling from the sky. I was working out at the gym around the corner from our house, and people in the weight room went to the windows to watch the snow fall. Halloween is the traditional day for the first snow for Montrealers; more than a week early was kind of fantastical, like a long-odds horse winning a race. tags:

Mo&apos blogging I can&apost say why, but my production has dropped off precipitously on this blog in the last week or so. Partly it&aposs had to do with an increased workload; also, being out of town for two long weekends in wt:Hudson (New York) and wt:Halifax (Nova Scotia) threw me off my pace. And I&aposve felt some pressure to cover these trips and other things going on in my life, which has kept me from writing short sharp posts. But mostly I think it&aposs a case of keeping up a feedback loop for myself. When I&aposve made a blog post, I watch for responses on Technorati or Planet Debian. I add one more thing or one more post. I get in the habit of blogging and then it comes more naturally in short bits and movements. I guess it all comes down to the typical but hard-to-remember suggestion: if you want to do something, you have to do it. tags:

BarCampMontreal Montreal&aposs BarCamp event turned out to be even better than I anticipated. I got up late on Saturday morning and I wasn&apost at the downtown location till quarter to 10. It was held in Fred Ngo&aposs swing dance studio, Cat&aposs Corner, on the power-centre block of 400 Ste.-Catherine. The studio had tables and chairs and a reception area set up, and it turned out to be a great venue -- lots of room and a big feeling because of the mirrors on the walls. I got there just in time to catch Chris Hand of Zeke&aposs Gallery give an excellent talk about collecting art and participating in art culture in Montreal. Not only was it extremely informative, but it charged me up to be more involved in Montreal&aposs art scene. It also set a great tone for the rest of the day -- talks at the event ranged from alternative voting systems to art and research projects to technology surveys to demos of new products and Web sites. It kept the entire thing really fun and refreshing -- different parts of your mind used at different times. I was glad to see that Heather Kelley and Damien had come; I&aposd made a point of inviting them, so it was good to see their faces. They did one of the first presentations, about their upcoming games-and-art event, GAMMA, at SAT on 9 November 2006, straddling the gap between the industry-oriented Montreal International Games Summit and the gamer convention Festival Arcadia, not to be confused with Montreal&aposs other top export, The Arcade Fire. Man, games are hard. Anyways, they demo&aposd a game they&aposre developing for GAMMA in which the gameplay action responds to arbitrary musical input; they&aposve got several teams of developers who are putting together games to fit this criterion. Interesting concept, fun and cool. There were a ton of great discussion, but I think my favorites for the day have to include Hugh McGuire&aposs talk about the excellent Librivox project; Anne Goldenberg&aposs presentation on Wikigraphe, which I&aposd seen before but which continues to boggle; Austin Hill&aposs discussion about raising money and building Zero Knowledge; and Sylvain Carle&aposs talk about successful consulting. The best part of the talks was that I came away feeling smarter and with new projects I wanted to work on. S bastien Pierre&aposs demo of data-mining del.icio.us tags in revealicious made me think hard about wp:data clustering algorithms (something I&aposve wanted to work on for a while). Patrick Tanguay gave a great talk about co-working setups in other cities, with the aim of starting one here in Montreal. As a near-independent worker who&aposs getting tired of his home office, this was a pretty fascinating idea, and I&aposm hoping to follow-up. And Simon Law&aposs talk about Web 2.0&aposs negative influence on Open Source software gave me a lot to chew on for my visit to the Web 2.0 Conference coverage I&aposm doing for Linux World. All in all, I thought the event was the best that BarCamp has to offer. Montreal has such a rich technology and Internet culture, and some of the smartest people in town were at the event. All our major tech sectors were covered, and people interested in hacking, yakking, and entrepreneurship were in a nice balanced attendance. We were all in one room together, which kept up a good atmosphere, and we had only 15 minutes per talk, which kept things well-varied and interesting. If I had any criticisms, it would be merely that I can think of so many people I wish had been there. There are a lot of women involved in Montreal technology and Internet culture who weren&apost in attendance, and Montreal&aposs majority francophone community was underrepresented. But I think those are outreach problems that need to be handled for the next time around. Fred Ngo is already talking about BarCampMontreal2, which may or may not be coordinated with RecentChangesCamp. Yesterday&aposs Montreal Gazette had an article called Geekfest comes to town which featured a photo of Heather and Damien in the print edition. Simon Law got an excellent BarCampMontreal photoset on Flickr, and also invited me out to take photos together (fun). There&aposs a BarCampMontreal post-mortem for those interested in a follow-up discussion. tags:

N Dollars... American! One of the funny things about Canadians is that when they talk about a large amount of money, they suffix the dollar amount with the word American to let you know that it&aposs really a large amount of money. Like, "I just ordered this t-shirt online and it cost me thirty-five dollars... American!" or "He moved to New York and now he&aposs making 85 thousand dollars a year... American!" It&aposs less of a punchline than it used to be -- American dollars used to trade at about 1:1.5 or 1:1.6 to the loonie, but now it&aposs hard to find 1:1.2. Still, Canadians talk about American dollars like D&D players talk about platinum pieces. They&aposre just a qualitatively different currency. I note this because I joked about in previewing Austin Hill&aposs talk at BarCampMontreal, and he did note that they raised $80 million American for Zer0 Knowledge. I had to stifle a laugh during the talk. Austin writes - Hi Evan. Yeah that&aposs funny. I may have mispoke - we raised $55 million american which at the time was important to distinguish because that was $80 million canadian. Just wanted to be clear. Loved your presentation BTW tags:

Project Blackbox Everybody&aposs all abuzz about Sun&aposs innovative design in their new Project Blackbox. It&aposs a datacentre that&aposs built into a big shipping container; whenever you need a datacentre you can just ship one of these blackboxes to wherever you need it. I have to admit that it&aposs an amazing piece of in-your-face metaphor. I mean, when a company is shipping tech jobs overseas, they can make it all the more poignant by actually taking the jobs and putting them in this big shipping container and stenciling "JOBS" on the side and packing it on a cargo ship and sending it off into the sunset. JOBS And you don&apost really use these big containers unless you&aposre shipping something faaar away. If your job is in that box, man, you can just kiss it good-bye, because baby it&aposs gone. Maybe the best way to ship out one of these jobs containers would be to have a big bulldozer that comes through the middle of town, crushing the community infrastructure under its treads, and then picks up the big shipping container full of tech jobs and carries it off to a big ship in the harbour (rolling over some more schools and houses and small businesses) and then sends it off to somewhere crazy and foreign where they keep monkeys as pets as a matter of course. In any case: good job, Sun. I hope this works out great for you. tags:

John Goerzen: We need to follow the Amish example

Just a few weeks ago, the world heard the news of the tragic school shooting at an Amish school in rural Pennsylvania. A deranged man entered the schoolhouse, bound and gagged female hostages, brought along torture equipment, and shot 10 of them. 5 died, and the remaining 5 are believed to still be hospitalized.

Back in 1990, a deranged man committed a series of murders near the University of Florida campus in Gainesville. The story mentions 5 people that were killed.

Both were tragic situations. Both men killed people that had their whole lives in front of them. Both shook an entire community.

But look at how the communities responded. The Amish responded like this:

CNN reported a grandfather of one of the murdered Amish girls said of the killer on the day of the murder: "We must not think evil of this man."

Jack Meyer, a member of the Brethren community living near the Amish in Lancaster County, explained: "I don't think there's anybody here that wants to do anything but forgive and not only reach out to those who have suffered a loss in that way but to reach out to the family of the man who committed these acts," he told CNN.

The Amish have reached out to Roberts' family. Dwight Lefever, a Roberts family spokesman said an Amish neighbor comforted the Roberts family hours after the shooting and extended forgiveness to them.

An article in a Canadian newspaper the National Post stated that the Amish have set up a charitable fund for the family of the shooter. (Wikipedia)


In addition, the Amish invited the Roberts family to attend the funerals for the Amish girls he killed.

Gainesville reacted this way:

Dianna Hoyt, Christa Hoyt's stepmother, said Rolling's execution has been eagerly awaited by the victims' families. Some will be inside the prison to witness it. . .

Sadie Darnell, who was the police department's media spokeswoman at the time and developed enduring friendships with the victims' families, said Rolling's execution still matters, even if it also provides him more of the notoriety he sought.

"Retribution . . . is important because it represents that our society is holding that person accountable," said Darnell, now a candidate for Alachua County sheriff. (CNN)


We've all heard of murders that have taken place lately. Usually they are accompanied by calls by politicians, victim's family, and sometimes even clergy to kill the perpetrator. In the days after 9/11, there were reports of anybody that looked Middle Eastern being attacked in several different places around the country.

I have never understood this great desire for revenge. How does that help anyone?

What the Amish did was right religiously and morally. They truly followed the New Testament call to love your enemies and forgive. It is not easy to follow all of Jesus' teachings, and nobody said it would be. But they are doing it, and they have already begun healing. Reports are that the Roberts family has become friends with several of the Amish in the area, and they are working to help each other out after this horrible tragedy.

Even putting religion aside for a moment, the Amish actions are quite simply the right thing to do. By spreading love instead of hate, and friendship instead of revenge, they have succeeded in making sure that no cycle of violence starts there.

In contrast, 16 years later, the families of the victims in Florida still aren't healing. They are still angry and bitter. They are still seeking revenge. They hope that their lives will get back to normal after the murderer is killed. But after 16 years of stewing about it, will they really? And what about the family of the murderer, whose lives certainly must have been a mess for the past 16 years? They will now lose a family member. Does anyone care about them, or will they now turn angry at society and possibly spread the pain more?

Imagine what would happen if so many more people around the world took the Amish perspective -- to forgive those that wronged us. How long must it be before we can forgive? How far back do we spread our hate? Do we still hate those that were involved in 9/11, or can we forgive them? Do we still hate the Germans for what their ancestors did in World War II, or can we forgive them? Do we hate politicians with whom we strongly disagree, or think are liars? Do we still hate all those that have wronged us personally -- someone that stole something from us or the sadistic boss?

Knives, electric chairs, and bombs do not buy reconciliation. They can not "win over" the hearts of others. They do not make our lives easier. Hate brings more hate, and more resentment.

Forgiveness is not easy. We all hope that we will never be involved in such a tragedies as these. But let us follow the example the Amish have shown -- forgive for all things, big or small, important or not, painful or not.

Only then will we be at peace with ourselves, and only then will we have the chance to be at peace with our neighbors.

22 October 2006

Adam Rosi-Kessel: Channel Cafe: Respectable Espresso

One of my longstanding frustrations living in Boston is the lack of artisanale espresso sources. Starbucks is, of course, ubiquitous (I think there are four within a block of where I work), and at least espresso drinks there aren’t bad, but there is little-to-no artistry involved. They aren’t aiming for perfection, they’re aiming for absolute consistency, mass appeal, and caffeine. Ever since Starbucks started opening in strip malls and grocery stores like Safeway, I’ve doubted whether they even care about maintaining an image of serving an elite population. This article presents some good background on the art of espresso, but apparently the only place it’s happening in Greater Boston is on the other side of the Charles River, which might as well be Prince Edward Island. (See also this article about Murky Coffee, my and Steve’s favorite coffee place in DC). I’d love to support Emack and Bolio’s, my neighborhood coffee shop, but the coffee and espresso there are inconsistent at best. I don’t get the feeling that the baristas there get a lot of training. Or that they even consider themselves to be baristas (according to Wikipedia: “one who has acquired some level of expertise in the preparation of espresso-based coffee drinks,” or “a professional who is highly skilled in coffee preparation, with a comprehensive understanding of coffee, coffee blends, espresso, quality, coffee varieties, roast degree, espresso equipment, maintenance, latte art, etc.”). Hey, while I’m talking about Starbucks, I should mention that Google Maps is wrong. There is no Starbucks at 1510 Centre Street in Roslindale, Massachusetts. It’s nearly a mile away from the real Starbucks at 1810 Centre Street, that has the same phone number. Wouldn’t you think Google could have figured that out? Can someone tell them? Anyway, I recently discovered the Channel Cafe (deserving a PageRank boost), just a brisk 8 minute walk from my office down Summer Street across the Fort Point Channel, actually has quite respectable espresso and espresso drinks. I first went there for lunch several months ago and the place was mostly empty — more recently, there seems to be a line up the steps every day. (The cafe is in the basement of art gallery space and is owned by one of the Fort Point artists.) Aside from excellent espresso, they have a great menu, especially for vegetarians, with entrees such as baked tofu with pan steamed vegetables, peanut dipping sauce, jasmine rice, mandarin and oranges, and basil and ricotta ravioli with fresh tomatoes, zucchini, sweat pea and mint coulis, and parmesan cheese. All for under $10, which is a bargain in the greater financial district. I’m afraid the line up the stairs may soon be out the door… It’s a good sign for the burgeoning Seaport District, though.
(…more espresso art…)

Biella Coleman: Hunting and Gathering on the Internet

This morning I got back to an article that has been on and off my work-plate for a year now, one that I have to turn in to a discussant for my 4S panel as well for an edited collection of articles on the intersection between art, activism, and biopoltics. Part of my efforts meant attacking a virtual “stack” of articles and one of them was one of best journalistic articles I have read in a long time. Exceedingly clear prose is combined with good references, hard numbers and just the right amount of passionate verve to make reading actually fun and not just another nameless, faceless cog in the academic research wheel. The article mentioned a couple of interesting studies that while sadly not linked from the article (but I am going to take that was an editorial and not authorial decision), they were pretty much cake to find by doing a little poking and prodding on the Internet. So for example, one of them was published on PLoS Serotonin and Depression: A Disconnect between the Advertisements and the Scientific Literature and stands pretty strongly on its own right. But what is even better are the long list of citations (many with links) that would otherwise be frankly, a *total* time consuming bitch to find like the correspondence between the FDA and pharmaceutical companies: # Food and Drug Administration Division of Drug Marketing Advertising and Communications (1997) Effexor warning letter. Rockville (Maryland): Food and Drug Administration. Available: http://www.fda.gov/cder/warn/june97/effexor.pdf. Accessed 14 October 2005. Total gems given to you right there on a silver plate. That is what I love about Internet based research… On the other hand, this extreme access is not always so peachy. The amount of data now available can be experienced as a totally mind-numbing, frightening, chaotic infolanche (as one of my old adivsors liked to call it), which translates into a lot of academic hunting and gathering not to mention all the sorting, sifting, cataloging, and then of course trying to remember what the heck you have just amassed in the first place, even with the aid of tags and all I am not sure if things have gotten easier or harder because this is all I personally know but what I do know is that there are times when I just love the hunt, losing myself for hours, following links, gathering articles, enlivened, exicted about research and there are others when the woolly mammoth of infomartion gets the better of me.

Kenshi Muto: Tokyo Debian monthly meeting, October 2006

Yesterday, I had a chance to talk about Extremadura i18n meeting at Tokyo Debian monthly meeting. This meeting was organized by Junichi Uekawa and wonderfully 20 or more people came and filled the meeting room (awesome!), thanks! My paper is included in this PDF [in Japanese]. I picked up and spoke some themes from what we discussed at Extremadura; i18n task force, Pootle system, and language-pack/tdeb. PO-based translation has an advantage and a disadvantage. The tools support PO are mature and PO is very useful for the short messages. But using it for documents, such as manuals or Web pages is not so useful. Especially translating to Japanese sometimes add/delete/reform sentences. Some attendees suggested that we would always use the original XML (or something) format for translating/reviewing and have PO format in the central database. Masayuki Hatta pointed the license of translation. For example, Japanese is completely different from English, both words aren't always correspond 1 on 1... Translators use their creativity power. He said translators would have a copyright for their translation instead of original author. When I talked with Warren Togami was Fedora US leader last month at Tokyo, he said his project asked to agree "translation license agreement" to all translators. If we Debian or Debian-JP apply a central translation system like Pootle and use its translation memories, it's time to consider making similar license. Although current idea of Tdeb is still under the development, most attendees loved that idea rather than language-pack. For me, the goal of this meeting was not only speaking my experience report but recruiting more people for i18n/l10n working also. I'd like to recommend Nabetaro-san for next i18n meeting attendee instead of me, and Noritada Kobayashi for next of next. I strongly suggested attending next Debconf to them also. They are hardly working for Debian i18n/l10n in Japan. I hope attending such meetings expands their personal connections and motivations. There were two other sessions at the meeting. Matsuyama-san demonstrated creating Flash on Debian by using ming, and Junichi talked about profiling apt-get by oprofile tool. Both topics were interesting for me.

21 October 2006

Per Olofsson: acpi-support vs hibernate

I used to use the acpi-support package. It originally comes from Ubuntu. The problem is, it really does a *lot* of weird things when suspending and resuming. There are all sorts of workarounds for broken drivers and hardware. And in the end, all these hacks only made things worse: it actually worked better if I just did "echo mem >/sys/power/state" than if I used acpi-support.

I guess this is an Ubuntu thing, hack around everything and try to make it work. It gives fast results. In Debian, I think there's often a kind of opposite perspective: if the driver is broken, fix the driver, don't add ugly hacks. Both approaches of course have their pros and cons.

But now, I have switched to the hibernate package. I like it a lot better, because it isn't just a collection of shell scripts. You can actually configure which workarounds you want to enable, and how you want things to be done. I don't know why Ubuntu didn't simply use this package instead of inventing their own. Maybe hibernate wasn't around at the time.

In the long term, there really needs to be distribution-independent suspend/hibernate interface though. The current situation is less than ideal. Maybe pm-utils will fill this gap.

Update: Oh, I forgot. acpi-support is configurable, but not in a particularly intuitive way, at least not when compared with hibernate. Or maybe it's just my irrational taste.

Update: What I meant to say here actually, I think, is that hibernate is a lot easier to configure and much better documented. You can in a much easier way control exactly which workarounds/hacks you want to apply. And the options are described in the manpage for hibernate.conf. Editing /etc/default/acpi-support is a lot less flexible and a bit confusing.

Masayuki Hatta: BTS got a bug


Trying to read Debian Bug#394350, it says:

An error occurred. Dammit. Error was: Bad bug log for Bug 394350. Unable to read records: state kill-init at end at /usr/local/lib/site_perl/Debbugs/Log.pm line 205. .


Hmm...

Evan Prodromou: 28 Vend miaire CCXV

It's been days since I've blogged -- I've got a lot to write about Halifax and I've been putting it off, but I wanted to jump on one more time to put in a plug for tomorrow's BarCampMontreal. I keep forgetting how great this city is for interesting technical people. Simon Law is going to be talking about how Web 2.0 is destroying Open Source software, and Austin Hall will talk about how you can get billions of dollars (American) with Zero Knowledge. The full Horaire shows the proposed schedule, but... hey, it's BarCamp, right? Anything could happen. As little as I like being up and about at 9AM on a Saturday morning, I'm excited about the event tomorrow. Should be a good time. tags:

19 October 2006

Tollef Fog Heen: Releasing Ubuntu

So, the Ubuntu release candidate was released today. As a release manager, it's a fascinating process. First the development where there is relativetly little central control: People work on their specs and my job as a relase manager is to roll new alpha/snapshot releases every couple of weeks. Those are lightly tested (does it boot and install on at least one machine?) and if a derivative or an architecture isn't ready, well, then it isn't ready. Beta, the release candidate and the release are completely different beasts. We have test plans, people are assigned tests and so on. In addition, we have a freeze which in total lasts about a week for beta, two weeks for release. Every upload has to be hand-checked and approved. As the release grows nearer, the bugs have to be more severe in order for an upload to be approved and in the end it's more or less a full commitment "we have this, we have tested this thoroughly and there is no way we can do a full test and still release on schedule". At some point, it gets scary. There is just one command left to run; sync-mirrors. No arguments, just the command. I pushed the button, and we are now live.

Wouter Verhelst: nVidia

I know, I just ranted about it. However, it would seem that the Xorg driver can do more with the video card in my laptop than would appear at first sight. If I plug a VGA monitor to the mini-DVI output of my PowerBook and start X, then the nv(4) driver seems to detect it. Behold the diff:
--- Xorg.0.log.not-connected	2006-10-19 14:49:07.000000000 +0200
+++ Xorg.0.log.connected	2006-10-19 14:49:51.000000000 +0200
@@ -11,7 +11,7 @@
 Markers: (--) probed, (**) from config file, (==) default setting,
 	(++) from command line, (!!) notice, (II) informational,
 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 19 14:42:00 2006
+(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 19 14:42:46 2006
 (++) Using config file: "xorg.conf"
 (==) ServerLayout "Default Layout"
 (**)  -->Screen "Default Screen" (0)
@@ -444,7 +444,7 @@
 (II) NV(0): Probing for analog device on output A...
 (--) NV(0):   ...can't find one
 (II) NV(0): Probing for analog device on output B...
-(--) NV(0):   ...can't find one
+(--) NV(0):   ...found one
 (II) NV(0): Probing for EDID on I2C bus A...
 (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
 (II) NV(0): I2C device "DDC:ddc2" removed.
@@ -452,7 +452,46 @@
 (II) NV(0): Probing for EDID on I2C bus B...
 (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
 (II) NV(0): I2C device "DDC:ddc2" removed.
-(II) NV(0):   ... none found
+(--) NV(0): DDC detected a CRT:
+(II) NV(0): Manufacturer: MAX  Model: 178e  Serial#: 2006
+(II) NV(0): Year: 2000  Week: 13
+(II) NV(0): EDID Version: 1.0
+(II) NV(0): Analog Display Input,  Input Voltage Level: 0.714/0.286 V
+(II) NV(0): Sync:  Separate
+(II) NV(0): Max H-Image Size [cm]: horiz.: 36  vert.: 27
+(II) NV(0): Gamma: 2.76
+(II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
+(II) NV(0): redX: 0.632 redY: 0.329   greenX: 0.272 greenY: 0.604
+(II) NV(0): blueX: 0.142 blueY: 0.062   whiteX: 0.280 whiteY: 0.311
+(II) NV(0): Supported VESA Video Modes:
+(II) NV(0): 640x480@60Hz
+(II) NV(0): 640x480@75Hz
+(II) NV(0): 800x600@75Hz
[...more data about the monitor goes here...]
The nv(4) manpage also contains this bit:
       Option "CrtcNumber" "integer"
              Many graphics cards with NVIDIA chips have  two  video  outputs.
              The  driver attempts to autodetect which one the monitor is con 
              nected to.  In the case that autodetection picks the wrong  one,
              this  option  may be used to force usage of a particular output.
              The options are "0" or "1".  Default: autodetected.
... but when I set that to 1 in the Section "Device" of my xorg.conf, it still uses the internal monitor of my laptop. Am I missing something?

Russell Coker: blogs and bug tracking

I believe that adding blogging technology to bug tracking systems (such as the Debian BTS and the Red Hat Bugzilla) offers significant benefits for users and developers.

It seems that there is only one significant difference between the features offered by blog software and the features required by bug trackers, blog entries are owned by the person making the post (the owner of the blog) and BTS entries are owned by the package owner. This is a minor technical difference, adding the ability for anonymous users (or users who have authenticated via an email address or other method) to create new entries in a blog owned by someone else is a minor feature change. Once the entry is created only comments would be accepted, and comments could be made in the usual manner with moderation etc.

The benefits of using blogging software (or extending current BTS systems) would be to have RSS feeds of bug reports and comments on bugs, include a single feed of all bug reports (IE blog entries) and updates (IE comments on blog entries) for a single blog (IE package) - this functionality doesn't seem to be common in blog software but surely will be soon.

This would allow Planets of recent bug reports in distributions or in areas. EG a SE Linux planet installation could syndicate the bug feeds for packages in Fedora and Debian as well as other sources of SE Linux information. The SE Linux bug feeds could include all bugs with the selinux tag in all blogs on the BTS, thus a single Planet configuration could easily cover all new development and debugging.

Another configuration possibility would be to have a single blog for all bugs in a distribution and to have tags for each package, this would become messy though as tags have to be used for issues that are not specific to packages (EG a "selinux" tag would list bugs in all packages that relate to SE Linux).

Tags could be changed by any user (possibly with some restrictions), and there could be special tags for release-critical bugs or for bugs in different stages of QA (for example the Red Hat Enterprise Linux approval process could be managed by adding certain restricted tags to the bug - this would also allow getting a feed of all bugs that have passed certain approval milestones). This would make it easy to get a list of all bugs in a certain approval category.

Current BTS systems such as the Debian BTS and the Red Hat Bugzilla could be extended to syndicate content. As they already have web interfaces and support automatically sending updates by email it should be easy to add the basic level of such support to them. But it might give a better result to go the other way and modify a multi-user blog system such as Wordpress-MU to have extra features for bug management.

BTS systems typically have bug ID numbers that increase sequentially while blog software typically gives something like http://blog.example.com/YYYY/MM/blog-entry-name.html when it's often more convenient to have something like http://bug.example.com/number. Of course it would not be difficult to have a little database that allows creating sequential numbers to map to arbitrary URLs in a similar manner to tinyurl.com. This could be either integrated into blog software (so that it says "bug #1234 has been created" or be available on demand (click a link to get a sequential number assigned). Incidentally using characters and digits for the short name of the bug (as done by tinyurl.com) would allow four characters to represent 1679616 bugs, this is enough for all bugs in the Debian and Red Hat bug databases combined. With tinyurl type technology there is nothing preventing us from having a single system creating unique IDs for all bugs in all distributions of Linux with a four character index (which is easier to remember than the 6 sigit numbers used in Debian and Red Hat at the moment).

I realise that most blog software will store the entries in a database which has sequential numbers assigned. So doing a database lookup to convert a human-readable URL into a sequential index when we have just done another database lookup to convert a sequential index into a human readable form is inefficient, but that's the way of things, computers do things inefficiently so that humans can work in ways that are efficient for them.

Note that throughout this post I refer to the Planet aggregation system, but really any of the aggregation systems can be used. One of the benefits of this is that people can use mailing lists, Google's reader, Planet, or any other reader they wish with the feeds. RSS feeds can be read by many programs and the user gets to choose which works best for them.

18 October 2006

Wouter Verhelst: Wanted: some systray applications

There are a few things that I'd like to have in my fd.o-compatible system tray, but that do not seem to exist at this time (either that, or I haven't been looking too carefully): Anyone know of such a thing?

17 October 2006

Russell Coker: Debian SE Linux

Yesterday Erich Schubert blogged about reducing Debian SE Linux work due to lack of hardware. To solve such problems I've put a Debian/unstable machine on the net and given Erich the root password. Also now I am starting work on Debian SE Linux again too. There should be some significant developments in Debian SE Linux in the near future.

Also if anyone else has a problem of a lack of hardware getting in the way of free software development the first thing to do is to mention it on the IRC channel for the project in question. While Erich has demonstrated that blogging works, IRC is faster.

Russell Coker: review of Australian car web sites

It seems that Toyota isn't alone in having non-functional web sites. In fact it's better than some, the basic information on the cars is available and it is possible to get contact information for car dealers, also they have a feed-back form on their web site (to which I submitted my previous blog post). Incidentally the Lexus site had much the same problem as the Toyota site (hardly surprising as Lexus is the luxury marque from Toyota). But I expect that if I phoned Lexus to ask about their vehicles I would get a better call-center experience which would make me less inclined to blog about them.

Daihatsu vehicles are sold by Toyota. Their web site doesn't use Flash, but it has so little content that it doesn't count.

I decided to quickly review the web sites of car manufacturers that sell in Australia for a fair comparison. I found three sites worse than Toyota, two sites that were equal (counting Lexus), and six that were better than it.

Holden has the worst site, they don't display any information if you don't have flash, they don't even display a phone number! I wonder how much Adobe pays web programmers to pull this sort of stunt. I can't imagine Holden management saying "if a customer comes to our web site and doesn't have Flash then don't display our phone number or any other contact information, they can use Flash or buy a Ford instead". Obviously some web monkey has run amok and done their own thing without following directions. Probably some people need to be sacked in the Holden web development group.

Volvo Cars has a very bad site. Most of the content is involved with Flash in some way and refuses to load. There is a mailto reference that is broken, and the overview page for the S60 seems to have a JavaScript loop (I aborted the load after it loaded 245 pictures and was still going). The Volvo page for their other business is quite functional although minimal.

Hyundai has a bad site. The front page works OK, but some of the sub-sites to display information on vehicles redirect to sites such as evolveddriving.com.au which are "optimised for 1024x768" and require Flash and Quicktime while others do strange things like changing the size of the browser window. Overall it's a very bad site, but at least I could find the contact details for my nearest dealer, and it has a feedback form.

Subaru has an OK site. The only thing I couldn't access without Flash is information on their AWD (All Wheel Drive) technology. Unfortunately they provide no email address and no form for sending feedback.

The main Ford web page claims that Flash is required, but their site just works without it. In a quick test I was unable to find any functionality on the Ford site that is missing because of not having Flash. Ford have a well designed site.

The Volkswagen site makes no mention of the fact that I don't use Flash, it does however have some strange unused spaces in the middle of the screen. I guess that it recognised that I don't have Flash and made a semi-successful attempt to work around it. I could get all information I wanted including dealer contact details.

The main Mazda web page displays a message about Flash not being installed and offers a link to a non-Flash version of the site. The Flash section is at the center and the buttons at the sides work if you don't have Flash. This seems to be a well implemented site.

Citroen has an OK site, no flash that I noticed (although there were large blank areas on the screen at times indicating that something was missing), the information was all available and browsing was reasonably easy. One thing that annoyed me was that there were movies available but only through some sort of JavaScript that tried to play them in my browser. I have never bothered setting up my web browsing machine for playing movies (among other things it has no speakers) so this is a problem for me.

Peugeot has a good site. No apparent flash and it's reasonably easy to use. It has more pictures than Kia but the JavaScript navigation stuff is fancy. One nice feature is a single page with pricing summaries for all models. If you have $X to spend on a Peugeot you will easily discover which ones you can afford.

Kia has the best site I saw! Not only is there no flash, but it's well designed, easy to navigate and it loads quite quickly. Please review the Kia site as an example of how to do it properly!

Let me know if I've missed any makes and I'll post an update.

Next.

Previous.