Search Results: "ag"

26 July 2007

John Goerzen: OSCon and Portland Photos

I've taken my camera around OSCon and Portland a bit. Here are a few photos that I've taken so far.

At OSCon Itself

(click here to see all)

img_3165

Overflow from breakfast. Most tables had powerestrips and laptops on them.

img_3204

Debian booth at the expo hall. And the only one with beanbags. Sign reads "The developer is in."

img_3166

Filing in for the keynotes. Everyone seemed to want a seat either at the very front or very back.

img_3177

Simon Peyton-Jones explaining how locks with traditional threading can be improved upon with transactional memory.

img_3202

Run for your life! The bell will attack at any moment!

I didn't hear it ring all week.

Around Portland

(click here to see all)

img_3127

The Japanese Gardens were beautiful and tranquil. Jacob actually feel asleep while being rolled around on his stroller.

img_3145

For some reason, this one reminds me of the Jedi Academy in one of the Star Wars video games.

img_3118

One of the many bridges in Portland.

img_3164

Terah's favorite find: Sweet Masterpiece Chocolate and Coffe.

We went there after the Blossoming Lotus Cafe, which was an interesting experience but not quite as good as I had hoped.

Bdale Garbee: SPI Board Election

All contributing members of SPI should make time RIGHT NOW to go vote in the SPI Board Election currently underway. We have 13 candidates from a variety of SPI's associated projects running for 6 open seats this year. The election closes at 2007-07-28 23:59:59 UTC, so don't delay!

Simon Huggins: Debian Maintainers vs New Maintainer process

Sorry Bastian, but your "Why don't we aim for something simple, like improving our New Maintainer process." seems a little na ve. People have tried to improve (read, mostly speed up) NM for years and I don't believe the blockers are particularly simple to solve. We want a rigourous NM process adn we're a volunteer project so it's hard to do quickly. I know some talented people who have to be sponsored which means waiting on others being available. I know I've failed them at times when my life has been busy and I've not dedicated as much time to Debian. The DM proposal is a great way to get valuable contributions into Debian sooner without people losing interest in the project all together. The other issue anyone considering voting against the DM proposal should bear in mind is that it's going to be easy to remove people from this keyring if you have a decent reason. I really can't see any downsides.

Ross Burton: Devil's Pie Tutorial

Christer Edwards over at Ubuntu Tutorials has written a short tutorial on Devil's Pie. Thanks Christer! Now if only people would stop using a hack I wrote several years ago and fix the real problems... NP: The Last Flowers from the Darkness, Mark Van Hoen

Raphaël Hertzog: Some changes concerning DSA

Since march the DSA team uses a request tracker to handle all the requests that they get. Therefore you should no more use the debian-admin@debian.org alias (DSA members only). The debian-admin@lists.debian.org mailing list (DSA + local admins) is also scheduled for removal. Instead you should mail admin@rt.debian.org making sure to put “Debian RT” somewhere in the subject (crude but working spam prevention). By default, your ticket ends up in a private incoming queue. Up to now only DSA members had access to those queues. They moved most tickets in the public queue but it happened several times that this simple administrative burden took several weeks. Since a few days, Matt Taggart and myself have been granted RT accounts with required privileges to handle tickets and move them between the various queues. So from now on, all tickets will be quickly moved in the public queue (when they don’t contain sensitive information of course). We’ll be able to do some triage and ping DSA members for urgent requests. Matt and me have been trying to help out the DSA team for quite some time now, and while we’re not DSA with root rights, we’re in regular contact with the members (except Martin “Joey” Schulze who refuses to join the DSA IRC channel, who doesn’t use the request tracker and who doesn’t read the DSA mails either) and with several local admins. So if you have some troubles interacting with the DSA team, you can try to get in touch with us and we’ll see if we can help you. In too many cases people contact directly individual DSA members (Joey in particular). Please refrain from doing so, other volunteers (who might help you) won’t notice your request. Furthermore systematic request tracker usage helps us identifying what is well handled and what’s not. And it’s not more complicated than a simple email for you. Update: currently local admins are not subscribed to the request tracker. The RT setup will need some further adjustment for that, so the debian-admin@lists.debian.org list can still be useful if you want to reach them.

MJ Ray: Bradley Wiggins Should Have Stayed in Race, According to UCI President

