Search Results: "ag"

13 January 2008

Christian Perrier: Rant about useless changes in code

Here's what I found in the recent APT upload as changes to PO files:
 #: apt-pkg/cdrom.cc:678
 #, c-format
 msgid ""
-"Found %u package indexes, %u source indexes, %u translation indexes and %u "
-"signatures\n"
+"Found %zu package indexes, %zu source indexes, %zu translation indexes and %"
+"zu signatures\n"
The consequence of such changes is fuzzying translated strings, thus forcing translators to re-update their files and the translation coordinator to commit them. In short, valuable time wasted. One could object that translators shouldn't try to keep up 100% all time long. However, those who do not do so just end up with huge updates to do...which is sometimes demotivating. So many of us prefers keeping up with small updates. However, when one sees such updates that appear to be cosmetic, it's very hard to refrain hating developers (I even ranted about this in dpkg commit logs, which bringed some argument with Guillem Jover.... I certainly shouldn't have ranted in commit logs but that probably gives a good idea how upset I was). Please think about this next time you change a translatable string, particularly when you *know* that someone is taking care to coordinate *your* software translation work with translators. Side comment: bzr choke up on my local APT copy and I can't even cope with updates for APT. That will not really help me to love those DVCS. Update: many explained me that such changes are not useless which I'm ready to accept given my level of knowledge in programming. So, apologies to programmers who made these changes. I just hope this will however better give the translator's POV wrt such matters. We all know that translators *and* maintainers work really hard to give the best results and both always need to have a better knowledge of other's constraints....and limits! I've also been very wisely teached about possible ways to jiggle with VCS to work on defuzzification by reverting changes, unfuzzy, re-apply changes. Sure. At the expense of a lot of invested time to check how to do this properly with all these neat modern DVCS, I could. Yay, I so much love fiddling with VCS....and spending hours doing this is something that makes my days.

12 January 2008

Filip Van Raemdonck: Big G having issues

Something awry on Gmail this evening... I've been having status messages — you know, the yellow/orangish overlay on top of the page that usually shows when an action has finished — telling me that "the system encountered a problem" for a few hours now while reading my email, intermittently.
Now all of a sudden, I'm dropped in the "old version" of the Gmail interface and there's no longer a choice at the top for the current UI, you know, the one with the funky coloured labels and such; which disappearance leads me to believe that it's not just a client side issue. I'm simply curious now how long it'll take them to fix things.

*Update* As I finished this post and went back to navigating through Gmail, the new UI is back. That didn't take them long...
*Second update* ... but the service also wasn't fixed, I almost immediately started getting error status messages again. And now I'm back into the "old" UI. As I'll be off for bed soon, I probably won't find out how long it'll take. Not that I'm that interested.

Aigars Mahinovs: Having a (pyro)blast with your new Ice Block

Here is something I wrote some while ago, hope this will be useful for some World of Warcraft p(l)ayers. Has no other relation to Linux or Debian, except it works on it flawlessly. Also note that 2.3.2 patch went live last week. It is not a secret anymore that mages of all talent specs will be getting a present when patch 2.3.2 hits the live realms - the Ice Block will be available from any friendly mage trainer for a nominal fee. Currently this spell requires a whopping 21 point investment into the Frost talent tree. With patch 2.3.2 Ice Block will become trainable to all mages, Ice Barrier will take it’s place in the talent tree and a new awesome talent - Icy Veins will take the place of the Ice Barrier, so that even frost mages have a new toy to gain in this 2.3.2 mage winterly fiesta. While there is a significant proportion of mages that are frost for PVP or grinding survival purposes, a large proportion of mage population have never used Ice Block or haven’t used it for a while. For that reason, the rest of this article (after the break) will explore all the great uses of Ice Block, that all of you can look forward when patch 2.3.2 hits the live realms (or sooner, if this article convinces you to re-spec frost :)). So, what does the Ice Block do? When you cast the Ice Block, it purges you from all debuffs and releases you from all snares, you get frozen solid into a large block of ice (same look as hunter’s ice trap) and for 10 seconds you are immune to all damage, but unable to do anything - no moving, casting anything, no bandages, nothing. Getting rid of: Ice Block is a buff, so you can get out of the Ice Block by right-clicking it off at any time. Another way for keyboard-addicted mages is to press Ice Block keybinding button again (after the global cooldown is done). Enemy shamans can purge it off you and priests can mass dispel your Ice Block in PVP. Cooldown: the Ice Block is on 5 minute cooldown, which can be ended early using the Cold Snap talent from the mage frost tree. To prevent mages casting two ice blocks back to back by using the Cold Snap, Blizzard added the Hypothermia debuff (in 2.1) that prevents you from casting the Ice Block 30 seconds after the last cast. The main use of Ice Block is to survive pulling aggro in groups. While we all know that “good mages don’t draw aggro”, experienced players can easily show situations when drawing aggro is not mages fault and surviving that can be the difference between a wipe and a win. When Ice Block is used, your threat is NOT reduced, so you need to stay inside the Ice Block at least until you are under 130% of the tanks threat. After you Ice Block, the mob will run to the next person on the threat list. If your tank is dead, Ice Block will send the mob to another DPS or healer giving you a couple seconds to nuke it when it will be running back to you again. I have seen a few bosses loose their last 2-3% of health running between mages with Ice Block and hunters with Feign Death after a unfortunate death of the main tank. Ice Block is a great way to get rid of almost all debuffs that exist in the game: warlock DoTs, stuns, snares, polymorph, mind control … Even boss debuffs go away in a snap - Garrote from Moroes, Demonic Chains from Illhoof and many more deadly debuffs are no threat to a mage with an Ice Block ready. Ice Block can be used as an alternative to Slow Fall if you’re out of Light Feathers. Just do not cast it too high in the air - if the 10 seconds tick by and you haven’t hit the land yet .. you could as well kiss 10% of your durability goodbye. When solo grinding there is noone to draw aggro from you, so the mobs will continue to beat on your personal icy sculpture, however during that time your Water Elemental or other battle pets could be dishing some damage, your cooldowns will tick down and also you will also regenerate some mana inside the Ice Block. The Ice Block could thus make the difference between your death and Frost Nova+Blink+Blizzard and their death. Have you had some fun experience with Ice Block? Leave a comment so that others could repeat it too!

