Search Results: "ag"

7 January 2007

Evan Prodromou: 16 Niv se CCXV

Amita June is reaching a point in her life where it's time for us to start weaning her from breastfeeding. Most parents do this much earlier, if they breastfeed at all, but we've been devotees of attachment parenting for a while, and we wanted to give her as much time nursing as possible. But at 15 months, she's ready to start doing things like sleep through the night on her own, drink only cow's milk, and be a little more independent. So, this month we're starting to do some night weaning. What does this mean? First of all, Maj is no longer nursing the baby to bed. She now is doing the main pre-sleep prep work (a bath), does a short nursing period, and then hands the baby off to me for some reading, songs, and walking down to sleep. This will gradually move into fewer, shorter nursings before sleep, and ultimately to none. Once that connection has been broken, I think the main point of nursing will be occasional comfort nursing during the day. Gradually, that will fade out. And then there will be none. It's kind of exciting to be the Primary Sleep Guy for the baby. We're re-connecting in a way that we haven't in a while -- I was only putting her to bed occasionally for a quite a while. It's also been pretty successful so far, which has been good. tags:

Souper Bruncher When Maj and I first moved to Montreal, we had help from some friends who we'd known from before. After we moved into our apartment, we invited them all over for dinner to say thanks. In order to get to know people in our new hometown, we also asked each person to bring someone we didn't know, so we could make new friends. The event was so successful, and we met so many new people, that we made it a regular occasion. For almost three years, every Tuesday night we invited friends over to our home for dinner (or souper in Quebecois French), with an open invitation to meet new friends and interesting people. It was a great way to meet interesting folks in Montreal, and most of our best friends here we met through these dinners. We were even profiled in Elle Quebec as a model for how to make new friends. But when the baby was born, we just couldn't manage to organize dinners any more every week. Cooking for 20+ people isn't that expensive, especially since we're pescevegetarians and that kind of food just isn't that costly. But it does take a lot of time and energy, and with a newborn baby we just didn't have either. Now, with Amita a little more than a year old, we're trying to start up our regular home parties on a more manageable scale. We're doing brunch at our house on Sunday afternoons around 3PM, with a much smaller list of invitees, requests for RSVPs, and a clear indication that the event only goes until bedtime. (Our Tuesday night dinners would occasionally stretch until dawn.) It seems to be working pretty well; we've had a lot of fun at the last couple of brunches we've had. And brunch is a much more laid-back meal than a dinner party, anyways. (Although John Usher asks incredulously, "By what stretch of the imagination is 3PM between breakfast and lunch?") I'm looking forward to our next brunch (tomorrow) a lot, and I hope to get many more friends over to our home in the next few months of Sundays. tags:

Eddy Petrișor: New laptop #2

A new laptop means more things than just new hardware.
  1. I will no longer have a PowerPC machine; it has been fine, I have been spoiled by Apple hardware and design, but I also had my share of bitterness (like it or not flash is ubiquitous, wlan works on i386 hardware via ndiswrapper, wine is good enough when no free alternatives are around)
  2. my father will use my current laptop in OS X; as sad as it may sound I am glad I will not have to administer the machine that much, and, like it or not, the OS X is better suited for him since he is not "that" skilled with computers
  3. I can't work on powerpc/bigendian specific issues, thus, the long pending and incomplete glest big-endian support patch will have to find a new person to take care of and finish it. BTW, the glest project needs developers, the current ones are busy and can hardly do maintainance. Is a pitty, the game has incredible graphics.
  4. I will be able to test the Debian Games Team's games... and I will be able to play again cursively Oolite. (BTW, Oolite should autobuild now, but it seems it hasn't been autobuilt, just the upload architecture is on version 1.65-4)

Adam Rosi-Kessel: Preventing Burglary

According to my neighborhood newspaper (the Roslindale transcript), there has been a rash of late-night home burglaries in the area lately. Although the paper calls them “robberies,” they are probably more accurately burglaries (and thefts). Common law burglary requires breaking and entering the dwelling of another during the night with the intention to commit a felony therein; robbery requires taking property from a person by force. (Modern statutory definitions of burglary typically do not require the “night” element). In any event, my point is not to quibble with the legal terminology, but rather to question the preventitive measures. From the article:
Captain James Hasson of District E-5 said that this robbery does not fit the mold of the Bellevue Hill break-ins. … Hasson said he was very shocked because Rendall Road is a beautiful, quiet neighborhood that doesn’t normally see violent crimes. He added that there have been extra patrols of the Bellevue Hill area and there will now be extra patrols of the Rendall Road area.
On a much smaller scale, this response is similar to the air travel liquid ban that occurred shortly after the foiled transatlantic bomb plot from last August. Obviously a complete ban on liquids will make it less likely that a terrorist will concoct a liquid explosive plot, but does nothing to actually deter attacks overall. Similarly, once a house on a particular street has been burglarized, adding additional patrols on that street might make another attack on that street less likely, but I don’t see how it makes the community as a whole any safer. More likely this response makes the community less safe. Assuming the total amount of police protection hasn’t changed but just been reallocated, there are now other areas with less coverage. Even a dumb criminal should be able to figure out to avoid heavily policed areas. Unless you actually live on the street that is now getting the additional protection, I would not be reassured by this news.