OK, this is probably my last Tour post for a while... back to business, software and the village after this, but I heard this on the radio over breakfast and I can't see much about it online. One of the most disappointing things for English Tour fans about Moreni's failed dope test [tdfblog] is the departure of his Cofidis team-mate Bradley Wiggins from the race, days before the last (and most Wiggins-winnable) of the individual time trials. In an interview this morning on BBC Radio 4's Today Programme at about 07:45 (in case you can Listen Again to it), there was the question:
"We've had whole teams withdrawing. It's not just the two who test positive. It's the sense that those are the tip of an iceberg, isn't it? The whole team pulls out and you don't really know how many others in that team are affected by the same behaviour."
and UCI president Pat McQuaid answered:
"Well, I mean, the fact that the whole team pulled out is something which the UCI is quite annoyed about, in actual fact, and it was that the organisers asked the teams to pull out. It wasn't the fact that the teams pulled out of their own accord. The organisers said to them, as a result of the positive, that they got the one person and they said they want the whole team out of it. That actually goes against the rules and it shouldn't have happened. Erm, so, from that point of view, you can't put anything on the other riders. You can't say that the other riders are up to anything just because they're not in the race. They were asked by the organisers to get out."
The interview continues to point out how there's much more testing in cycling now than ever before, and more than in any other sport (remember, Puerto implicated footballers and others too), but it's interesting how the whole-team-out approach is criticised for removing the other riders on a team from the race testing! Anyway, by the UCI president's reasoning, Bradley Wiggins should still be racing. Well done to UCI and the tour for catching Moreni and almost-well-done to Moreni for admitting it, but boo Cofidis for pulling the whole team out! (2007-07-26: +1 comment)

Simon Richter: Compiling compilers

I've spent a few days with the gcc package now, trying to get them to a point where cross compilers will be sanely autobuildable. I'm going to let the dust settle for a few days (and give my script time to catch up) now, and then send patches if they work. The stack smashing protection (and the fact it is enabled by default on Ubuntu) sure make things interesting.

Russell Coker: Train Routing

Last year I spent several months living on one side of Melbourne and working on the other and travelling by train to work. Every day I had to catch two trains each way with an average wait of 5 to 10 minutes for each train to arrive giving a total of at least half an hour a day spent waiting for trains. The obvious solution to this problem is to have trains not go back and forth on one line but instead go from one side of the city to the other. This map shows that there are 14 train lines out of the city with about 5 major lines. The smart thing to do would be to have every major line have one train every 5 minutes during peak hours and to have every train go back out on a different line. Then if you are on one of the major lines and want to travel out on one of the other major lines then every 20 minutes there would have a train that would take you straight there without changing trains! Currently we don’t even have such frequent trains, during peak hour the trains on most lines run no more often than 5 per hour, the Sydenham line has trains 4 times per hour during peak hours and the trains are crammed full before they get half-way to the city. If the trains ran more frequently and were routed through the city then commuters who travel through the city would save 20+ minutes per day without going to any effort and 30+ minutes a day if they chose to start their journey at a time to avoid changing trains. This would be a significant incentive for catching the train instead of driving! For the commuters who travel to work via a single journey then having trains run every 5 minutes at peak times would mean that an average of 2.5 minutes was spent waiting for a train each way (an average of 5 minutes per day) instead of the current situation of 15 minutes per day or more. This would mean triple the number of trains on the Sydenham line which may sound excessive. However the trains are currently so crowded that there could be twice as many trains and all seats would still be full. If there were three times as many trains then I expect that more people would catch the train (surely some people would be convinced to drive to work by the idea of spending 20 minutes with barely room to stand), it’s not inconceivable that there could be three times as many trains and all seats could still be full! The next issue I have been considering is the time taken for a tram ride to/from the central city areas in peak hours. Peak hour trams stop at every stop because there are always people getting on and off. If a tram could stop less frequently then it could make a slightly higher average speed. One way of achieving this would be for the peak hour trams to stop at every second stop outside the center of the city. On the way in half the trams would accept passengers at each stop (each tram would be designated as either odd or even and labelled as such - the tram stops are already numbered). But if you have twice as many trams then the average wait would be the same while the duration of the trip would be reduced. On the way out of the city the tram driver would announce that after stop 10 (to pick a random number that might work) the tram would only allow passengers to get on or off at even/odd stops. If you knew that your stop was on an even number and the tram was an odd-numbered tram then you would change trams to an even tram. The small delay in changing trams would be made up by a faster trip overall. Politicians are always talking about ways to alleviate the water shortage caused by climate change and to improve the economy. Having people spend an extra 10 minutes a day working because of saved time on the trains would help the economy. Encouraging people to catch the trains via more frequent and efficient service as well as less overcrowding would help reduce climate change - which is the best way of improving our water supply and the only way of helping the farmers long-term!

Bastian Venthur: On Debian Maintainers