Adam Rosi-Kessel: TSA Gripe of the Day

I arrived back late last night from DC (National Airport, called “Reagan” by some) to Logan Airport. I got to National about an hour before my departure and checked two bags. Only one of them appeared at the baggage claim on the other end. The U.S. Air baggage people were surprised; they said National rarely loses or delays bags, especially where the passenger checks in with reasonable lead time. My second bag finally arrived this afternoon. I found the solution to the mysterious delay within: a Transportation Security Administration “Notice of Baggage Inspection.” Presumably they held my bag for too long or it just didn’t get routed properly after being manually inspected. I don’t believe the random manual inspections provide much improvement over the full CT scans now mandated at all airports. But apparently they do create inconveniences. On another note, I noticed for the first time this trip that the now obsolete “no smoking” signs above every seat have been replaced with “turn off electronic devices.” (Query which is more addictive.) Technorati Tags:

Holger Levsen: xorg backports for etch updated

I'm uploading new backports of xorg for etch at this moment. They are based on what was on unstable on the 9th on January, which was xorg 1:7.3+10. Thanks to XSF for their great work!

I've also included a backport of Andres Salomons xserver-xorg-video-amd package, as the one in sid is not uptodate enough for the OLPC laptop.

Adeodato Sim : Ikiwiki for, cough, debian.org?

(Disclaimer: I’ve decided to blog this mainly to get it off my mind. I’m not claiming it’s viable or appropriate, nor that the tool would be up to the job, or anything else. Heck, I’m not even involved with debian-www at all, but don’t we all love to share happy ideas.) The other day, when trying to think of a possible Summer of Code project to undertake this year, I thought that working on migrating (by making a parallel copy, see below) www.debian.org and wiki.debian.org to be ikiwiki-powered could be one, and see how it goes. Me, I think that having www.debian.org use a markup language, and have wiki.debian.org (or www.debian.org/wiki) live in a real VCS (us being Debian people, after all) would be two big pluses. The www instance would be only editable via the repository, either by the current group or DD-wide, and would have stuff like htmlscrubber disabled. And the wiki would be another setup/instance, with the normal setup for an ikiwiki wiki setup, backed up by a real e.g. Subversion repository open to all DDs, and possibly contributors at request. I believe that would be very very cool. Plus web edits as usual. This could also be used as a fresh start, and maybe as an opportunity to accomplish the long-awaited re-design of the site: if this job is done by making a live paralell copy, able to update itself from the current webml repository, and MoinMoin as well, it would give an interesting playground for experimenting, and could be adopted later on, when it’s truly polished, if ever.

Jacobo Tarrío Barreiro: ETOOCLEVER

