Search Results: "beh"

25 May 2007

MJ Ray: Leukemia Research Weston-super-Mare Bikeathon: More Feedback

liz radford commented:
"Thanks for the advice, your comments on the route match those of a couple of others so I think we will go ahead and make those changes but keep the hill of pain! I will ride the revised route this weekend to give it a go."
While you're out there... I heard some comments that Windwhistle Lane on the short route wasn't very easy to follow, but I suspect that's more a problem with the council's (lack of) signs than a bad route. I didn't find the black-and-white bikeathon signs easy to spot on the faster/busier stretches. The pink and the yellow(?) ones were usually easily noticeable. I wonder whether the first black-and-white signs were at Worle Moor Gate - I went so wrong there that I rode up to the marshals at Summer Lane/Diamond Batch from behind!
"On the photo web site, you can get access to a total of about 700 pictures but it's not immediately obvious how. Mind you I can't criticise - the http://www.lrf.org.uk site is even less user friendly. We have photos on it of local people getting out there and doing great things to raise money but you try and find them its like wandering the catacombs. We need our own simple West-country site! Have a look and comment if you want, an experts critic is well overdue."
Well, the LRF site isn't bad - it needs to sort out its colours and contrast, and the text alternatives to images seem to be nonsense like asterisks, but I think I can actually access all of the pages without trouble. If you'd like a westcountry site, contact me at work and I'll offer a deal.
"Anyway back to photos. Get onto the one page of photos it will let you see and then click "refine search." This will take you to the menu as follows... Start Childrens Race Bleadon Hill Finish 1 Finish 2 Finish 3 Finish 4"
I can see more photos that way, but still only the first 8 from each category. Thanks once more for organising a great event Liz! I've noticed that my page is attracting some search results for bikeathon - is anyone else who rode this event reading? Care to comment on it? (If you're reading this at swik.net or a similar irresponsible republisher, click "Read more" to get the real comments form.)

21 May 2007

Neil Williams: gpe-cash - double entry accounts on handhelds

subtitle: Break up GnuCash into lots of forks

With an ISP problem throttling my broadband to 4000B/s, I've switched to developing in C instead of building Emdebian packages - downloading Debian sources was taking an hour or more even for small packages.

This has made time for a long overdue project: gpe-cash - double entry accounting for handhelds. It's a spin-off from the stalled cashutil project and it just might provide the impetus to get cashutil into a releasable state.

gpe-cash uses QOF (Query Object Framework) which itself was spun out from GnuCash some years ago when it was described as "the gnucash engine without all the financial stuff". So gpe-cash is a happy reunion of the engine and the financial stuff along with Gtk+, only a lot smaller than GnuCash. Yes, it is a fork but a fork done for, IMHO, very good reasons. (Why write free software and then frown on forked projects?) There's little hope of getting GnuCash to run on any embedded hardware (it would probably end up as a laptop instead of a handheld in the process) so it has to be broken up: forked into a few smaller bits and simply dropping larger bits.

I've long wanted to break up the GnuCash behemoth and this is how this fork will work:

  1. Package the basic GnuCash objects as a shared library with -dev, -dbg and -doc

  2. Package the GnuCash business objects as another shared library, with ditto.

  3. Leave the commodity (stocks and shares) objects for a later date due to QOF compatibility issues with the GnuCash code.

  4. Use the pilot-qof Default Currency Table to create a tiny set of gnucash compatible currencies. (Also used by gpe-expenses already.)

  5. Share live expense data with gpe-expenses and gpe-cash (prevent duplication)

  6. Share contacts and live calendar data with gpe-invoice (calculate invoices)

  7. Drop direct file compatibility with GnuCash until GnuCash itself supports a sane backend, a suitable data import or cashutil is fixed, whichever comes soonest.

  8. Retain object compatibility with GnuCash at the QOF level - permits removing certain parts of GnuCash specific code from the objects whilst retaining functionality.

  9. Drop all reports, graphs, CSV import, QIF import, Scheme and other complexity of GnuCash.

  10. Use a simple SQLite backend via QOF.


Best laid plans . . . etc. It always ends up a bit different to the plan but you have to have a plan of some kind. (No?, well I do.) ;-)

The code is a combination of gpe-expenses and cashutil. It will (eventually) live within the cashutil SVN at SourceForge but I haven't committed the first changeset yet. The basic structures already work, it is tying the C objects to the Gtk that is the bulk of the remaining work.