When voting on the current Debian Maintainers General Resolution, I think it’s worth to think about the following questions: What is the difference between a Debian Maintainer and a Debian Developer? Who is interested in becoming a Debian Maintainer and not a Debian Developer and why? Will this Debian Maintainer class really improve the situation for New Maintainers? I suppose most of our New Maintainers will aim to become a Debian Maintainer just to bridge the time until they’re full Debian Developers. And I predict that this is also the major target audience for this new Debian Maintainers class. Some people said on -vote that there are people actually interested in becoming a Debian Maintainer and not a Debian Developer. Personally I find their reasons questionable, but after all I suppose there won’t be many people going this route. On the other side, I don’t see how this new class enhances the situation for the New Maintainers. Now they not only wait for the Application Manager, Front Desk and Debian Account Managers — No, now they will also search for someone who advocates them to become a Debian Maintainer and have to wait for their key being added to the Debian Maintainers keyring. So my question is: If this General Resolution mainly helps New Maintainers, why must it be so complicated? Why another class of contributers, all those complicated rules to set it up and this additional layer of bureaucracy? Why don’t we aim for something simple, like improving our New Maintainer process. I would rather see some of those Debian Maintainer rights granted to New Maintainers after a certain point in their New Maintainer career, but not in this complicated and overengineered way the Debian Maintainer class proposes.

Daniel Burrows: Do not install aptitude 0.4.4-4b+1!

Apparently someone decided to resolve the dependency problems with aptitude in unstable by doing a blind recompile and NMU of the package, presumably because of my horrible laziness in not doing an upload to unstable yet. The problem, as I wrote in the bug reports regarding the need for a recompile, is that this produces a package that's totally unusable, which is why I didn't do it myself. If you are running unstable, you should either not upgrade the apt system, or install the experimental aptitude (either using "apt-get install aptitude/experimental" or by going here). These packages are not perfectly stable, but they also aren't totally unusable.

I apologize for the inconvenience -- if I can get some time this evening I'll rebuild the aptitude in experimental and throw it kicking and screaming into unstable.

Martin F. Krafft: A new list: mailtags

I've received a fair number of responses to my previous blog post on labelling/tagging mail and have created a list for public discussion of the topic. Please subscribe if you're interested in this topic. I am also trying to get permission to repost some of the responses I got there. Furthermore an update of my blog post with some of these comments is pending. Busy times NP: Dredg: Catch without Arms

Mike Hommey: Firefox Foundation

So, after having dumped Mozilla Suite, the Mozilla Foundation is now pushing Thunderbird out to pursue its goal of an “open web” (understand: MoFo only cares about Firefox). Why is it called the Mozilla Foundation, again ?

John Goerzen: OSCon Wednesday Part 2

After today's keynote session, I met up with Simon Peyton-Jones and Bryan O'Sullivan. A vibrant discussion with these two Haskellers. We had all noticed that Haskell, and FP languages in general, have been doing really well lately and mused about why. Perhaps it's that people are becoming more used to functional approaches to problem solving because popular languages include some of them these days. Or perhaps it's that FP already has tools to solve problems that are suddenly hot, such as parallelization.

In any case, Simon's Haskell talks have really been highlights this week for many.

I had some time to visit the show floor. Stopped by the Debian booth and met Steve Langasek. A couple of Sun guys dropped by to talk about trademarks with OpenJDK. Bart Massey of Portland State Univ. also dropped by. I've conversed with him in email a few times. We talked about what PSU is doing with Haskell, some of the code I've written, and some of the code they've written. They're doing some fun stuff with rocketry and software-defined radio.

Oh, attended Simon's talk on nested data parallelism, which he is working to add to GHC. That sounds like a very interesting topic. Think list comprehensions, but the compiler automatically parallelizes the task for you.

After the conference's events, went out to dinner with some local (and some conference) Haskellers. That was a lot of fun, and Terah and Jacob got to come along too. People are doing some interesting stuff with Haskell.

MJ Ray: The Dopey Tour de France

After my comments about the TV audience figures, Ismael Valladolid Torres commented:
"Audience in Spain will keep on raising while Contador keeps playing such a big race!"
I hope that's still the case after the recent revelations. The evidence suggests that Vinokourov had someone else's blood [tdfblog] and Cofidis's Moreni was using something like a nutsack patch [tdfblog] while Rabobank have fired race leader Rasmussen for telling them he was in Mexico when he was in Italty [tdfblog] so it looks like this year's race is still really unpredictable as the dopes are caught and kicked out. Maybe my hopes for a Valverde (now 6th, 10:18 back) win still stand a chance... (My "serious" prediction, Kl den, left with Vino.)

Christoph Berg: The DM GR