6 January 2007

Peter Van Eynde: Slow times

While the next debian release is being prepared it is not a good idea to upload new packages, so I'm trying to use the holiday to 'look across the fence'. For starters I've gotten me an iMac and so far I like Mac OS X. It is an immense improvement over Windows and a pretty good alternative to KDE from my point of view. I'm still a bit lost with accelerators and in-program window movement but it is nice to have another environment to play with.

And on that machine I'll try to play with sbcl, openmcl and f-script. But so far I'm been busy using iMovie to convert our DV tapes into DVD's.

Martin F. Krafft: Adam's Apples

I've been away from Zurich for a while, and one of the things I missed the most was my favourite cinema. So last night, I didn't need my arm twisted much (by Hanspeter) to go and see the Danish film Adam's Apples (warning: Flash content). Imagine a church community made up of four people: Ivan, the reverend, who lives Jesus' philosophy to offer the other cheek when slapped on one. Ivan is father to Christoffer, a spastic-retard, and widow to his late wife, who killed herself not being able to handle the retardation of their child. Ivan, of course, denies all this and treats Christoffer like a regular, jovial and energetic child, and lulls over the loss of his wife in an accident. If someone get too close to Ivan, he'll bleed from his ear. Ivan is played by Mads Mikkelsen, who also plays Le Chiffre in the latest Bond movie "Casino Royale" (which I'll cover in another post). Then there's Sarah, a dosser who got off with a man she didn't know or love and now expects a child. Because of her drinking problem, the child is said to have a 40% chance of being disabled. She cannot handle it and runs to Ivan for advice. Khalid is a Saudi who's on parole at the church after plenty of armed robberies of Statoil stations as part of his mission to destroy the Statoil empire. He speaks broken Danish (wonderfully translated in the subtitles), seems extreme at most of his actions, but all he really wants it is to return to Saudi Arabia. He's been at the church way longer than his parole, saving money but also just enjoying the innocence. Gunnar is a massively obese ex-tennis player who turned to overeating and alcohol after a ball of his was wrongfully judged to be out, causing him to lose an important game. He's at the church on parole for small-scale thievery and plays a role somewhat reminiscent of Lenny in "Of Mice and Men:" stupid but kind. He is also way beyond the end of his parole. There's also a doctor who seems to be the only one with a firm grasp of reality, but his sarcasm overshadows that completely. One day, Adam arrives. Adam's a misanthropic neo-nazi on parole, sent to the church to be cured. Adam calls himself evil and seems to be just that: he cannot deal with niceness, especially not the straioght-up, disarming kind displayed by Ivan in fact, he's the kind of guy who'd slap the other cheek even if not offered. Adam's task is to care for the apple tree (which is everyone's pride) and bake a cake from the harvest. As the story develops, Adam's fight against Ivan's benevolence reaches hilarious heights as the characters seem to exchange exactly those sentences that the other didn't want to hear. When later a group of neo-nazis join the battle, as well as what would have to be called God, everyone (characters and movie-goers) are left wondering who's after whom, and sundry other questions on morale. The film was once again a great display of Scandinavian cinematography, which I've grown to like a lot over the years of being a regular at this cinema. Despite the somewhat flat story and the surreal element of God in one scene (and only one), I can hartily recommend it. The actors are doing an amazing job, and in the end, the movie is primarily funny, not because of jokes or forced humour, but because of the dryness and darkness of what's happening between what seems to be average people like you and me on the screen. NP: The Flower Kings / Paradox Hotel

Andrew Pollock: [life] Trip to Spain

(continuing with clearing the blogging backlog) Four days after returning home to the US from the trip to Australia, I was at it again, flying the other way around the world. In hindsight, this was totally insane, but I'd expressed interest in going much earlier in the year, I think before we'd organised to visit Australia. I flew to Madrid, via Philadelphia. I've said it before, but I'll say it again, Philadelphia International is a very nice airport. It's the first time I've flown across the United States, and it really is a long way. Just like Brisbane to Perth, it's a long time on a plane for staying in the same country. Arriving in Madrid, entering the country was extremely straightforward, as I've also said previously, the immigration guy barely looked at my passport long enough to open it and find a page to stamp. It was my first time in a country that didn't speak English and wasn't terribly bilingual. Fortunately the airport was signed in English as well as Spanish, and the information/assistance people all seemed to be able to speak English. I arrived in Terminal 1, and the European contingent were mostly arriving at Terminal 4, which is essentially a completely separate airport, a short shuttle bus ride away. My flight arrived in the morning, and I had about 4 or 5 hours to kill before the first of the European contingent rocked up. It was tempting to get a train or taxi into Madrid and have a bit of an explore, but I really didn't want to risk not getting back in time, so I just loitered around Terminal 4 for the time. The highlight of the waiting was I bumped into Doug Foster, who I used to work with a SecureNet in Canberra, disembarking a flight from London (where he's now working). It really is a small world. After everyone turned up, we got on a bus and headed for Badajoz, a mere 5 hour bus ride away. We didn't get away until about 7pm, so by the time we hit the road, it was dark, so there wasn't a lot to see. We arrived at Badajoz around midnight, and made a short walk to the hotel and had a late dinner and hit the sack. Unfortunately with all my travelling in the three weeks, I'd managed to come down with a cold, which started manifesting itself pretty much from the moment I got to Badajoz, so I started to feel increasingly suboptimal as the week wore on. Badajoz itself is an incredible little city. It's just like what I envisaged an old European city to be: narrow winding streets. It had a funny effect on me. I'd alternate between finding it really quaint, and incredibly claustrophobic (and I'm not usually the claustrophobic type). After doing a bit of self-analysis, I think the problem was the lack of sky. With so many buildings crammed in together and the narrow streets, the amount of sky you got to see was minimal. Definitely no horizon. I felt more comfortable at night, in fact the place looked really awesome at night. Everything was lit up, I think especially so for Christmas, and everyone came out and walked around and did shopping. The other thing that, well, I noticed about the city was that it was wall to wall concrete (or bricks, or bitumen). The buildings all connected up, there were no gaps between them, and the sidewalk basically ran from the front edge of the building, to the kerb, then there was the road, and then the reverse, so it was a real concrete jungle. That said, it was pretty clean. the sidewalks were all swept, there was no rubbish in the gutters. By about the second day, my cold had driven me crazy (my nose was running incessantly) and I just wanted some pseudoephedrine to dry it up. I didn't have a clue how pharmacies operated, but fortunately I was able to get Miriam to tag along with me, who spoke English as well as Spanish. She'd never heard of pseudoephedrine before, but as soon as she said it to the pharmacist, he knew what it was and came back with some form of Nurofen (ibuprofen) that also had pseudoephedrine in it. I didn't really want or need the ibuprofen, but when sick in Spain, beggars can't be choosers, so I took it. I didn't feel that it did a great deal for me anyway. Getting home again was fun. Due to various peoples' flights, the bus was leaving at 6:30am, and that wouldn't get me back to Madrid the ideal 3 hours before departure, so I took a taxi with a few people who needed to be there earlier. It left Badajoz at midnight, and arrived at Madrid at about 4am, where I had to wait for about 5 hours before I could check in for my flight. I had a bit of fun leaving, which I've already written about, and was happy to get home late on Sunday night. My cold had gone to my chest by this stage and I had bronchitis, so I was just glad to get home and see a doctor on Monday. So now I can say I've been to Europe. It was a shame I didn't get to see Madrid itself. Next time. Update Photos from the trip are here

