Search Results: "ag"

25 February 2007

David Welton: Microsoft - an exercise in frustration

I've been investigating ways of testing out applications like Stuff to Do on Windows, and boy has it been frustrating. It's not a fun task in the first place, as I'd rather be coding than trying to deal with crappy incompatibilities between browsers and operating systems. I first looked into VMWare products, which look pretty good. The Workstation version has a free 30 day trial download, and the basic player is free of charge. Unfortunately the Ubuntu player packages appear to be seriously broken. Qemu also looks like a good possibility. I don't care if it's not blazing fast, just as long as reloading a page in IE doesn't take 5 minutes. I think I could make either one of those options work. However, the hairy, gorilla size problem is the microsoft operating system itself. I don't want to deal with Vista, because it's a hog, and emulating a hog is bound to be slow. So I'd like to get XP, and since I'd prefer people to respect the licenses of software I write, I think it's only fair to get a legitimate copy, even if my friends here in Italy will probably think I'm batty. Overlooking the fact that the basic retail price is $200, which is somewhere north of double what I think is reasonable, it seems as if you can't even download the damn thing and pay with a credit card. How antiquated is that? I want to be up and running now, not fiddle around with a CD that might arrive a week from now. The end result: massive amounts of frustrating and nothing to show for it. That I would have avoided if I just found a cracked version. I think for now I'll just put up some extra 'get firefox' banners on my sites:-/

Ross Burton: Lack of Tasks/Evolution Synergy

I'd noticed back when Dates was started the libecal was failing to notify Dates when events in Evolution changed, and vice versa. This was magically fixed when Dates moved over to ESource, so I didn't continue investigating it. However, Tasks doesn't use ESource yet and people had noticed that if you add items to Tasks, they don't appear in Evolution or the panel. This is a major problem, so I build EDS and debugged the problem. Turns out that the system tasks store is at ~/.evolution/tasks/local/system/ but when using ESource it is at ~/.evolution/tasks/local/system (note the lack of a slash) and as backends are looked up using literal string comparisons, these don't get the same backend so you don't get change notifications, and even worse modifying the task list with one application will overwrite the other's changes. Luckily the fix was trivial, and I hope that it gets reviewed soon.

Ian Murdock: The times they are a-changin

Yochai Benkler: “I find myself talking to all sorts of weird hackers one day and chief economists of major corporations the next day, and they’re all interested in similar things.”

Christian Perrier: Thank you, Mr dbmail maintainer

Today, I was about to announce French reaching 100%. The announcement was written and ready to be sent as of today when the status page would have been generated. But, of course, as of every week-end, this is the moment that yet another maintainer choose to break his debconf templates. That sucks. A lot.

Pierre Habouzit: git rebase is not harmful, it's just _not_ always the best solution, that's all.

I must say I disagree with John a lot about git rebase. git-rebase is the most nice feature I've ever seen float around in a SCM, and is part of the things I love in git. I mean, I do not disagree with the fact that it cannot be used in every single case. It is indeed meant to be used in private topic branches. git-rebase is meant to be used in a workflow where you have a topic branch (meaning some non releaseable nor push-able work) and that you still want to keep up with others work. With other SCM's, you have to update your working repository, wich in many cases generates nasty conflicts, hard to deal with. Especially in svn e.g.. With git, you commit your work, pull the remote branch, and then rebase ontop of it. It makes a lot of sense, and when your topic branch is indeed ready, you can push it upstreams, and the next rebase will merge the bits that have been accepted automatically. I just can't think of a simpler way. Btw, we use svn at work, and I do use git-svn instead of svn to be able to develop my own patches without fearing conflicts in the same way I did before. I know I will benefit from the powerfull git merging capabilities and help at any stage, even if I did not pulled the svn for a long time. That makes the developpement much more sane, as I only try to push coherent changes, hence on a less regular basis. You could not do that without git-rebase. In that sense, git-rebase is anything but evil.

24 February 2007

Wouter Verhelst: The cool kids

Primary school is a long time ago. Still, every time I buy me some new toy, I somewhere in the back of my head wonder how this will have an influence on my social standing. I have this Nikon D50 since a few months now, and have brought it to FOSDEM. Mostly to take pictures, but, well, I did think it'd make me look good—at least slightly so. Turns out everyone and their dog has one. Guess I'll need to take my flute next time. Or, well, convince nattie to sing Aria 14, and then follow that up with Aria 15.