If anyone is interested in upstream development, subscribe to the (very low volume) QOF-devel mailing list and let me know.

Evan Prodromou: 1 Prairial CCXV

I just got back from taking Zach Copley to the airport, and for the first time in a few days I'm sitting in front of my desktop computer again, trying to get back on track. I think it's probably a good idea to get my notes about RoCoCoCamp down on electronic paper while the experience is still fresh in my mind. (I wrote about the first day in Journal/29 Flor al CCXV). Saturday morning I got up considerably later than I had the day before, and I took my time getting to SAT. Which was OK, since things went much smoother in the morning. The only really annoying thing about Saturday was that I had to wash about 50 cups by hand -- we'd run out of clean cups, and I couldn't figure out how to run the dishwasher. It didn't take long, but it meant that I had my head down in the sink as people came in and didn't get to spend as much time talking to them. I was glad to hear that people had a good time going to L'Utopik on Friday night. Apparently a few people who'd flown in late on Friday got a chance to meet up with the experienced crew at L'Utopik, so they were well-prepped for Saturday. Probably the biggest buzz of the pre-sessions was SJ Klein's pair of functional OLPC laptops. They were cute and fun -- I got a few minutes to play with them, and I enjoyed the interface tremendously -- although it took me a few tries to open it. People were fiddling with them throughout the day -- including Amita June, who came late in the afternoon -- and Tristan P loquin even blogged about them. My first session was about wiki and other technologies, which I titled Wiki And.... (I borrowed the name from Last Exit to Brooklyn, in which it seems no-one eats anything but "coffee and".) My main point was that a) wiki people tend to overuse wiki where other software tools may be more appropriate and b) we need to be careful with impedance mismatches when using wiki with technologies with other cultures behind them. Wikis and blogs mismatch; wikis and forums mismatch. You need to work out ways to make them work culturally. As a proof-of-concept that there are ridiculous applications for wiki, I created in about 3 minutes before the session the wikiclock. It's a computer clock that runs on wiki technology: the time is kept up-to-date by human beings editing the page, rather than with software. I was so pleased with myself that I twittered about it, and from there it's taken on a life of its own. The clock is implemented on the amazing minimalist system pageoftext.com. I heard about p.o.t. from Liz Henry's April report from Palo Alto Wiki Wednesday, and I think it's totally great. It's a cross between a pastebin and a wiki -- like an open-edited ImageShack for text. Brilliant. The second session I did was a hyper-focused one on a particular Semantic Web problem. Both Wikitravel and Open Guides have tons of information on "places" in various cities. (That is, restaurants, bars, nightclubs, hotels, museums, parks, etc.). It would be good to export our data on these places to each other, so we could possibly keep them in sync. For example, if a restaurant changes its hours , that info could be updated on The Open Guide to London and automatically synched to the Wikitravel page on London. So we went over some ways to do this kind of interchange; we'd brainstormed before about it on the Open Guides' RDF Workshop, but it was good to sit down with Earle Martin and do some face-to-face hacking on the idea. We don't yet have a vocabulary for it, but we'll get something going on the new wikirdf.org site (which also emerged from this session). I had a great lunch with a lot of people from RoCoCo on the terrace at the Bar St. Sulpice, about 8 blocks away on rue St. Denis. The sun was out, it was cool, and we had a very nice time. It was especially nice to see Marcus Bornfreund and Tina Pipers of Creative Commons Canada, who'd come to talk about the PDwiki, a project to collaboratively document Canadian works in the public domain (see Canadian Public Domain Registry Announced). We talked quite a bit about the social challenges of getting a community excited about such a dry subject, but I think we got some good ideas about it. In the afternoon I led a session on MediaWiki. We were lucky enough to have Tim Starling sit in, and he told everyone about the new developments going on with MW. He's refactoring some very deep parts of the storage and rendering sections of the code, which will result in considerably better reliability, performance, and flexibility. I think it sounds great. I had to work the registration desk for the last session of the day, which was pretty great because I ended up baby-sitting Anoushka Jaroski-Biava for most of the time. But I missed Robin Millette's cool talk about BuzzyBee, which looks to be really fun to play with. We rounded out the evening with music, pizza, and beer at the SAT. tobias.dj played some great dance music, and we had some wiki-collaborative VJ-ing using the SAT's fancy screen systems. All the kids were there -- Mark and Allegra's daughter No ma as well as Amita June. Fun. Sunday morning I didn't have to start coffee until 9AM -- luxury! We had a great Open Space Technology convergence -- a way to turn the discussions of the previous few days into action items for going forward. I did a convergence session on the future of RecentChangesCamp. We had most of the interested parties available (except for the RCC Portland organizers, who had to fly out early that morning). We made some decisions about future RCCs, and we made some plans for next year's RCC -- in the Bay Area (California). Last night we brought back the Keiki gang to our house, since it was great to have them all in Montreal for the event. We did a big brainstorming session on next steps to launching the project, and we also did some graphic design review of potential logos. We have some great designs coming; I'm really happy we got Sarven Capadisli and Bridget to work on the site. I had to crash out at 10:30PM -- Amita and I fell asleep together -- but others were up late talking and thinking. I don't know how they did it -- I was all talked out by the end of RoCoCo. All in all I had a fantastic time -- the event far surpassed my expectations. It was hard -- too hard. I bit off far more than I could chew. But I think we did a good job of establishing Montreal as a technology city -- Wiki City Canada -- in the international mind, and I think we also brought together some really interesting people for some fruitful and productive work. You can see some of the projects that came directly out of RoCoCo on the FutureChanges page -- an ingenious name courtesy of Pm. And there are some indirect ones that we can expect soon. tags:

Cause and solution So, Technorati has a good listing for rocococamp items, but I especially liked Steve Faguy's post: Wiki: The cause of, and solution to, all of life s problems. Steve was an extremely game participant in the event, which I think was pretty incredible. He wrote a good overview of wikis in the Montreal Gazette this year. A funny thing happened on Friday evening during the daily wrap-up known as "Evening News". We had Open Space's minimalist instructions posted on the walls of the SAT, so people would see and remember them. Steve pointed out that the first of Open Space's "four principles" is grammatically incorrect: Whoever comes is the right people. He said, "In the spirit of wiki, I'm going to correct it right now!" And to applause, he got up with a marker and changed the "is" to "are". This stimulated an interesting discussion. One person noted that the "is" is there because possibly only one person could show up for a session, and that's OK. Finally, Brandon CS Sanders stood up and said, "I like 'is' because when we come together like this, we form a cohesive group, however temporary -- 'a people'. So I'm going to change it back." And he did -- to lots of applause, again. Steve came up to me at the end of the night, laughing. "I got reverted! I should have started an edit war!" It was a hoot; he's got a good sense of humour. tags:

20 May 2007

Steve Kemp: He was in a bind 'cos he was way behind

My girlfriend who was returned from hospital on Friday learnt a couple of days later that she d managed to suffer a fractured skull. Apart from that shocking news I ve been doing little. Lots of travelling, lots of tidying up /bin, little else. One new toy is release which will allow me to easily release projects. The idea is you run /bin/release inside a project directory and it will: Very simple, almost trivially so, but it has a lot nicer than having to do all the bits manually. (sample .release file.) I had a piece of code for triggering new freshmeat announcements working a while back but it was a little too fragile when it came to reading the ChangeLog files I use so I ve killed it for the moment. (Probably $EDITOR fresmeat.tmp & would be a better idea anyway!) Connectivity is bad right now, since I m in the middle of changing home ISP, but hopefully that will be resolved in the next week or two. (Switching from Telewest/Virgin -> Sky for people in the UK who might care.)

18 May 2007

Michal Čihař: New Gammu API

Thing I longer wanted to happen is now becoming reality - Gammu is getting new public API. Man reasons for the change are: The work is not yet still complete, but the API is getting final shapes right now, so you still have chance to change something. While doing such big change, I decided also to complete documentation of all public functions. This is also currently work in progress, but arising API documentation is already available. If you are developer using Gammu library, you will have to change some things in your code. To document these changes, new Porting guide has been created. I suggest you not to start with this right now as the API is really not complete and might change a lot during next days.

17 May 2007

Gunnar Wolf: Starting as a mentor soon