Martin F. Krafft: Credit card verification codes

There once was a credit card number tied to a name and when it was abused, the credit card company decided to tie it to an expiration date. It didn't take long until gifted hackers found out that twelve months and an average life cycle length of two years required them to check each credit card number against the 24 possible expiration date month-year pairs, so the credit card companies also required the billing address to match (at least fuzzily). Unfortunately, many of the companies accepting and storing credit card data are run by clueless people and the data sets of names, numbers, expiration dates, and billing addresses leaked, causing even more organised abuse. The credit card companies did not like that and proceeded to invest tiny amounts of additional energy and manpower into improving the status quo. So then, one day, in the dungeons of the credit card company offices, a bright young graduate from one of the American elite colleges yelled "heureka" [*] and outlined how to secure credit cards with the "credit card verification code" (CVC), printed on the back of each card printed, not stamped like the number. Maybe his/her theory was that the stamped number could be read from both sides, so a printed CVC would only be readable from one side of the card, bringing instantaneous 200% security increase. Maybe it was some other theory. In any case, the companies readily adopted the CVC and by today, every web form will ask you to also enter the CVC. They'll probably store and leak it too. What's next? Credit card colour?
[*]"Heureka" is Greek for "this bath is too hot" [Dr. Who].
NP: OSI / Free Update: Andrew Pollock points me to the Wikipedia article on CVC as good reading. Indeed, the article explains security benefits in face-to-face transactions and in the socalled "card not present" situations, like ordering over the Internet. Apparently the CVC must not be stored, so in some ways they have learnt from the past. I know of at least one merchant in the US who stores the CVC in my profile though. Update: Mark Brown adds: "The CVC is being used because it defeats attacks like taking a photo of a card with a mobile phone: it makes it usefully harder (not impossible) for people to transparently clone cards." This squares with the Wikipedia article.