Jurij Smakov: Debian kernel configs

For a while now there has been a small but consistent demand for a simple way to obtain the kernel configuration files, used to build official Debian kernel packages. I’ve been working on a solution for that problem, and I think by now it’s working reasonably well to announce it to the world :-) . Ladies and gentlemen, without further ado I bring you the Debian Official Kernel Configuration Files. It works by scanning the archive nightly for new linux-image and linux-modules packages and extracting configs from them. If you have any comments or proposals on how to improve it, feel free to contact me by email.

David Nusinow: ImageJ Rocks

ImageJ is probably the coolest piece of Free Software that the Free Software community isn't broadly aware of yet. It's a stable, mature piece of cross-platform code that supports both plugins and macros, and a large number of these have already been written by the scientific community. When contrasted to the photoshop/gimp debates, there simply is no competitor to ImageJ in the world of biological imaging: it's the standard for such work (except for specialized tasks like driving microscopes). If it wasn't in java (which I don't really know the tools for right now) I'd have uploaded it to Debian long ago.

A word of note though: if you want to use it seriously, I recommend building it yourself. I just spent two hours reading through the interpreter trying to speed up an extremely slow macro only to find that with a simple rebuild with the jdk in unstable's non-free I got an immediate and more than acceptable speedup, which should speed up my PhD work significantly. Still, the code is relatively nice and it was fun digging in to the interpreter, which was quite easy to understand. I may have to add a few more macro functions that I've been itching to have.

With the recent freeing of java, it'll be great to see software like imagej and jedit (which I'm also really enjoying) enter Debian finally.

Michael Prokop: zsh: insert-unicode-char

Ever wanted to insert a character in your terminal but don’t have a keybinding for that character? zsh provides a nifty feature called insert-unicode-char:
autoload insert-unicode-char
zle -N insert-unicode-char
bindkey '^Xi' insert-unicode-char
Figure out the character’s code (take a look at unicode.org/charts/ for example) and press ‘ctrl-x i’, followed by the character’s code and press ‘ctrl-x i’ once more. Usage example: ‘ctrl-x i 00A7 ctrl-x i’ will give you an ‘ ’.

Evan Prodromou: 5 Vent se CCXV

A few days from now is the first BarCamp we've had in a while: DemoCampMontreal1. DemoCamp is a BarCamp variation with a much shorter time frame (a couple of hours, rather than all day) and strict rules about presenting. Demo-ers cannot use Powerpoint slides (or even OpenOffice Impress slides!); they have to demo working code. I'm going to be doing the first demo of the first DemoCamp, which should be pretty fun. What will I be demoing? The OpenID extension for MediaWiki, of course. I'd like to show folks who have MW installs how to get OpenID enabled on their sites, and I'd like to show other developers how to (easily) integrate OpenID into their existing software. I don't think it's necessarily that hard. DemoCampMontreal1 is on Tuesday, Feb 27 2007 at 6:30PM at the SAT. Everybody's invited, and as an extra bonus, t-shirts from BarCampMontreal1 will be there, for attendees. Cool! tags:

MLUG now has OpenID Lurking in #mlug (Montreal Linux Users Group) on Freenode, I caught a cross-discussion about OpenID being enabled on http://mlug.ca/ . Which is great news -- I'm excited to be able to use OpenID on some of my favorite sites. tags:

Creative Commons 3.0 I'm excited to see the announcement that the Creative Commons 3.0 licenses have been released. The 3.0 licenses were in part the product of the Debian-Creative Commons Workgroup, which tried to smoothe the rough edges of the CC licenses that made them incompatible with the Debian Free Software Guidelines. See the Debian Creative Commons Workgroup report for more info. We didn't get everything we wanted from the negotiations, but we did get the essential problems out of the way. I think that the 3.0 licenses are compatible with the DFSG, and that works licensed solely under CC 3.0 should be allowed into Debian main. But we probably have some discussion on debian-legal ahead of us on the subject. tags:

Dead tablet walking So, I think I mentioned that I borrowed a Nokia N800 tablet last week at the LWOSS. I took it to bed two nights ago -- it's a really good computer for reading in bed -- and the battery died on the nightstand overnight. When I plugged it in in the morning, it went into some kind of zombie fugue. It booted up, spun in place for a little bit, then shut itself down and rebooted again automatically. I couldn't get it to stop with the normal power button, so I eventually pulled the battery to make it stop. But if I put the battery back in, it went into its Roomba-bumping-into-a-wall loop again. Frustrated, I ended up re-flashing the entire system. That solved the problem, but I have to admit some regret at losing all my settings. It won't take that much work, but I'm going to backup to a mini-SD once it's done. tags:

Holger Levsen: FOSDEM

Wow! Great and unexpected network at FOSDEM! Yay! At least in the Debian developer room. The camera is also set up and we recorded the first talk already :-)

FOSDEM is organized pretty well this year again and again it's great to meet so many different people here!

More "later", but rather after the weekend, I prefer to talk to people here instead of writing long blog entries... :-)

Joey Hess: whadda week

I've been in a good mood toward the end of this week as the stuff I've gotten done has reached that critical mass that makes me feel I'm accomplishing something. First, I got a nice new domain for ikiwiki, with an irc channel for good measure, and there's also work on a Google Summer of code application for ikiwiki afoot. Then there was rather a lot of useful feedback and patches on ikiwiki, and a few nights ago a very tricky race condition was discovered. Batting around possible fixes for it on irc for several hours was pretty useful, it's a lot easier to think about locking, deadlock, races, etc, when there are some other minds to share the thinking. I eventually came up with a fix that seems ok, around 5 am that morning. Yes, my sleep schedule has been suffering.. On Thursday I took a digression into RL to fix some cladding that was pulled away from the eves of my house by a badly attached cable. I ended up wandering around Lowe's for over an hour -- when did that become such a fun thing to do? Oh yeah, when I bought a house.. Some kids were playing hide and seek; maybe a bit dangerous there but it has to be the funnest possible place to do it. Anyway, amoung other things I bought a collapsable ladder and had an interesting time on it 2 stories up while avoiding the nearby electric wire. Also fixed a broken latch on my wardrobe. Concurrent with all this, in $DAY_JOB, I've been working on the armel port of Debian, including getting d-i to work with it. Since this is an unofficial port, that is not gpg signed currently, this also gave me a chance to make d-i capable of dealing with an unsigned repository. Earlier this evening, I almost completed my first armel install on an nslu2, and I expect to release images by Monday. Finally, AJ reminded me about an item that'd been on my TODO list for far too long; some way for James to deal with gpg keyrings that doesn't treat them as binary blobs. I'd been meaning to work on that for oh, 2 years? 3? And I must have been thinking about it in the background a bit, because I fairly quickly came up with this gpg changesets idea, which is basically a dedicated revision control system, and a data format that's not too horrible (though it could be much nicer with support in gpg). Quickly followed by a whole working sample implementation that I hope James, or someone, will find useful.

Andrew Stribblehill: Laphroaig quarter-cask

We went to Scotland on a family holiday this week (brave or stupid, answers on a postcard). You would not believe the number of puns you can get from the simple town of Ayr. For example, R: “You should have turned right there!” Me: “Oh well. To Ayr is human.” I shall spare you the rest: if your mind isn’t already overflowing with similar appalling jokes, you’re no friend of mine. Whilst in Ayr, I came across a marvellous whisky shop, Robbie’s Drams, and bought a bottle of Laphroaig quarter-cask and another of Smokehead. This article, or what remains of it, is to describe the Laphroaig quarter-cask whisky. Should you wish to avoid the Flash-animated website, here’s a precis. Tales are told of a time when the business of Laphroaig was carried on less than legally and it was useful to carry away smaller casks when the Excise men were coming than the more conventional full-size casks. Over the past few years, they have tried their best to recreate the whisky that would have been drunk as Laphroaig a couple of centuries ago: quarter-sized casks, slightly higher strength and an older filtration model. The effect of the smaller barrels is to increase the surface area to volume ratio substantially, so more flavour will enter the whisky from the barrel. Thus, they bottle it much younger than their standard ten-year-old offering. To smell it, a sweet smell hits the nose — perhaps toffee apple. On the taste, there is an initial earthy sensation followed quickly by a brief flash of kedgeree, leaving the smoky aftertaste of turmeric at the back of the throat. This is a much more subtle whisky than Laphroaig’s ten-year-old: thinner and less oily, and with a much more delicate, though still substantial, peaty hit. Because it’s not chill-filtered, the whisky becomes delightfully cloudy when water is added. I recommend that you try it both with and without additional water: many of the flavours become more muted with water, but a creamy taste comes to the fore. In summary: if you can get your hands on a bottle or two of this, it’s well worth doing so. An excellent whisky. I should also say that even if you’ve disliked other Laphroaigs in the past, give this a shot. It may just be your way into the other delights from the Laphroaig distillery.