After a long time talking this as a mere potential would-be-nice thing, finally we are putting some action behind our words: One week from now, Sergio Mendoza and I will start a ~2 month long extracurricular course on Debian. The students? We have 12 students of the Facultad de Ciencias at my University. The students are pre- and post-graduate (licenciatura and maestr a), from the Phsyics and Astronomy areas. Sergio got this group as he is a teacher and researcher at Instituto de Astronom a.
While this first iteration is completely extra-curricular, unofficial and by invitation only, we expect this pilot course to be later presented as an official course in the Faculty.
Many people will remember I usually don't like general courses on Unix, Debian or whatever. What made me accept this time - even more, be enthusiastic about it? First of all, the requirements: We assume the students already know their way (at least as users) in a multiuser Unix-like system, so we won't be hand-holding them all the way through. Second, the focus: Sergio (who is among the first Debian users in Mexico and who got us our first full Debian mirror - which is actually a bit sick, but awaiting for prompt hardware upgrade ;-) ) wants them to focus on becoming developers. Not only developing science-oriented applications and libraries, but properly packaging and integrating them in Debian (and, hopefully, some of them will become interested in joining the project). We will also spend a good portion of the course on teaching them good practices on system adminsitration, teaching the principles behind what we do (i.e. I'm looking forward to participating, and in this case as one of the more students, in the sessions where different cryptography-related topics will be explained, starting from their mathematical foundations and going all the way up towards the implementation, where I'm more comfortable at).
It will be a nice experiment. I will be away for at least five of the lessons (Blame Debconf!), but I'm really looking towards the process and the results.
We will be making rough documentation of what we teach. We don't have a planned complete program, as we want to go with the group's real skills and interests, planning not more than three lessons ahead. This will be, however unofficial it is, my first time in front of a group in a university-esque setting (i.e. not short sessions, not capacitation built for a company, but with people eager to learn what we want to teach. I'll post again on this topic :)

Russell Coker: Lord of the Flies

Apparently they are planning a reality TV show that might be named “Kids Nation” where 40 children are allowed to develop their own society for 40 days. The claims are that there is “no parental supervision”, but of course with many TV cameras watching I’m sure that even the most stupid children can work out that there are reasons to behave relatively well. Also I’m sure that they will remove children from the show if it becomes necessary to avoid injury. It will be interesting to see how well this develops. Maybe it could evolve into a new form of schooling, just leave children alone in a school with lots of security cameras watching them and let them study or not as they wish. It would be cheaper than running a regular high-school, and as there is little scope for providing a worse education than many (most?) high-schools currently provide it should be worth a try. For a long time I have thought that the premise behind The Lord of the Flies was bogus. I believe that a major contributing factor towards much of the violence that is present in schools is the pointlessness of the entire system. There are very few students who are so stupid that they can’t realise that the education system is failing them. Whenever you put a large number of people in a confined space with nothing useful to do the results will be bad. If a group of students from a violent school were placed on an island without any supplies then I’m sure that they would soon realise that they need to cooperate to stay alive.

Russell Coker: Lord of the Flies

Apparently they are planning a reality TV show that might be named “Kids Nation” where 40 children are allowed to develop their own society for 40 days. The claims are that there is “no parental supervision”, but of course with many TV cameras watching I’m sure that even the most stupid children can work out that there are reasons to behave relatively well. Also I’m sure that they will remove children from the show if it becomes necessary to avoid injury. It will be interesting to see how well this develops. Maybe it could evolve into a new form of schooling, just leave children alone in a school with lots of security cameras watching them and let them study or not as they wish. It would be cheaper than running a regular high-school, and as there is little scope for providing a worse education than many (most?) high-schools currently provide it should be worth a try. For a long time I have thought that the premise behind The Lord of the Flies was bogus. I believe that a major contributing factor towards much of the violence that is present in schools is the pointlessness of the entire system. There are very few students who are so stupid that they can’t realise that the education system is failing them. Whenever you put a large number of people in a confined space with nothing useful to do the results will be bad. If a group of students from a violent school were placed on an island without any supplies then I’m sure that they would soon realise that they need to cooperate to stay alive. Update:
It seems that the Sudbury Valley school implements some ideas similar to mine. They also have a page of links to some other schools that do similar things.

16 May 2007

Adeodato Sim : Better sorting of maildirs in the Mutt browser

I’ve been always dissatisfied with the sort_browser=date option in Mutt, particularly when dealing with maildirs. For me, the reasonable behavior is to sort by the newest entry under the new/ directory, so that reverse sorting places the maildirs with most recent mails first. There is a patch by Dale Woolridge to address this issue, but since it only looks at the mtime of the new/ directory, once new mail has been read in a maildir, it still stays on the top of the list. So for me, the solution was to write an external program that would sort the list of maildirs by the date of the most recent new file, and have mutt read that list. Maybe you find it useful as well.

Michal Čihař: No current Wammu for Windows

You might have noticed that current Wammu is not available for Windows. The reason is simple - I was not able to produce working binary in reasonable time. Python-gammu itself seems to work, but when I run Wammu, it crashes quite soon. I tried to debug it for few evenings, but I was not successful. Therefore I again ask for somebody who would be willing to maintain Windows build. Somebody with Windows experiences will be probably able to resolve problems much faster and will help creating application that will behave good on Windows. I am not able to achieve this as I do not know Windows much and do not use it at all.

Michal Čihař: Wammu 0.20

I just released version 0.20 of Wammu. This is mostly bugfix release, which fixes various bugs reported by users.

14 May 2007

David Welton: mailmodel rails plugin

Here is the first cut at a plugin I created, called Mailmodel. It's pretty simple, you install it, configure the email sender/destination addresses, and then, in your ActiveRecord objects:
after_save :mail_model
For those objects that you want to be notified of when they change. Think of it as 'scaffolding' for email notification of changes in your database (new comments, new users, new payments) when you aren't quite ready to set up notification for each individual thing. Available from: http://svn.dedasys.com/public/mailmodel/ Some improvements that could be made:

12 May 2007

MJ Ray: Compost Awareness Week

Did you know that it's the last day of Compost Awareness Week today (Saturday 12 May)? No, nor did I. I was pretty aware of the compost bin when it flew across the lawn before I bricked it down. Maybe that's not what they meant. Getting a compost bin has reduced our rubbish to less than a bag a week, but we've yet to get any compost yet, after six months of winter. So last week, I tried a coco peat brick that you reconstitute in water. Easy to transport, but it seems to need mixing with regular compost to give a decent growing soil. Are you aware of your compost? Go on, give it a hug. Update: Alex Hudson wrote:
"Actually, I was aware of compost awareness week! We have a nice local website which many local groups use, including EcoLocal - they were doing build-your-own compost bin today, and handing out soil conditioner. I actually built our composter out of fence panels which blew down in winds a while ago, and I like the idea of using wooden/constructed bins than plastic (though I suspect plastic is much more efficient)."
I moved recently. I seem to have some random tiles and bricks, but I left all the wood behind in King's Lynn. The fence panel that was lying around when we saw the house was cleared away before we moved in. I'm not sure that I'm good enough at woodwork to build-my-own anyway. I don't know if plastic is better - I guess it insulates better, but they still tell you to wrap it up in winter, which is nuts: any wrapping would blow away in a storm.

11 May 2007

Edd Dumbill: Up close and personal at XTech

It's been a long time since I last wrote, mostly because we've been pulling out all the stops for XTech. Next week is set to be stimulating and challenging. I'm amazed at the collection of thinkers and innovators we've drawn together, and am looking forward to getting a boost of energy and inspiration from the conference.
Browser summit On Tuesday next week, Molly Holzschlag and I are sponsoring a Web Browser, Standards and Interop Summit. This is an opportunity for browser vendors, standards advocates, W3C and related standards supporters to talk in a vendor (and standards-body) neutral atmosphere about tackling the problem of browser interoperability. As the full announcement mentions, we're also throwing open the doors to interested bloggers and journalists to get involved in and cover the discussion. The summit came about after Molly and I got talking about our desire to provide a forum for effective exchange between the people shaping the future of HTML. This is something that spawned the vision of the Browser Track and XTech in the first place three years ago. I don't know how much we'll solve at the first summit, but it puts down a marker and a challenge for participation. I am not the only one concerned at the increasing fragmentation of the HTML landscape, the breakdown in communication, and the ultimate ill-effects for web developers and users. Personal scheduler and evaluations As my conference software Expectnation nears its public launch, we'll be using some of its fun features at XTech. Normally, the bulk of the work is done behind the scenes, so it's nice to have a feature to show off to attendees and the wider public. Personal scheduler The personal scheduling feature lets you compose your own timetable for the conference, just by clicking on the stars throughout the schedule. As a bonus, you can subscribe to your personal schedule as iCal, allowing you to take it with you on your phone or PDA. In addition, we'll be allowing attendees to submit evaluations of sessions online. If you're using the personal scheduler, it gets even neater as you can quickly find links to submit your evaluations, and review ones you've already submitted. Behind the scenes, I can see which sessions are the most popular and get advance warning if we're likely to need to move rooms to avoid overcrowding. I'm pretty excited about this. Features like this aren't exactly new, but now we've made them a standard feature for every conference. We're looking forward to adding more social software facilities to enhance the conference experience.Submitting session evaluations 

10 May 2007

Piotr Roszatycki: Test::Unit::Lite

I like very much a Test::Unit framework. I've found it as a very handy tool for organising the tests. I really don't like the standard Test::Simple and its deriveratives. I don't understand why I have to see the output for each failed test. I rather like the do-or-die tests grouped logically as test units. Somebody write me a note for Exception::Base module that it depends on non-core Perl modules. It is not for runtime but build dependency. Even that, it is true, because Test::Unit is a somewhat heavy module and it depends on i.e. Errors. I decided to reimplement Test::Unit. So it is available Test::Unit::Lite already! It is much lighter replacement for original Test::Unit. It should be compatible for existing test suites. The intention was possibility of bundling the Test::Unit::Lite with other module distributions:
$ perl -MTest::Unit::Lite -e bundle
It copies the Test::Unit::Lite module to the inc directory in the distribution source. The Test::Unit module isn't perfect. The most annoying behaviour is the random order for calling test cases. The Test::Unit::Lite sorts the function names and calls it always in the same order. There is not so many Perl modules distributions that use Test::Unit. I hope a little that my package could change this situation and the test units will be more popular and easier to use.

9 May 2007

Anthony Towns: Torrenting the Debian Archive

Continuing the theme from my previous post – the first and fundamental thing any distro needs to have, and thus the first and fundamental thing to think about disintermediating, is some way of distributing software. That might be burning CDs and sending them out to resellers or OEMs, or having your stuff available for download, whether by putting it up on your own server, hosting it via a dedicated high-reliability provider like akamai, or maintaining a network of mirror sites and keeping them up to date. And, of course, anyone who wants to distribute their own software has to do the exact same thing – which either means doing it themselves, and not being able to take advantage of the scalability the distributor has already made work, or going through the distribution and dealing with the problems that entails, as well as the benefits. In this case, disintermediation and decentralisation are pretty much one and the same thing: and decentralising content distribution is already a well understood problem: that’s what peer-to-peer is all about, and peer-to-peer distribution of, well, distributions is already very successful – at least when it comes to CD (and DVD) images. Which means that just about anyone can create a CD image, and distribute it to the world in exactly the same way a major organisation like Debian or Red Hat would – upload a torrent file, run a seed, and let the magic of BitTorrent do its thing. Scalability is no longer something you need a distribution organisation to manage, instead it’s built directly into the technology itself. Unfortunately BitTorrent is designed for large static images – not something you update on a daily basis. And for better or worse, my preferred distribution (Debian testing, currently lenny) does update that frequently. Fortunately, though, BitTorrent’s an open protocol and has dozens of open source implementations – so last year I was able to propose it as part of the Google Summer of Code, and was lucky enough to get a few responses and a student to work on it. It didn’t get much further than that unfortunately – the student lost internet access not long into the programme (and for most of its duration), and that was pretty much that. So when this year’s SoC rolled around, I didn’t really expect much, and didn’t put the idea up for consideration again, but lo and behold someone came through and asked if it was still possible and if there was any more information, and when I forwarded on some of the mails from the previous year we ended up with a second chance at the project. So far it’s looking pretty good – we’ve had a lot more success at keeping in touch, and thanks to the extended schedule for the SoC this year we’ve been able to do a much better job of keeping on top of what’s going on. So much so, in fact, that there’s a first (alpha) release out before the SoC is officially due to start! Wonderful stuff! What it does at the moment is allow you to take a Packages file (the stuff “apt-get update” downloads, which includes descriptions of all the packages that are available, how they inter-depend, and so forth), and from that information create a usable torrent from which to obtain the packages themselves which can then be used to share and distribute the packages. There are two crucial steps in that: the first is allowing the torrent to work without requiring huge amounts of extra information to be distributed (which would introduce scalability problems of its own, instead of solving them), and the second is that the pieces that make up the torrent are selected in a way that matches the actual packages, so that when you upload a single new package, you are in fact only making a minor change to the torrent, rather than having it (on average) completely redefine half of the torrent (and again introduce scalability problems rather than solve them). There’s more information on the DebTorrent wiki page and Cameron’s blog if you’re interested. Anyway, it’s just an alpha release at the moment, which means while there’s code that does something, it’s not actually all that useful yet. The current plan is to next add some code to make it automatically prioritise packages based on what you’re actually using – so that rather than downloading all the debs it see, it’ll only download the ones you’ve got installed, or maybe only newer versions of the ones you’ve got installed, which should get us pretty close to the point where it’s actually useful for something. The end result, of course, is to build a tool that you can point at a Debian archive, run it on a machine connected to the Internet, and you won’t have to do anything more to have a reliable, scalable and reasonably efficient means of allowing your users to distribute and update their systems. In this case, scalable means that if you end up with as many users as Debian or Ubuntu, your users will have a comparable experience, as if you’d arranged for a similarly comprehensive mirror network, without actually having to do the leg work. And heck, presuming that works, it doesn’t even matter if no one else actually does that – it’s worth it even if it saves Debian or Ubuntu the effort of keeping track of a mirror network by hand. There are interesting possibilities at smaller scales too, of course. :)