msgid "Unable to cw::util::transcode package display format after \"%ls\""
WTF. That’s not even proper English. How am I supposed to translate it? No, really. My mind boggles. I’m going out for a walk in the beautiful Dublin weather.

David Welton: Why "dying" is an inappropriate term for programming languages

If you follow online discussions of programming languages, you'll occasionally see articles about language X "dying". It is, however, a bad metaphor, because the "life cycle" of a programming language is different from single biological units, of which you can definitely say at some point "He's not pining ... this is an ex-parrot!". Once a programming language is widely deployed, it simply won't up and disappear from one day to the next. Too many people and companies depend on it, and replacing it is difficult enough, that the "switching costs" will keep it in place for many years. The obvious example is Cobol. This effect works in favor of languages that are not "the new thing", and means they will probably not truly cease to be used for many, many years. On the other hand, it's also pretty easy to tell which way the wind is blowing and get an idea of what's hot and what's not. Java got hyped a lot in the past, now it's Ruby. Scala is beginning to get hyped some, so is Erlang. Careful observers can spot the rise of languages as they hit the early stages of the technology adoption lifecycle. By paying attention to what's going on in the wider world, it's also possible to see when languages are used less and less for new projects, and solely kept on for the legacy systems. I think this is what most people mean by "dying", but of course it creates confusion, because it's clear that the language is still utilized. In some cases, I think it may be possible that a language continues to be more widely adopted, yet still seems to lag behind, simply because other languages are being adopted at a significantly higher rate. So what it's really about is two factors: how widely deployed is the language in any given moment, and, perhaps more importantly, the rate of adoption - is it accelerating or slowing down? Are more people jumping on the bandwagon, or is the language being used less by innovators, early adopters, and new projects? You need both those coordinates to understand where a language is at - it may be huge but declining, small but on its way up, or a niche language that never achieved widespread usage that isn't catching on any more. The last one is the one you'd probably want to be wary of. The first two will probably be ok as long as you understand what you're getting, and the type of user or organization you are matches where the language is at in its lifecycle. I think that perhaps those interested in discussing these things seriously ought to find some good terms to use. "Forth's rate of adoption is declining" doesn't sound as exciting as "Java is dying!" though. "Fortran's diffusion is decelerating" doesn't have much of a ring to it. Any other ideas?

Antti-Juhani Kaijanaho: A visit at the emergency room

At 9pm Thursday my heart went into overdrive. At the emergency room I was diagnosed with acute atrial fibrillation and was scheduled for electric cardioversion but the problem went away on its own (as it sometimes does) so I was discharged in late afternoon yesterday, after a 16 hours long hospitalisation with no food or drink (cardioversion requires anesthesia). A noninvasive echocardiogram detected no faults in my heart, and no reason for the attack was identified. I am told this is a good thing and means I have a very good prognosis (it is likely that the problem will never recur). I feel fine now. The hospital visit was educational. I learned stuff about hospital procedures and some things about the equipment they use there, and met various people. I’m glad I had to make the call (if you have to go to the ER, it’s best if it’s for something nontrivial so they don’t feel you’re wasting their time but still something relatively dangerless). A bit more detailed report in Finnish is available.

Russell Coker: Victoria Hotel Melbourne

I have just stayed at the Victoria Hotel Melbourne. I booked it through www.WotIf.com and paid ~$110 per night instead of the list price of $186 per night. The location is great (little Collins St near Swanston St). It’s a short walk from most things that are in the central city area and the nearest tram stop has a tram that goes directly to Melbourne University which will be good for people attending LCA (although it’s close enough that you might want to walk and save a few dollars). The price is pretty good too (you don’t get much cheaper than that in the central city area). But there are some down-sides. The hotel is old and has an old design. It has small windows and air-conditioners are retro-fitted into the window (as opposed to the modern design of having huge windows and A/C in the ceiling). The air-conditioning is barely adequate and once the hotel walls heat up the room will be warm all night. The window-based air-conditioning also greatly diminishes the possibility of looking out the window, and for people who are tall enough to see over it they will probably find that the bed is too short for them (I stayed in a twin room, maybe a double bed would be longer - of course if I was alone in a double bed then I could probably sleep diagonally). The room lights are all halogen spotlights, that includes the reading lights over the beds. This is 90’s architectural fashion and not a functional design. If you want to lie on your bed to read a book or watch TV then you will be able to see at least three halogen lights from the corner of your eye. Seeing such a small intense light source in your peripheral vision is really unpleasant. The pool is about 5M*5M in size and approximately 1.1M deep (it seems deeper than a 1.0M pool I recently swam in but shallower than a 1.2M pool). In conclusion I think that the Oaks on Market [1] apartments are better value for money, altough Market street is less convenient. Update: I forgot to mention one last failing. For curtains my room had nothing other than a Venetian blind. As such a blind does not cover the entire window space I was woken by the sun rise. It’s bad enough seeing a sunrise after a hard night coding, I definitely don’t want to see one when I had planned to sleep in. Curtains that properly cover the window is not an expensive feature to add.