Benjamin Mako Hill: Fit For an Emperor

I found this box outside my apartment labeled, "The Emperor Clothes." Fortunately, the contents were exactly what I was expecting.    Surely clothing fit for an emperor. That is of course, if you are fit enough to appreciate them.

Jan Wagner: OpenWRT 0.9 / X-WRT 2.75

Last week I updated my WRTSL54GS to OpenWRT 0.9 with X-WRT 2.75. Since my box has an USB port, I was missing a way to umount mounted usb storage. Looking deeper into it, I noticed that partitions get mounted by ‘/etc/hotplug.d/usb/01-mount’ like this:

# mount
[…]
part1 on /mnt/disc0_1 type ext3 (rw)
part2 on /mnt/disc0_2 type vfat (rw) The correct devices are missing. A patch is available:

mount.patch Okay … So far, so good. Now some tweaking to webif^2 for umounting attached usb storage devices. Here comes the patch:

umount-button.patch Umount Buttons , , , ,

John Goerzen: Rebase Considered Harmful

Today I was musing about different version control systems and merge algorithms. I've been thinking specifically about how I maintain Debian packages in Darcs. I tend to import upstream tarballs into one branch, and maintain the Debian packages in another, simply merging when a new upstream is released.

Now, there seem to be two prevailing philosophies on how to handle merges in this case. I'm thinking here about merges back to upstream. Say I want to contribute my Debian patches to them.

  1. Commit "clean" patches upstream. Don't have a bunch of history -- the fixing typos commits, the fixing bugs commits, or the merging to track new upstream releases. Just something like a series of diffs against the current head.
  2. Bring across the full history, warts and all, and keep it around permanently.


git encourages option #1, with its rebase option. Darcs encourages option #2 (though some use its amend-record option to work more like #1).

As I got to thinking about it, it occured to me that git-rebase would be very nice if you are going to use philosophy #1. In short, rebase will remove your local patches from a repo, update it to the latest upstream, then re-apply your local changesets -- aborting to have you fix any conflicts. This is as opposed to a more traditional merge, where you add the upstream changesets to your local branch and then commit new changesets to resolve conflicts. (So a rebase would be totally useless in situation #2)

I got to thinking about this, and started wondering what would happen to people that I'm working with that in turn work off my branches. And sure enough, the git-rebase manpage says, "When you rebase a branch, you are changing its history in a way that will cause problems for anyone who already has a copy of the branch in their repository and tries to pull updates from you."

I maintain, therefore, that git-rebase is evil and should be avoided. It only works for a situation where someone maintains a private branch of a project, never shared in any way except to submit patches to an upstream. Forget it if you have a team maintaining that branch, or want to post that branch online for others to help with (as I do with my Debian darcs package). Even if you keep it private now, do you really want to adopt a work process that forces you to keep it private forever, or else completely change how you work?

And this brings me back to the original question of patch philosophy. Personally, I dislike philosophy #1. I'd much rather have the full history of a change, warts and all. Look at the Linux kernel example: changesets that introduced bugs that made it into the official tree have their fixes documented, but changesets that introduced bugs that were fixed before being merged into the official tree could be lost to the public due to rebasing by submitters. Is that really what we want? I don't think so.

With Darcs, tagging is very cheap and it is quite trivial to write an "apply a changeset bundle" script that makes a before tag, applies a series of patches, and makes an after tag. One could then run a darcs diff between the two tags to see the net effect on the repository, or could still look at the individual patches. (Or, you can avoid tagging and manually specify the "from" and "to" patches.) I find that a much better model: you can have it both ways. I'd think that most modern VCSs ought to support some variant on that, too.

And I think that git-rebase should be removed on the grounds that it encourages poor version tracking practices.

23 February 2007

Biella Coleman: On Mole-patrol