Eddy Petrișor: New laptop #1

I am in search of a new laptop and this is difficult.

What I (know I) want:
What I don't know for sure aka "help lazyweb":
Dear lazyweb question:

David Moreno Garza: Planning trip to DebConf7

I’ve also started to look for the best plan to reach Edinburgh next June. I don’t think I’ll fly directly from Mexico City, since I want to visit Paris (in spite of my previous and only experience with CDG back in 2005 :-P ) and then visit a nice friend in Bilbao. Then I could fly from there to Edinburgh or some place nearby with a cheap flights airline.
Quick searches throw an estimate of 1′150 USD for the trip MEX-JFK-CDG-JFK-MEX on Delta. Fortunately, I’ve started saving already, so I don’t get pressure on money once DebConf gets closer. I still don’t know anyway if this could be the best way to travel. I’ve been suggested, also, to travel from Canc n to Madrid through Air Europe, with the cost of ~515 , which is way more cheap than to fly to Paris, but I should also pay for the transportation from Mexico City to Canc n and from Madrid to Paris, if I really want to visit it, which I do. Anyway, the cheapest flight I could get directly to Edinburgh is ~1300 USD: MEX-ATL-EDI-ATL-MEX, with Delta too. Any suggestion on the matter is welcome and appreciated.

Michael Janssen: Apparently, I'm flexible.

You scored as Either. You brain is neither specifically male, nor female in the way you perceive your surroundings. As bad as this may sound to some, it can easily mean that you are capable of combining both gender aspects to your advantage. Rather than being genderless you are possibly able think freely. This does not mean that you are bisexual or androgynous or indecisive, but it might.

Either
64%
Male
57%
Female
43%
Neither
18%

Should you be MALE or FEMALE?*
created with QuizFarm.com

This quiz was blissfully short. I've seen ones at quizfarm go hundreds long. I love the "this does not mean xxxx, but it might" complete cop-out.

Russell Coker: document storage

I have been asked for advice about long-term storage of documents. I decided to blog about it because my thoughts may be useful to others, and because if I get something wrong then surely people will correct me. ;)

Many organizations are looking at using computers for storing all documents. This gives savings on the costs of storing paper - the promise of the paperless office is being fulfilled. There are some potential issues about whether a signature in a PDF file that's scanned from paper is valid - but I guess it's the same as a signature on a FAX and everyone seems to accept FAXed contracts.

The technical problem is how to reliably store data long-term. The problem is that all modern methods of storing data will degrade over time. Anything less than engraving a message in stone, gold, or platinum and burying it will have some data loss eventually.

If the documents that need to be archived have no special requirements and if you have a good backup system in place (testing backup media, off-site storage in case of disaster, multiple sets of hardware that can read the backup media in case of hardware failure, etc) then you might be able to just store the documents on a server and include them in the backup plan. The regular backups should cater for replacing media over the long term. If however there is a significant amount of data or the data has confidentiality requirements that preclude having it all online all the time then you need a separate infrastructure for such storage.

Regular backup systems have to deal with files being deleted from storage and files that have their contents changed. For a document archiving system no file will ever be changed once it has been created and no file will be deleted. This allows some simplifications to the backup strategy. For example if you have multiple terabytes of documents backed up by tape and stored off-site you could use CD-ROMs or other media for storing recent changes. It would be very easy for an employee to grab a couple of CDs before rushing out of a burning building, but grabbing a set of tapes (or the correct tape from a large set) may not be possible.