I haven't said anything in the DM threads yet because I still don't know which actual problem the introduction of DMs is trying to solve. IMHO the current process with sponsors reviewing and uploading packages has proven to work nicely, i.e. the amount of broken packages uploaded is not too high. Most of the perceived problems with this process stem from the fact that most of the packages offered on debian-mentors or #debian-mentors are initially crap and need lots of review cycles. Once people produce good packages asking the last sponsor for another upload should work. (And at that point NM will be a breeze.) Particularly I don't like the fact that the "initial policy for an individual to be included in the keyring" does not include any check of any technical or non-technical skills besides having a gpg key and be able to tick 3 checkboxes. I fear this will lead to people blacklisting "DM" packages because they don't want low-quality packages on their machines. At the same time, the rest of the GR text is micro-managing every other detail of the process in a way that doesn't leave much room for practical implementation decisions. It appears to me that the DM concept as sketched in the GR is mainly meant to let NMs upload earlier, i.e. it tries to fix the fact that front-desk or DAM approval take too long. I think the fix for that is just to find someone besides Joerg to also read the AM reports. DMs as in the GR are a workaround, not a solution. On a sidenote, I'm still wondering why front-desk (and afaict the DAMs) were never asked about their opinion while/after the GR was drafted. I had some chats with Anthony on IRC on the topic, but that was shortly after Debconf 6 (there was a related BoF), nothing in the past months. (not with the front-desk hat on, but having it within reach) PS: I voted "-1".

25 July 2007

David Moreno Garza: The White Camel Awards 2007

In the lands where the camel roams, the white (albino) camel is a rare and revered individual. The White Camel Awards recognize the many significant contributions made by the unsung heros of the Perl community. The efforts of these volunteers collectively make the Perl language and the Perl community better for all of us. – The Perl Foundation. 2007 Recipients
Allison Randal
Allison is at the center of the Perl community. She’s been president of The Perl Foundation, a leader and manager of various parts of the Perl 6 and Parrot efforts, as well a Perl author and editor. Her latest contribution to Perl is version 2 of the Artistic License, under which most open source Perl code, and Perl itself, is licensesd “under the terms of Perl itself”.
Tim O’Reilly
You may think of Tim as the guy who published Programming perl and Learning Perl, but he also kick-started the current form of the Perl community by giving it a place to come to together once a year. O’Reilly & Associates started The Perl Conference in 1997. Perl Mongers, the organization that helped start Perl users groups all over the world, started at that first Perl Conference. O’Reilly Media has been incredibly gracious and helpful to the Perl community.
Norbert E. Gr ner
Norbert help start the German Perl Workshop in 1999 and now is involved in several of the Perl conferences and workshops that take place in Europe. He’s the chair of the YAPC::Europe committee.

Russell Coker: Blogging Frequency

You may have noticed that my frequency of posting has increased significantly recently, and that my posts are generally at 7AM and 7PM. I am using the scheduled posting feature of Wordpress and writing my posts in advance (currently I have 8 posts in the queue including this one). Generally readers of my blog (particularly those who read Planet syndication pages) don’t want to read 5+ posts in one go. In the past I would write one post at a time and sometimes a couple of days would pass between feeling inspired to write. I had been writing text files and uploading them, but having a text file that’s 95% done is not the same as having a complete post scheduled to be released while I’m doing something else. This technique works for me, I encourage other people who have things to say but don’t seem to get around to blogging on some days to give it a go. Incidentally I chose the times 7AM and 7PM because the traffic to my site seems to peak between 7PM and 11PM local time (I haven’t analysed the logs in enough detail to determine whether this is Australians reading blogs after work or people in other countries doing it at work). To release two posts per day it seems most appropriate to space them 12 hours apart (and means that people in the same time zone as me can read a post before going to work).

MJ Ray: Reply of FSF Radio Interviewee about Skype