So last year as I entered the job market, I posted less “personal” blog entries and have more or less kept with the tradition except with the occasional post, especially when it concerns my mom. Right when I moved to Canada, I broke with this tradition and wrote a longish entry about my moles which I thought of as a public serive announcement to get people to go on mole patrol, because really, that is the only way to deal with recalcitrant moles. Of course, I am on constant mole-patrol and a day before I left Puerto Rico, as my sister moved her hair away from her neck to pull it back, I noticed a funky looking mole. Now, it was not all that weird but a little weird and I was like, go go go to the dermatologist and check it out. It took a few weeks to get an appointment and then they took it out, bioposied it, and indeed, there was melanoma. Everyone was shocked because, well it is shocking news to get and if anything, I thought the mole would have abnormal cells like mind did. She thankfully was pretty calm throughout the whole process (I attribute it, in part, to the fact that she does not spend too much time on the Internet, where you can arm yourself with a lot of good, but often downright frightening information). A few days ago, after a battery of tests, we found out that the melanoma was very small and contained and they had taken everything out. So for now, we are on the clear but it means constant mole partrol for her and I… Melanoma runs in families and as kids we also ran around on the beach so this issue is not going to go away. But I guess it is good that I had my scare in August, otherwise I would have never given her mole a second thought. I probably would not have made myself stare as I did at her hidden moles, every chance I had. So anyway, again, go to your dermatologist and check your moles. Or at least go on mole patrol. It is well worth the hassle…

Edd Dumbill: XTech 2007 schedule: behind the scenes

After a couple of months' hard work, I've posted the schedule for XTech 2007. And, though I say so myself, it looks good. XTech 2007 grid You can read more about the schedule itself over on the XTech web site, but I thought it would be interesting to explain how we got there. The people bit  After the call for participation, we wound up with 200 proposals in the system. From there, the target was to get down to 5 tutorials and 68 presentations. Each proposal contains an abstract of at most 500 words. I enlisted a small army of reviewers (69 in all) to help, and assigned four or five reviewers to each abstract. 829 reviews were assigned in all. The reviewers work blind, so they don't get to see who the proposer is.
After the review, I read every score and proposal, and created a shortlist of the best scoring proposals plus those that had spuriously low scores given their quality. From this shortlist the hard graft of preparing a draft schedule started. We had already decided in advance on our usual format: four parallel tracks of browsers, core tech, applications and open data. I then filled in the schedule, aiming to create themes for days, or at least for the 2-session blocks. The draft schedule and details of those shortlisted but who missed the cut were circulated among the committee. After some iteration and feedback the final schedule emerged. Picking tutorials was a little different, as this is done by myself and the committee directly. The constraints on choice are more commercially-oriented. Experience has shown we need mainstream topics that people will be happy to pay for. Even so, each year we try to include one emerging topic. Last year, it was Rails. This year, it's OpenStreetMap.
Choices made, I then notified the speakers, awaited their confirmation, and reached the point where we could publish the schedule. The mechanics of it all A glib reading of the above would make it all sound quite simple. And this year I'm pleased to report that it was a lot simpler than previous years. We have been able to use Expectnation from beginning to end, which has streamlined a lot of the work.  Expectnation's my super startup that's taking up the time that XTech and fatherhood don't! I'm about to tell you why it's wonderful, so please forgive a little pride.
Gathering the proposals was easy once the CFP had been set up inside Expectnation. I set up three calls: one for presentations, one for tutorials, and a secret one that the public doesn't get to see. (We always need a secret one for people who have very good reasons why they didn't make the public deadlines.) Request response The review phase Recruiting reviewers was done by Expectnation's request system. This lets me send a request to a large number of people simultaneously, and collect their responses via the web app. (Previously, this had involved email, spreadsheets and wasted time.) The chart you see to the right shows the breakdown of the response to this request. If a reviewer said 'yes', they added a note to say which types of proposal they would review, and signed up for an account in the system. I then passed through every paper assigning four or five appropriate reviewers. A quick search each time allowed me to look for the right reviewers, and ensure no one reviewer got overloaded with work. Once reviewers were assigned, I headed over to the Mailroom department. Expectnation has a large number of configurable mailing targets, one of which is "reviewers with work to do". I emailed each reviewer with details of how to get on with the reviewing. Every reviewer then logged into Expectnation, saw the proposals they needed to review, and used the interface to efficiently score the proposals. One big lesson here is that it needs to be very efficient if you want to get the best reviewers, who are often the busiest. Another wizzy graph enabled me to keep track of the reviews, and the mailroom let me send out a reminder to those reviewers who hadn't finished their work yet, when the time for the close of reviewing drew near. Picking the papers Gridding out XTech 2007 Expectnation lets me sort and filter proposals pretty flexibly, so I went through the papers for each track in turn, ordered by their review score. Anything scored 3 or higher (4 is best, 1 is worst) was almost certain to be shortlisted. I read all the reviews and the abstract, and moderated any score that was unusually low (for some reason, reviewers rarely overrate proposals!) The next step was to set up the empty grid, shown in the top half of the diagram to the right. Here I added the empty time slots to the rooms we had, and assigned putative tracks to each of the rooms (they can be swapped around later if needed.) After that, the scheduling can start, shown in the second half of the picture to the right. Each empty slot can be assigned a paper from the shortlist for the relevant topic. That way it's easy to "paint on" talks into each room and quickly get a sense for the overall flow of the conference. Once it was time to finalize matters, I mass-marked all the scheduled papers as accepted, which automatically sent a notification to the presenters, using the same request system as for reviewers. When a speaker confirms, their proposal status changes and they appear in the final public grid. From there, I am able to use the mailroom again to inform speakers of the information they need to know. Additionally, speakers can log into the system at any time to see when they've been scheduled to speak.
Gridding out the conference in Expectnation is probably the biggest timesaver of all. Previously this involved a lot of sketching on paper or a spreadsheet, and a lot of manual work notifying people, and then more work creating the timetable to go on the web site. Now, both the grid and a full web of abstracts and speaker details are generated automatically. What next? As you can probably tell, I'm rather excited about both XTech 2007 and also about the work we're doing with Expectnation. What's next for XTech is the process of publicising the conference among attendees, recruiting session moderators, and also the writing of papers by the presenters. As the conference draws nearer, the attendee-level interactive features of Expectnation will kick in, allowing personal scheduling and rating of sessions. What's next for Expectnation is that we're ramping up to our 1.0 launch. We're working with a handful of early adopter customers right now, and are always interested in new use cases. As we get nearer the end of the first tranche of engineering work, we're going to gear up the publicity effort and start explaining to the world why we're special. As usual, I'd love to hear questions, feedback and suggestions.