It would be possible to use a tape library system as the primary storage for documents. If a large organization was going to implement this a few years ago that might be a good option. Nowadays storage is getting increasingly large and cheap. Terabytes are available in desktop PCs and hundreds of terabytes are available for server storage. So having the primary document store on a server with a decent amount of space and then making tape backups for storage in secure locations seems viable.

One thing to note about such document storage is that having everything on a server allows a much larger amount of data to be accessed and copied more easily than on paper. Sorting through a billion paper documents and copying the thousand most useful ones would be a difficult task for someone who was involved in industrial espionage. Finding the most useful files when they are indexed on a server should be quite easy and copying a few thousand is also easy (one thousand scanned documents of medium size should fit on a USB memory stick - much smaller than a few reams of copied documents).

Finally documents have to be archived in publicly documented file formats that can be easily read in the future. The PDF specification is well known and there are multiple programs that can display data in such files, another good option for scanned documents is JPEG. Proprietary formats such as MS-Word should never be used, you never know whether you will be able to read them in four years, let alone the seven years for which many documents must be retained or the 20-30 years that some documents must be retained.

Eduard Bloch: Just orphan by force

Yes Mark, your rant expresses well what I think. And also what I have said before but apparently not many people do care. I still think that we need a strong DPL or a special delegate with powers of orphaning packages by force, since sometimes getting a new maintainer is a step ahead no matter how much experience the new maintainer needs to have. Skills can be learned. But skills in the hands of an inactive maintainer is simply dead potential. Doing something somehow is sometimes better than not doing anything. A such hypothetical delegate would need to have the right nose to detect such cases and orphan such packages. No matter how important this package is - bugs are bugs are bugs and they need to be fixed in a timely manner, ie. without unacceptable/long delays, no matter which RL problems of the particular maintainer do hinder him/her.

Marc 'HE' Brockschmidt: Debian's BTS still sucks

In response to my rant about Debian's BTS, I got some mails about other project's handling of bug tracking system - I'm still looking through those.

More interestingly, Joey Hess blogged about it and defended keeping old bug reports - which I also think. I explicitly talked about bug reports with no activity and no maintainer reaction. I took the time to look at some of the bugs Joey submitted and found some good examples for bugs and packages that obviously need help.

230485 is now in the ripe age of nearly three years. Almost three years is also the age of the last mail to that bug report, which was one maintainer setting the severity to important, without a comment. Since then, there has been no note if this bug is going to be fixed, how, when, why and who is going to do it. A user might get the impression that the maintainer simply doesn't care about this (or other) bugs. That's not a good thing, I believe.

271752 is also a good example. The bug seemed to be unreproducible, now someone found a way to reproduce it and ... nothing happened.

206605 is also weird - a patch is there (and we're talking about little grammar change here!), but no upload actually included it. Without a comment why it is not happening...

Keeping old bug reports to inform users of existing problems is OK. But not fixing bugs (or even trying to fix them) is a problem!

Bernhard R. Link: clean vs. crowded bug pages

Marc Brockschmidt wrote the BTS is too crowded and Joey Hess objected that a too clean BTS can also be a bad sign.

I think both is true or to say better none of the ways makes sense without the other:

Bug reports are in my eyes one of the most valueable resources we have. Noone can test everything even in almost trivial packages. To archive quality we need the users input and a badly worded bug report is still better than no bug report at all. Our BTS is a very successfull tool in that as it lowers the barrier to report issues. No hassles to create (and wait for completion of) an account, no regrets by getting funny unparseable mails about some developer changing their e-mail addresses (did I already say I hate bugzilla?).

As those reports are valueable information, one should keep them as long as they can be usefull. Looking at the description of the wontfix tag shows that even a request that cannot be or should not be fixed in the current context is considered valueable. Most programs and designs change, and having a place to document workarounds and keep in memory what open problems exist.

On the other hand a crowded bug list is like a fridge you only put food into. Over time it will start to degrade into the most displeasing form of a compost heap. The same holds for bug reports:

Most bugs are easier when they are young: You most propably have the same version as the submitter somewhere, know what changed recently and when you can reproduce it you get some hints on what is happening and get add it. If you cannot reproduce it, the submitter might still be reachable for more information.

When the report is old, things get harder. Is the bug still present? Was it fixed in between by some upstream release? Is the submitter still reachable and does still remember what happened?

When I care enough of a problem to write a bug report and trying to supply a patch for it, I try to always take a look at the bug list and look for some other low hanging fruits to pick and submit some other patch, too. (After all, most of the time is spend trying to understand the package and the strange build system upstream choose instead of plain old autotools and not when fix the problem). But when it is hard to see the trees because of all the dead wood around it, and there is nothing to find with some way to reproduce it and one knows far too well that the most efficient steps would be a tedious search for old versions to see if that was a bug solved upstream many years ago, good intentions tend to melt like ice thrown in lava.

So, when I wrote both is true I meant that keeping real-world issues documented and aware is a good thing. But having bugs rot (and often they do), will pervert all the advantages. In the worst case, people will even stop submitting new reports as it takes to long to look at all the old ones to look for a dublicate.

Stefano Zacchiroli: ocamlnet 2.2 in experimental

Ocamlnet 2.2: test it by yourself from experimental A couple of days ago I finally managed to complete the packaging work of Ocamlnet 2.2. This upstream version is a (r)evolutionary release in which it aggregate in a single source package libraries who used to be distributed separately, namely: equeue, ocaml-rpc, netclient, and ocamlnet itself. I've been quite surprised to discover that upstream is explicitly nice with us packages and provides guidelines on how to split the various libraries in binary packages addressing both dependency and licensing problems (e.g. for nethttpd which is GPL and can't be shamelessly linked with other components which are MIT/X11-licensed). The packages are in experimental but need NEW-processing, as well as cryptgps (a pure-OCaml implementation of some symmetric crypto algorithms, which is a new build-dep of Ocamlnet). Hence to ease testing I set up an apt-gettable repo here:
deb http://people.debian.org/~zack unstable ocaml