Peter Brown replied:
"Thanks for the message. Here are some comments on the issues you raise:
"> - On the Radio New Internationalist show "Up in Smoke", during an interview with Peter Brown of FSF (about 43 minutes in), I was surprised to hear the following revelation that FSF uses Skype and the failure to challenge the claim that Skype is free software:"
The FSF doesn't use Skype. I would appreciate if you would clarify that on your blog post. The interviewer used Skype to telephone me on an FSF telephone. I agree that from what I said, it would be easy to infer that FSF uses Skype, but it doesn't. The interview lasted about an hour and we covered a lot of ground. Also, in this exchange I didn't clarify for the listener that when the interviewer remarked that "Skype was free", they meant as in price, but not as in freedom.
"> - I was disappointed not to find much on the FSF web site about the need for free VoIP software, building on GNU oSIP and other free software, instead of Skype's proprietary software, which has contained spyware and worms already. Will you be adding such information soon? What is the official FSF view of Skype and similar proprietary VoIP systems?"
Skype is proprietary and we don't use it. In that section of the interview we were discussing telecoms monopoly and net neutrality, and I lost the focus on the free software issue - my bad. As far as adding an article about VOIP on fsf.org I think that's a great idea. Unfortunately, I don't think we can cover that immediately, as we have some campaigns we have other campaign activities to focus on. We would be glad to take a contribution though, if you would like to write such an article - we might also want to think about using such an article as a basis for a campaign.
"> - Nevertheless, well done for covering DRM, net neutrality and the privacy problems of Google, Yahoo! and Microsoft in a relatively short interview."
Thanks. I actually used to work at the New Internationalist in Oxford, and they are a great coop. I have been working with them now for a couple of years, tying to encourage them to cover free software related issues for their audience. Have you seen the article Bruce Byfield (Newsforge) wrote that I got placed in the November issue of the magazine? all the best peter"
Thanks for the reply! To my shame, I'd completely forgotten that Skype can also call ordinary telephones and the interview didn't remind me. I guess that might be because my main awareness of Skype is when it's a problem, when someone gives a skype: address instead of a sip: one or a real phone number. However, I'm not sure a called person would usually say that they were being called over Skype, rather than being telephoned. FSF people are smarties, though, so can hear the artefacts, or maybe the interviewer had mentioned it beforehand. Anyone else want to summarise the benefits of free software VoIP compared to Skype systems? I won't get time before next month. kris commented:
"There's openwengo, it has more features than skype (i.e. video), is encrypted, open and free. Enjoy."
I keep meaning to try openwengo, but each time I look at it, I fail to find the source tarball for the latest release. It also seems to be Qt-only, which I also try to avoid installing (as it'd be a fourth set of desktop widgets). At the moment, I'm using linphone from the command-line. I sometimes consider replacing it with a stand-alone telephone adapter. I wonder: are any running free software? (2007-07-27: 7 comments)

Ian Haken: On Power Outages and Package Building

I'm sure few would disagree with me when I say that power outages suck. But on the bright side it gives me a chance to test the resiliency of my server setup. I haven't bought a UPS yet, mostly because I'm waiting until my next bulk purchase of hardware.

When I logged onto my home system from the office ssh gave me a friendly notice that a new IP for this hostname had been added to the list of known hosts. This flagged my attention since although I have a dynamic IP with my ISP, they haven't given me a different one for months. But it's reassuring to know that the program for updating automatically the DNS entry is working. I quickly figured out that there was definitely something wrong when my screen sessions were gone and PIDs were small. Sure enough, w reports the system has only been up for an hour and a half. Good to know the Full On BIOS setting works as well. Really aside from losing screen sessions, there was no real notice of the power outage. Well, that and I had to reset my alarm clock when I got home.

But back to the topic subject of summer of code, vlosuts is just about out of alpha now. For anyone wanting to try it out, here's the set of commands that'll build and install the package.

cd /tmp
svn co svn://svn.debian.org/vlosuts/vlosuts
cd vlosuts
debuild
cd ..
sudo dpkg -i vlosuts_0.1_*.deb
sudo vlosuts upgrade --config=/usr/lib/vlosuts/default.cfg


I haven't added debootstrap as a dependency yet, so make sure you've got that. Also make sure you have qemu/kqemu/kvm installed (depending on what backend you want to use; default is QEMU). Notice that vlosuts needs to be run with superuser privileges. This is a consequence of needing to mount and bootstrap the image. The "upgrade" part of the command line instructs it to perform an upgrade test (as opposed to just building an image or creating a vlosuts mirror file of the system).
You'll probably want to copy that config file and change the mirror to something local. Also make sure you've modprobed kqemu (or else it could take far longer than necessary) and if you're running amd64, either change the target arch to amd64 or set the qemu path in the config to /usr/bin/qemu-system-x86_64 (as of writing, kqemu on amd64 only works with this binary, not qemu). man vlosuts can also provide some information.

Joey Hess: software sentence subtexts

Sometimes the mad libs way we have software fill in the blanks and make a sentence can be unintentionally interesting. Like this old but good one, that sadly doesn't work with GNU make:
% make war
Don't know how to make war. Stop.
I was pleased when ikiwiki made up this sentence when editing a discussion page. ikiwiki creating discussion.png Creating discussion sounds like a fine goal for a wiki. But I was startled to see this in Gnome, after I picked "Windows" from the "Preferences" menu: gnome starting windows.png Yipes!

Next.

Previous.