Junichi Uekawa: Hypothesis about number of Debian installations, from apt-listbugs logs.

I've analysed merkel.debian.org access logs.Since etch was released, 30000 unique IPs were used to accessmerkel.debian.org using apt-listbugs.According to popcon, 3% of all Debian installations install apt-listbugs.Let me add three simplifications to the equation.(A) popcon models Debian user installation behavior reasonably well. (Decision to install apt-listbugs and popcon (which both happen to be applications requiring network connection and leak information about what packages are installed on your system) are independent.)(B) A unique IP represents a single system (Even though DHCP may change IP address over a month's period, NAT may share IP addresses, and ignore everybody who's working offline).(C) All Debian installations are using Debian etch, lenny, or sid (no old distributions).I can assume with these three conditions that there are 1,000,000 Debian users worldwide.Does this number sound big or small to you?UPDATE: since it looks like this topic is very interesting, and I'm receiving a lot of comments, I've reposted the contents to debian-devel, so that it's much easier to discuss.Lemmesee.

Michal Čihař: python-gammu has asynchronous wrapper

Yesterday I hacked asynchronous wrapper for python-gammu. It is start of progress to make Wammu behave better while talking to phone. My plan is that all operations will go through this asynchronous wrapper and will be completely non blocking to Wammu. This means no progress bar will pop up to front, but entries will appear in window as they are being read. Progress will be of course still shown, but only in status bar. The current code is only first step, next thing which has to be implemented in python-gammu are virtual commands. Those will be used for things like getting all calendar events from phone, so all you will have to do for getting all is enqueue GetAllCalendar event and worker will do all for you including progress reporting. If you want to write own application using this new wrapper, you can look at example which is in sources. It shows all current possibilities, but it will be enhanced in future.

8 May 2007

David Welton: Rails bitten by Ruby's nil.to_f

I guess I'm still new enough to Ruby that this does not make sense to me:
>> nil.to_f
=> 0.0
Magically, from nothing, you have something. I suppose it might be convenient in places, but today I ran into a minor bug in Rails that causes problems when trying to get the average of a column that doesn't have any entries. So what is the reasoning behind nil.to_f being 0.0 (and nil.to_i being 0, to_s being ""), anyway?

7 May 2007

Neil Williams: Smaller libc6

libc6 is by far the largest package in the current Emdebian repository and as part of a rootfs it is simply overpowering. So various ideas cropped up on Emdebian IRC. Split the gconv libraries into three or more packages. Split the binaries into a new package and split out libnss into another. Have to see how if pans out and whether an over-arching pseudo package is needed later to make it easier to package reverse dependencies of libc6.

(Yes, uclibc is an option and Emdebian is actively working on that too but it would be nice to be able to have the flexibility of something inbetween uclibc and the behemoth that is Debian libc6.)

Next.

Previous.