Please try it and give feedback to debian-ocaml-maint@l.d.o. In all my tests the upgrade from ocamlnet pre-2.2 has been smooth: the (too many) transitional packages I had to create did their dirty job. The only "issue" non-addressed (and I don't know how to actually) is that the nethttpd library used to be distributed in libocamlnet-ocaml-dev and is now distributed in libnethttpd-ocaml-dev. Since the former package is entirely useful without the latter there is no dep among the two and it's possible that upon upgrades an user ends up without a working nethttpd library on the system. I added a Recommends in the hope it's enough, let's see how many complaints I will receive ...

Rudy Godoy: News and more news

Seems that I manage to publish yearly news. Well this time I've many of them. DebianPeru's event videos.
As promised, we've published the videos for our D aDebian 2006 anual event. You can find the event videos and also the lightning talks videos.
I want to thank our sponsors and people involved on producing them. We are already working on our next event which is mainly focused on attract, teach and involve more people on directly contributing to Debian and free software. Talking about Debian events and user-base growth, when I went to the place to make stickers for give out on our last event, I went with the swirl logo and said to the business owner: I want to print this. He said ok, and later he asked me: is it Debian right? I was like... yes!. Later we talked a bit more and he told me that he found Debian on the Internet while looking for alternatives to have his business run safely, since, as he related me looking worried, the police came to their place and seizure all the computers from other businesses claiming that they are running "pirated" software. So he found Linux and Debian. He told me that was having some issues with their devices, mostly his CD/DVD printers and scanners. We talked a bit more and I invited him to our local group and the event of course. It was a very cool incident, and I nominated him our official merchansiding supplier ;) Debian gaining market share.
Last year was quite good for Debian in Peru, besides the growing user-base, some government agencies have explicitly named as the operating system or linux-flavour they want third party deploy for them. One of the most important cases, IMHO, is the PDT software, which is the program that every business should use to submit taxes information. Currently it's only available for Windows and it's written in Visual Basic. Although, mostly because it's lack of stability and extensibility by third party, some government agencies have been pushing for SUNAT open it's source code. It was, as with many other out of place subjects, source of lot of flames and irrelevant waste of time by the local linux-supporters. Anyway, they didn't open the software, but instead they called for software vendors to compete for the development of a new version which should be multi-platform and according the specs at least run on Windows, Linux and Mac OS X, and on the Linux side they mentioned specifically that the program should be apt-get-able, thus vendor should provide a Debian package compliant with 3.0 or superior. Microsoft loves Debian.
I was invited to, which was meant to be, the true and first Microsoft vs. free software debate in Peru, but was, as we in APESOL have experienced for years: Microsoft refusing to debate. So it was mostly APESOL being technical, as requested by orga, and Microsoft being funny. I was astonished that almost half of Microsoft speakers mentioned Debian at least 5 times in their talks and dedicated almost half of their time to talk about free software (open source), interoperability and technological neutrality. It was fun for me to see them helping us to get known. There are some pictures on my flickr page. Personal life and Debian work.
Last year I've lost my two cats, both died in not a very good way, they are missed for sure. I'm sure I want a full white one, but not sure how soon. I've been really busy working on my business which led me to not being able to contribute as much as I wanted but I managed to do some stuff. In the other hand I've learned many important things that we, as free software community should seriously consider. Most of them have been already pointed out by some people on p.d.o already. Ok I believe this is enough, blame this to the not-blogging-for-long-time syndrome due the commies hidden over there locking my access to former hosting.