11 January 2008

Maximilian Attems: Testing Etch + 1/2 Kernel

2.6.24-rc7 is available on 5 architectures (amd64, i386, powerpc, s390, sparc). Please add the following line to your Lenny or Sid box sources.list and report back:
deb http://kernel-archive.buildserver.net/debian-kernel trunk main
This is not yet the real Etch + 1/2 kernel, but comes pretty close. According to our initial testing and user feedback 2.6.24 promises to be a great release. It will help Etch to have proper hardware support for newer hardware, has better power efficiency due to tickless kernel, enhanced wireless card support, the CFS scheduler and much more... It is a Debian novelty to provide an supported optional Linux kernel upgrade for a stable release. This is not the final as due to incompatible user interface the Etch build will have the old firewire stack. Once aboves land in Sid and got broader coverage will announce the Etch snapshots. So please give it a shot on your Testing/Unstable boxes.

Steve Kemp: I still got the blues for you

Been a week since I posted. I've not done much, though I did complete most of the migration of my planet-searching code to gluck.debian.org. This is now logging to a local SQLite database, and available online. I've updated the blog software so that I can restrict comments to posts made within the past N days - which has helped with spam. My other comment-spam system is the use of the crm114 mail filter. I have a separate database now for comments (distinct from that I use for email), and after a training on previous comments all is good. Other than being a little busy over the past week life is good. Especially when I got to tell a recruitment agent that I didn't consider London to be within "Edinburgh & Surrounding Region". Muppets. The biggest downside of the week was "discovering" a security problem in Java, which had been reported in 2003 and is still unfixed. Grr. (CVE-2003-1156 for those playing along at home). Heres the code:
#!/bin/sh
#
#  Grep for potentially unsafe /tmp usage in shared libraries
#
find /lib -name '*.so' -type f -print > /tmp/$$
find /usr/lib -name '*.so' -type f -print >> /tmp/$$
for i in $(cat /tmp/$$ ); do
    out=$(strings $i   grep '/tmp')    
    if [ ! -z "$out" ]; then
        echo "$i"
        echo "$out"
    fi
done
rm /tmp/$$

Holger Levsen: about Debian on the OLPC and OLPC Europe and more

Originally I planned to post this with the title "Last night I slept with 300 people" but this night happened two weeks ago... It was the night before the fourth and last day of the 24C3 were I slept in the gym :-) Actually I also planned to blog on the third day but then this day turned out to be really busy... and then I arrived home on new years eve and suddenly it was a week later and now it's the 10th of January. Time flies when you're having fun. And as you might have noticed it's not even the 10th anymore...

Timewarp back to the chaos communication congress! I think it's safe to say that the Debian booth at the 24C3 was a success. It was a nice meeting (and storage) point for Debian people, we collected quite some donations for t-shirts and stuff (the exact amount needs to be examined still) and we were able to help various users and contributors answering Debian specific questions of both kinds: how to install/configure/fix foo and packaging and other development questions from a number of people.. And we had a babelbox setup which was much better understood and perceived, once I added a sign explaining it :-)

Thanks a lot to the 24C3 organizers and the angels (thats how the congress volunteers are called) for making such a smooth and interesting conference as well as giving such a great space to the Debian booth! And equally thanks a lot to all the people operating our booth! For those who are interested to attend next year: roughly 64 talks were held in english, and 26 in german. I saw about five events live...



The sign hung for about an hour unmodified...

On the third day of the congress we had an OLPC.de meeting, which was quite productive and resulted in us founding OLPC Germany this monday. In the aftermath of this meeting I came up with the idea of having an OLPC Europe event at FOSDEM in Brussels in February, which by now has been accepted and scheduled by the FOSDEM organizers. Yay! So if you are in Europe and involved or interested in the OLPC, please mark the 23rd of February 15-17 localtime in your calendar :-) The idea of these projects is probably best summarized with "think global, act local and global", for more detail please read our vision. (And keep in mind this is in its very early stages.) OLPC Europe should also become an interface for all those european OLPC efforts which have been popping up recently and which all take up ressources in Cambridge, the OLPC "mothership", taking ressources away from the children of the world.