Christian Perrier: German bump: fr: 99.928%, cs: 93.662%, de: 83.592%, sv: 80.372%, vi: 77.949%

Big bump for stats of german debconf translations This is somewhat expected: most of the NMUs I'm doing today include german translations. It seems that the german l10n team had a great activity between October 2006 and January 2007, which is the period of time I'm fixing remaining bugs for right now. Today's uploads: localization-config, xmcd (switch to po-debconf and a lot of translations). And I finally couldn't resist and I posted a call for new translations for my geneweb pet package. 23 translations and already one more came (Tamil). On The Road to 100%, we're now missing Florian Weimer's debsecan.

Holger Levsen: debian-community.org

I wanted to write a much longer blogpost about debian-community.org before FOSDEM, where I'll have a opportunity to present the idea in some greater detail anyway. But as we are about to leave from the Debian-Edu gathering in Soissons, I guess my time will not allow it.

So I will not waste much time to describe here, what debian-community.org is about, you can read about most of the ideas on the webpage already anyway. I have quite some more ideas and concrete plans, which I will reveal in Brussels and after that on the site itself.

And for those, who cannot make it to FOSDEM (or just to my presentation, which is at the end of the schedule) the DebConf videoteam will also (try to) record the talks in the Debian room at FOSDEM - we'll see if that will work :-)

Besides being aware since some time that Debian has developers and users and (officially) nothing in between, there were two talks at LCA2007 which inspired me to start debian-community.org: the talk by Jono Bacon about the ubuntu community and the keynote from Kathy Sierra about passionate users. I suggest you watch both, they both are very insightful. If you are really low on time, I really suggest to find some. And if you can't, watch Kathy's :-)

But personally I think both are a must see. They changed my way of thinking about Debian, the OS, the project and the community. Thanks Kathy and Jono!

Oh, last but definitly not least: please join the #irc-channel, the list (both linked on the website) and get involved. Especially if you want to help to shape your local(ized) debian community!

Next.

Previous.