Andrew Pollock: [life] Children of men

It's been ages since we've been to see a movie. Tonight, we went to see Children of men, a movie I've been looking forward to, since I saw the trailer I'd seen some reviews that sounded like they were canning it, but in my opinion, the movie didn't disappoint. It's another one of those studies of a not-too-distant future, where the world has gone to pot and Britain has prevailed. Like V for vendetta, I think it was a thinly veiled parody of the United States taken to the extreme. I really enjoyed the movie. It had a few humorous moments, and an interesting twist about half way through. The two hours went very quickly. Update Completely forgot to note that I saw trailers for these movies, which piqued my interest:

Evan Prodromou: 15 Niv se CCXV

We got back to Montreal yesterday morning just after midnight. Maj got us upgrades on United to business class, which was really a life-saver. There's a direct flight from San Francisco to Montreal, but it's 5 hours one way and 6 hours on another. This time traveling to California, we decided to split up the flight, stopping in Chicago about halfway between. Returning was a good flight. We were comfortable, there was room, Amita had enough space to play on the ground and sleep comfortably on our laps. Maj: "Business class isn't anything fancy; it's just enough space, good service and quality food that you feel like a human rather than like livestock." The only downside was that Chicago O'Hare is a half-ass airport. For one of the most (the most?) visited and transited airports in the world, it's really skimpy on services inside the security area. There aren't any big restaurants or nice bars or stores inside the B and C concourse; just stand-up kiosks. We walked halfway across the airport to find a pub to eat at. Probably the best thing about the airport is the giant brachiosaurus skeleton in B concourse. Amita June couldn't stop looking at it; she ran from foot to foot banging it with her hand. Good for her; it's a pretty neat thing to see in a boring airport. tags:

Ebjo Another Maj quote: "It's just a coincidence that we use the term blog as a cutesy contraction for 'Web log'. It could have easily have been a 'Web journal' people were contracting, and then we'd call it an ebjo." tags:

Goethe One of the things that I've found as a participant in Open Source software and Open Content is that there are a lot of different people involved. And today, in 2007, Germany and France have become important loci of new developments in Free Culture. I've been working on my French for a while, and I think I'm getting pretty good, but I've never learned any German. At all. But German Wikitravel is one of the largest and most popular versions of the project. And I want to be more of a participant -- or, at least, have some better relationships with our German users. So, today I signed up for German lessons at the Montreal Goethe Institute. The Goethe Institute promotes German language and culture world-wide, including high-quality lessons in German. Montreal's is in a beautiful old building right at the corner of Sherbrooke and St. Denis. It's got a nice office and a friendly warm bookstore, "Das Buch". I'm going to take the intensive beginner's course -- mornings Tuesday and Thursday for 6 weeks. I hope at the end of that time I'll be better able to meet German-speaking Free Software advocates, Open Content participants, and most of all Wikitravellers a little more towards halfway. tags:

La ka I went to La ka this afternoon again to meet a couple of people. It was my first two-meeting day at La ka, which I think is a bad sign I'm turning into a serious maven. But like they say, it's really where the hipsters are doing business on this le lately. The nice thing was that I got to introduce two Montrealers that I like a lot. Hugh Macguire of, among other things, the Librivox public-domain audiobook project, is really interesting and passionate about communities and free content. Nicolas Ritoux is one of the most clued-in tech journalists I've met. It was nice to introduce them, and it was good that they seemed to get along. Depressing, on the other hand, was walking around the Plateau in January with 12C weather. This has gotten beyond funny into scary -- we just haven't had any serious snow in Montreal this winter. I'm worried that it's going to get worse, too, and I don't know what that will mean for Quebec's culture. Mon pays, c'est l'hiver, goes the song, and I'm not sure I get what a city without winter would mean here. tags:

House Maj and I have been watching House on DVD. It's really good, although a little formulaic. Everybody's always running around and bleeding and vomiting, and people get an average of 3.8 different rare diseases per episode. There's also a lot of cheating and sneakiness. It's great. tags:

Mantini One nice thing about New Year's Eve this year was that Baron Earl served a refreshing -- nay, energizing -- spocktail called a mantini. I was especially pleased to find out that the first ingredient was not, in fact, a praying mantis. With the Baron, you never know. tags:

Joey Hess: a clean BTS is a sign of a sick mind

Marc, I disagree. Solving every issue and whim that every user files against a popular package, while not letting the package degenerate into a mess, is hard. Taking some time to gather opinions and produce a well-designed fix that strikes to the core of an issue, rather than treating symptoms, is a good thing for many classes of bugs. (Other classes should instead be fixed immediately.) The existence of many open bugs against a package in Debian is not an indication that it's of lower quality than the corresponding package in Ubuntu -- which in fact probably has 99% of the same bugs anyway. As a user, I also regard a BTS as perhaps the best form of documentation there is about real-life problems that I might encounter while using the package, the general quality of the code in the package, etc. It's the first thing I look at when installing some new peice of software. It's also a good way to gauge how well the package is maintained -- not by counting bugs, but by reading how the maintainer responds to bugs. What I look for in a BTS is an indication that the maintainers care about a bug. The fact that bug #725 took ten years to get fixed doesn't mean that X's maintainers suck, it means that for ten years, we were able to document a minor problem to the few users who cared about it, and that we were able to keep track of it until someone finally figured out how to fix it. That's quite an accomplishment. Another example, to keep picking on X, the fact that bug #216933 is marked wontfix is not an indication that the bug is worthless; in fact the bug documents a quite subtle issue in the Crusoe's code morphing software, and has been an invaluable reference to a lot of Crusoe users. I'm much more concerned about all our users who don't know about the BTS and are unwilling to bother to file bugs than I am about the total number of unfixed bugs in the BTS. Getting 100% of our users to file good bugs on every issue they run into would do much more to increase the overall quality of Debian than fixing every > 1 year old bug in the BTS would.

Marc 'HE' Brockschmidt: Debian's BTS sucks

Blogging is hard, isn't it? Finding a topic that's not better placed on specific mailing list or somewhere else is not easy. One of the classical subjects for bloggers is ranting. And that's what I would love to do now :-)

I have had discussions with people who are turning away from Debian in the past few months, mostly to Debian derivatives like Ubuntu. Mostly, the reason for that is some sort of software that is newer/better supported/blabla in some other distribution, which I think is OK. Debian has a policy of a long, painful release cycle, but the stable releases that come out of it tend to be useful for a long time and relatively bug-free. That is good and shouldn't be changed without good reason.

Most of the people I spoke too revealed a far more disturbing thing: The long release cycle isn't the only argument against using Debian. Most of these people had other reasons, and a good number of those are things that Debian as a whole can - and should - address. Mostly, the Debian BTS comes up as a topic. Not because we don't use the Industry Standard [tm] bugzilla (which I personally hate so much I can't even describe), but because the BTS contains a lot of old bugs nobody cares about. Look at most of our packages: Bugs filed 7 years ago, with the last activity from that time, without a hint how (and if) they are ever closed are not uncommon; they are what you actually expect if you look at a bug list.

Naturally, processing, forwarding and closing bugs is the task of the maintainer. This doesn't work out in all cases, we have more than one cases where maintainers are overwhelmed by the sheer number of bugs flowing in against their packages. Also, and that is probably accepted everywhere: Bug processing is uncool. It is so much more fun to rewrite your code, add features, get new packages in the archive and doing new, blingy stuff, that the boring maintenance work of existing packages moves to a place far down on the todo lists. But hey, this maintenance. That's what maintainers are for. Most Debian Developers are Package Maintainers. They should do it, not adding new stuff.

We need to discuss how to work around these issues. We are not the only project which an overfilled bug tracking system. Look at the Gnome and KDE projects, the number of bugs filed against Mozilla products each day. Can we learn something from them? I would be happy to get a bit of feedback about this, so whoever is involved in other projects which have found better days to deal with bugs, please send a mail.

Apart from the fact that I would love to get more input on this, I want to start something new for lenny, the stable release planned after etch. I want to get the bug count down. Not the release critical bug count (which is eagerly watched all the time), but the small issues that bug users every day. For that, I have planned to look at 5 random important and normal bugs each day (starting with software I use) starting the day etch is released. I may begin to do this earlier, but I'm currently really not swimming in free time.

I don't plan on fixing all these issues (well, I may, if I can easily reproduce them), but more on forwarding them to the appropriate place, upstream, and noting so in the BTS. I want to poke maintainers long enough to invest some more time in fixing bugs. This will also help with the MIA efforts of the QA team, I guess...

Oh, what I almost forget: I expect help from all of you!

Next.

Previous.