Then on the last day of the 24C3 congress I also gave the DebConf7 "thank you, Sponsor"-package to those four people from the freifunk community, who helped us out with accesspoints for Edinburgh. Much to my surprise and joy, they were really happy about it! Funnily two of those four are also among the three OpenWRT developers who ported OpenWRT to the OLPC laptop, which I borrowed to them somewhat in return :-) And now we work together in OLPC.de and .eu. Networking is sometimes really really fun.

Fast forward to 2008. Two days ago I finanlly had the time to to run etch, lenny and sid on the OLPC laptop (with wireless (including WPA), xorg and sound working and dualbooting with the original fedora install) and then yesterday I've created a usbstick which successfully booted a "d-i prototype". Yay! And best of all (for me), most of the actual work was done by other people, I just had to collect the pieces. My next steps will be documenting what I did and prepare a d-i image which actually works. I don't have pics yet (it's Debian running on a laptop, I guess you can imagine this), so for now I will just post another picture I received some three months ago and which made me incredibly happy at that time:



When I have a working d-i running on it, I'll post more pics.

Joey Hess: my first terabyte

I bought one of the new terabyte drives, to double the storage space on my home network. I put it in a Thecus, so I have a terabyte of storage in a computer about the size of my first computer's floppy disk drive.

Felipe Augusto van de Wiel: 11 Jan 2008

Bits from the Debian i18n meeting (Extremadura 2007)
From December 12th to December 15th, Junta de Extremadura hosted another one of the Debian Meetings; five i18n guys shared ideas, food, buses and fun with the Debian KDE maintainers. We would like to thank Extremadura for hosting us during the Hispalinux Meeting 2007, the event was held at Universad de Derecho (Law University) in Caceres, Spain.

These are the minutes, results and notes from our work, it is a brief description but hopefully complete of what we have done and what is still missing/pending.

Thanks to Cesar (cek) we had the chance to work on churro (i18n.debian.net) locally; the server is still running a 2.4 kernel because of some "tick" problems with 2.6 series, the last one tried was 2.6.21 and we should try newer ones, in order to support upgrades and not get stuck with 2.4, we hope Cesar will find time to test new Debian kernels.

First, let me introduce everybody to the services, robots and resources being hosted by i18n.d.n:

  • MoinMoin wiki for local and simple reference documentation, it contains all the links to the below resources. (http://i18n.debian.net/wiki/)
  • Pootle experimental server
  • dl10n scripts, aka dl10n robots (codename Lion), these scripts are responsible for the status of pseudo URLs used by some translation teams, by the Project Smith and by the NMU Priority List for i18n NMU Campaign
  • Synchronization of the i18n material used by the Debian website to generate translation statistics about PO and PO-debconf
  • Generation of Compendium PO files per-language
  • Different types of statistics
  • Other non user-visible services like a full source mirror for stable, testing, unstable and experimental, used by the scripts and robots.
  • DDTP, Debian Descriptions Translation Project
  • DDTSS, The Debian Distributed Translation Server Satellite, a web front-end for DDTP, now integrated to DDTP to use the Database back-end instead of the e-mail interface.


And, at some point, we found important to state clear the acronyms and names used in related DDTP projects/tools:
  • DDTS, Debian Description Translation Server, this is the main "back-end" used in DDTP, it tends to be the interface between translator tools (present and future ones) and the database;
  • ddt.cgi is a CGI interface that is able to provide info for specific packages or translations, including diffs, related packages and active/inactive descriptions.
  • DDTC which is the old (and still functional) command line client for DDTP.


We took the chance to organize a few things on churro, old accounts were cleaned out and removed, we moved from /org to /srv and got more GBs of space to the "playground". Old files were also removed and some are schedule to deletion on early 2008. With the reallocation of /org we also find some more space to /home and /var, we reorganize some of the links on the web space (specially to remove services from people's accounts), and we changed the mirror script to also synchronize the Packages and Contents files.

Grisu and Martijn worked mainly on DDTP and DDTSS integration. DDTSS now provides statistics for stable, testing and unstable, we are also working with Debian Med to provide support and infrastructure to a specific audience, like packages related to Medicine. The conversion to talk directly with DDTP/DDTS database also provided:

  • Fetching new translations is almost instantaneous and marks translation as requested (avoiding duplicated works via the e-mail interface).
  • After sufficient reviews occurred, the upload is instant
  • Committed DDTS / DDTSS / DDTP website generation into SVN
    • Added READMEs for the above directories


DDTSS now announces the user using authentication because of its integration with the Database backend used by DDTP. Quick trivia: DDTP is now a compound of 25 languages occupying 18 GBytes.

A few days before the meeting we had the offer to use "AUTOBYHAND" to upload a package with the Translation-* files. The package is now called 'ddtp-translations' and we worked during the meeting to create scripts to build the package and to test it on the archive side. This approach allow Debian i18n Team to upload new translations and remove old ones (or inactive ones) without bother FTP Master Team. Special thanks to Anthony Town, he has been working with us to prove tips, fixes and info on how to produce the package and the scripts. The code is available in the debian-l10n SVN under pkg-ddtp-translations:
http://svn.debian.org/viewsvn/debian-l10n/pkg-ddtp-translations

In our case, "BYHAND" processing consists of a simple tarball of the main,contrib,non-free /i18n/Translation-*, we decide to work on a set of scripts to make it easier to create new packages (ddtp-translations) in a consistent way and keeping debian/changelog up-to-date. We also made some suggestions to the script what will run on the archive side to check the tarball structure, base on the examples of debian-maintainers and debtags (tags-override).

One of our initial targets for the meeting with regards to Pootle and Debian was to try big PO files per language, fortunately, Nicolas and Friedel were able to increase Pootle performance enough to get a few languages from DDTP loaded in Pootle. Using the upstream Pootle-diet branch, which uses a database back-end for the generation of statistics, the time to browse the DDTP POs of a language (~20.000 files) went down to a dozen of seconds.

Speaking about Pootle, Friedel gave us a good picture of what is coming next in terms of Pootle's development. There are improvements planned in the areas of permissions and rights delegation, as well as file management (for projects and templates). Improved management of terminology projects is also planned.

Improvements in the QA capabilities of the translate toolkit and Pootle are planned to help with the "false positives" of the pofilter checks. Better reuse of existing translations will become possible by using better translation memory techniques. There is also work planned on formats and converters involving, for example, XLIFF, TMX, TRADOS and WordFast.

Another pending task for quite a while was the CVS migration to SVN, it is now done, with a new layout. Commits to the CVS were disabled and every single script or resource depending on CVS should be changed to use SVN. For now, we are publishing (via HTTP) the status files generated by the pseudo-urls robots until we can fix the scripts to re-enable the commit of the files. You can find them here: http://i18n.debian.net/debian-l10n/status/

We are pretty happy with the changes and results of the work during those days, but we still have some items pending on our TODO list:

  • More advertisement and usage information about PO Compendiums
    There are two use cases are identified:
    • Filling new PO files.
    • QA work to find inconsistent translations.
    Maybe Eddy would love to do that? :-)
  • Extend the duration of the statistics history. (Nekral)
  • Debian packages of the services running on churro
    • DDTP (Grisu)
    • DDTSS (Martijn)
    • dl10n (Nekral)
  • DDTP: add some scripts to handle packages with version in the description (e.g. kernel and kernel modules) (Martijn)
  • DDTP: Standard generation of the translation tarballs (faw)
  • DDTP: document the bracketed stats on the main page (faw)
  • DDTC: should be updated to match the current features. Documentation to ease integration with procmail. (Nekral - low priority)
  • Implement mail service for translation teams with their own robots (e.g. Dutch) (faw)
  • Collect data from http://www.debian.org/devel/website/stats/ (Nekral)
  • http://www.debian.org/intl/l10n/po/,
    http://www.debian.org/intl/l10n/po-debconf/
    are built based on the churro material. It would make more sense to build these statistics on churro (Nekral)
    • We could "fork" the page and add some fancy new features on these pages (Nekral)
    • Add information from the coordination page to indicate that a translation is ongoing. (Nekral)
  • Pootle: missing review indication. Hard with PO back-end. (Friedel)


There are a couple more reports to be sent but they are more focused on i18n specific questions, tools and plans for 2008. So, probably those will be sent only to debian-i18n mail list. If you are interested, please, stay tuned. :-)
Posted on d-d-a: http://lists.debian.org/debian-devel-announce/2008/01/msg00002.html
And a big thanks to Nicolas François (aka nekral), he helped me a lot making notes, preparing the text and reviewing it; and was patient enough to wait for the report while I was solving some personal problems.

Neil McGovern: A quick comparison of top news stories

SwedenUK
  1. Victory for topless bathers
  2. Court gives thumbs up to anal massage technique
  3. Postcard arrives 25 years late
  4. Swedish prostitution: gone or just hidden?
  5. Ninety pythons left to die in Swedish cottage
  1. Parted-at-birth twins 'married'
  2. Pound at record low against euro
  3. Vomiting bug 'hits three million'
  4. Mr Potato Head makes octopus pal
  5. Ngugi laments Kenya violence

Kartik Mistry: The first step..

* .. towards KDE + Gujarati. Release announcement in Gujarati for KDE 4.0 is there! Thanks to kde-in team for encouragement and follow-ups with lazy /me.

Anthony Towns: LCA Sponsors

An article by Sam Varghese appeared on ITwire today, entitled linux.conf.au: What is Novell doing here?:
A GNU/Linux system does not normally load modules that are not released under an approved licence. So why should Australia’s national Linux conference take on board a sponsor who engages in practices that are at odds with the community? What am I talking about? A company which should not be in the picture has poked its nose in as a sponsor. Novell, which indicated the level of its commitment to FOSS by signing a deal with Microsoft in November 2006, will be one of the supporting sponsors for the conference.
Novell was also a minor sponsor of the 2007 conference, and Sam wrote an article in January expressing similar thoughts, which included this quote from Bruce Perens:
“I’d rather they hadn’t accepted a Novell sponsorship. It wasn’t very clueful of them, given Novell’s recent collaboration with Microsoft in spreading fear and doubt about Linux and software patents,” Perens said.
Ultimately, I think that’s a mistaken view. Linux.conf.au is what it is thanks to the contributions of four groups:
the organisers
who create the conference, get a venue, organise a schedule of events, help the speakers and attendees to get there, and generally make it easy for everyone to just get immersed in cool Linux stuff
the speakers
who provide the core of the schedule, the reason for attendees to go, and a core depth of awesome technical knowledge and ideas
the attendees
who fill in the organisational/content gaps that the organisers and speakers miss, who make for fascinating corridor and dinner conversations, who make side events like the miniconfs, the hackfest or open day interesting, and who pay the rego fees that lets the conference happen
the sponsors
who provide a chunk of money to fill out the conference budget letting us commit to venues and events earlier (when we might otherwise have to wait to see how many people come), and let us do extra things that registration fees alone wouldn’t cover
Obviously sometimes you have to exclude people from participating, but that’s mostly only if they’re actually causing trouble for the event. For sponsors, that pretty much means trying to interfere in the conference itself, or not paying on time. Otherwise, if you’re contributing to the conference, and not causing problems, you certainly should be recognised for that, as far as I can see. For me, the same thing would apply if Microsoft was offering to sponsor the conference – if they’re willing to contribute, and not cause problems, I’m all for it. If they happen to not be doing anything constructive in Linux-space anywhere else, well, it seems perfectly fine to me to start contributing by helping make linux.conf.au awesome. In Microsoft’s case that would be hard, because all the people going “oh my gosh, Microsoft, Linux! Wolves, sheeps! Hell, snow!” along with possible mixed messages from Microsoft and our long-term major sponsors HP and IBM about the future of Linux and whatnot could really distract us from all the cool technical stuff the conference is fundamentally about. I don’t think there’s anything Microsoft could offer to justify that much disruption, but having more of the world’s software companies involved in free software would probably be worth a bit of hassle, if the disruption could be minimised. Ultimately, I guess my disagreement comes down to these couple of comments from Sam’s article:
Asked whether it was right that Novell should be allowed to be a sponsor for a conference such as this - which, in my view, is a privilege - […] […] Novell, obviously, is hoping that, as public memory is woefully short, it will be able to wriggle its way back into the community. Providing such leeway is, in my opinion, a big mistake.
In my opinion, the ability to contribute to open source isn’t a privelege, it’s something that should be open to everyone, including people who’ve made mistakes in the past: and that’s precisely what the “free” in free software is all about. OTOH, if you want to see who’s been participating most in the Linux world lately, you’re much better off looking at the list of speakers than sponsors. Novell (or at least SuSE) folks giving talks in the main conference this year seem to include John Johansen and Nick Piggin. Interestingly, the count of HP folks seems a bit low this year, with only two that I can see, which leaves them not only merely equalling Novell/SuSE, but beaten by both Intel and Catalyst. Tsk! I guess we’ll have to wait and see if that changes when we can see the list of attendees’ companies in the booklet this year…

10 January 2008

Robert Collins: 11 Jan 2008

thank you lazyweb; A number of folk have written to me pointing out Netem. One in particular, Yusuf Goolamabbas even provided a set of wrapper scripts for Netem that I'm going to be digging into next week. Netem is built around various lower level tools like tc, which is good (tc is what I was using year ago). I'm hopeful it will be really easy to use, and will blog something when I've used it in anger :)

Christine Spang: MIT Athena: Not Dead Yet

(Disclaimer: I work for MIT Information Services & Technology blah blah blah I am a student blah blah these are only my words and do not represent the opinion(s) of my employer.) Way back in the day in 1983, MIT started something it called Project Athena, which had the goal of investigating how computers could be used to enhance education at MIT. This project became the origin of such pieces of software as the X Window System and Kerberos, as well as a campus-wide network of workstations all running similar software. In 1991, Project Athena ended, but the Athena system continued on, taken over by MIT Information Systems. It’s 2008, and Athena still exists at MIT—walk into a computing cluster, and chances are all the machines will be running Athena software. (Unless that particular cluster has been taken over be Athena’s evil sibling, often referenced as “WinAthena”, which often seems to be maintained by no one, and whose existence is sometimes denied by those who maintain and support Real Athena. Not many machines have suffered this agonizing fate, luckily.) Unfortunately, as the years have progressed recently, fewer and fewer resources have been put into the development of Athena. In many ways it is no longer on the cutting edge of things as it has been in the past, though it is certainly still useful. Some students these days, however, even think of Athena as only “their MIT email” or maybe use it occasionally to print something in a cluster on the way to class. I’ve seen people grow frustrated and storm out of a cluster due to things like instructions for using a flash drive that involve more steps than just plugging it in. While on the one hand it’s easy to laugh at people for a lack of patience or being open to a computing system that is not either Windows or Mac and perhaps a bit more complicated on the surface, on the other hand, some of these things really should just work by now, and on other UNIX-based systems they do—but Athena has lagged behind. When you log into an Athena workstation for the first time, you are confronted with what looks like this: Clean MIT Athena login That’s GNOME 2.8, and it looks kind of like the GNOME 2.8 default but uglier. When you look under the hood, there are pieces of the system that obviously originated in a time where nothing better existed and so something new had to be created—the “xlogin” login system doesn’t support PAM, and the login path involves a hairy maze of scripts that perform various tasks. Under the hood, the base OS is currently RHEL 4 or Solaris 10. I still can’t remember what the right options are to feed RPM whenever I need some information that I think I should be able to get from it. These things were once necessary but today just look crufty. Some people have tossed around the idea that everyone has a laptop these days and thus clusters are uselessly expensive, but it’s been met with a lot of resistance. I’m all for progress, but I use clusters all the time! They’re one thing that makes it an easy choice for me to have a really portable laptop, because when I really need computing power or screen space on campus away from my room, there is always a cluster nearby. They’re also nice isolated places that can be associated with “work mode”, which is good for productivity. Beyond all this, Athena provides a common platform that all technical classes can depend on, from providing standard and specialized academic software to standing as a baseline of “make sure your code works on this before handing it in because that is how it will be graded”. At any rate, things are finally happening on this front. Athena can’t stay RHEL 4 forever—while AFS allows non-system software to be easily updated for all machines without requiring any OS release, hardware moves on and compatibility is lost, and the rest of the world is coming up with new awesome things that Athena machines are missing out on. A student group that I am vaguely involved with, SIPB, took the early initiative with this and created DebAthena, which takes stock Debian and Ubuntu and allows it to closely resemble an Athena environment. We even run a campus Linux dialup using the packages. (I won’t claim to have done much work on DebAthena myself because, well, I didn’t.) Amazingly, the Athena release team has decided to work with the SIPB on the next release of Athena. So, what I really just wasted over 600 words prepping for is to say that Athena 10 will be based on Ubuntu. This is only relatively new news, but I am lame about finishing blog posts. There are a variety of reasons why Ubuntu was chosen over Debian. Some of them are lame and some of them are not. Even so, I am excited about this prospect—and it should be possible to peripherally support Debian in such a way that was not possible with Athena 9.4. I really like Athena. Even coming to MIT with a background in Linux there has been a steep learning curve, though, and I think that things could be better. Lots of people here have their first encounter with a ‘nix system in the form of Athena, and we should strive to make that experience as good as possible. I’m kind of skeptical on the expected release date of this upcoming summer, but as long as it happens soon it will be a big step forward. In some ways it’s kind of sad that I’m excited about a big part of a research institution catching up with others—but inertia is a strong force, and dealing with thousands of workstations is no trivial task. I kind of long for the exciting days of creating new big pieces of free software like X. I bet I imagine those days as being better than they actually were.

Next.

Previous.