Search Results: "ag"

22 January 2009

Jose Luis Rivas Contreras: libtorrent 0.12.3 and rtorrent 0.8.3 released! (beta)

So between yesterday and today I packaged the new upstream version of libtorrent/rtorrent 0.12.3 and 0.8.3 as beta. I still need to do some testing on the packages and maybe change libtorrent from OpenSSL to TLS. Anyway, in the meantime you can grab the binaries (only 386) and sources from my debian-playground:
http://debian.rivco.info/libtorrent/0.12.3-1~b2.exp/
http://debian.rivco.info/rtorrent/0.8.3-1~b1.exp/
(there may be new beta versions at the time you read this so please check as well the parent directory) Or my repo:
deb http://reprepro.deb.rivco.info/ experimental main
Hopefully they'll be available soon from the Debian Archive, just need to check some stuff before that. Anyway, they're fully working right now.

Jose Luis Rivas Contreras: new libtorrent and rtorrent (beta, again!)

I think Jari reads my blog haha. There are shiny new packages for libtorrent and rtorrent. The same place as ever: My debian-playground: http://debian.rivco.info/ My private repo: deb ,-src http://reprepro.deb.rivco.info/ experimental main And of course, git (checkout master-experimental and upstream-experimental): http://git.debian.org/?p=collab-maint/libtorrent.git http://git.debian.org/?p=collab-maint/rtorrent.git

Benjamin Mako Hill: Annual Free Software Foundation Fundraiser

When I explain the importance of free software, I often use some variation of the following example:
Suppose I see a beautiful sunset and I want to describe it to a loved one on the other side of the world. Today's communication technology makes this possible. In the process, however, the technology in question puts constraints on message communicated. For example, if I pick up my cellphone, my description of the sunset will be limited to words and sounds that can be transmitted by phone. If I happen to have a camera phone and the ability to send a picture message, I will be able to communicate a very different type of description. If I'm limited to 150 characters in an SMS message, my message will be constrained differently again.
The point of the example is this: the technology I use to communicate puts limits and constraints on my communication. Technology defines what I can say, how I can say it, when I can say it, and even who I can say it to. This is neither good nor bad. It is simply the nature of technology. But it means that those who control our technology control us, to some degree. As information technology becomes increasingly central to our lives, the way we experience, understand, and act in the world is increasingly controlled by technology and, by extension, by those who control technology. I believe that the single most important struggle for freedom in the twenty first century is over the question of who will set these terms. Who will control the technology that controls our lives? Free software can be understood as an answer to this question: An answer in the form of an unambiguous statement that technology must be under the control of its users. When free software triumphs, we will live in a world where users control their technological destiny. We simply cannot afford to fail. The Free Software Foundation is the most important organization fighting for the rights of users in this struggle. Here are some of the ways that I plan to direct the FSF to support software freedom in the coming year:
Network Services Last year, the FSF organized a meeting on software freedom and network services that lead to the creation of the Autonomo.us group and the release of the Franklin Street Statement on Freedom and Network Services. As network services --- like those built by Facebook, Google, and others --- continue rise in popularity, progress in this conversation is of increasing importance. This year, I will direct the FSF to build on the work of Autonomo.us to launch the first of what I hope will be several FSF position statements on software freedom and network services. More importantly, the FSF will begin to provide support and planning for solutions --- technologies, social campaigns, and legal steps --- that will protect computer users whose freedom is currently threatened by network services. Enforcing free software licenses Early on, people who decided to work on free software did so because they agreed with --- or, at the very least, were willing to abide by --- the principles and rules laid out in our licenses. In our push for software freedom, we have created software of immense value and attracted companies and individuals to our community who are less willing, or simply less interested, in protecting users' freedom. In December 2008, the FSF went to court for the first time in the organization's history to force Cisco to uphold the freedom of the users of FSF copyrighted software. This lawsuit asks Cisco to live up to its obligations under the GPL and to ensure that it does so in the future. The FSF needs the support of its community in this and in future enforcement actions. The FSF has operated a compliance lab for several years and has ensured software freedom for countless users. As free software becomes more successful in the next year, the FSF will be playing an increased role in protecting software freedom from those who do not share its principles. Continuing the fight against software patents As I said last year, one cannot write non-trivial software today without running a serious risk of infringing patents. The software patent minefield we've found ourselves in is a very fundamental threat to the success of free software and we've already begun to see the first casualties and costs. We must eliminate software patents. Now. The FSF will continue its work toward this end. The FSF's End Software Patents project's major contribution this year was a brief submitted in the In Re Bilski case at the U.S. Court of Appeals for the Federal Circuit. Recently, an opinion was issued which seems to mark an important shift away from broad protection for software patents. With this victory, now is the time to keep up this momentum. The FSF is drawing up a strategy to do just this and will be announcing the relaunch of its campaign on February 9,2009 led by Ciaran O'Riordan.
Every recent fundraising appeal seems to mention the difficult economic climate and it seems to cliche to do so here. That said, the effect of a bad economy is, in fact, felt most strongly in non-profits dependent on donations. The FSF is not immune. The FSF's work is essential for success on the issues I've described here and on all of its other campaigns and projects. Although the cost of a membership or donation may be less easy to afford this year for many of you, the free software movement cannot afford a weakened FSF at this important moment. If you are not an FSF associate member, now is the time to become one. If you are already a member, please join me in giving generously through a tax-deductible donation. The FSF is a very lean, very humble organization of passionate and dedicated individuals working tirelessly for software freedom. Every single gift makes a difference.

David Welton: Github Part III

Since this seems to be fairly constructive, I'll keep going. Those not interested in Github, or the dynamics of open source code creation can safely tune out. Chris, the Github dude, has some more to say: http://ozmm.org/posts/forking_continued.html
I mentioned the Network Graph and Fork Queue but David mentioned neither. I think he doesn t know what they are, probably because I didn t explain what they are :)
I had had a look at them, and they're handy tools (I would never accuse Github of not doing good work, that's not the issue at all), but I would respectfully submit that perhaps Chris is looking at things from a very Github-centric perspective, in which it's second nature to go look at those. They aren't obvious, and certainly don't jump out at the user to say "hey, maybe this code your looking out isn't the latest and greatest!". For someone just cruising around, perhaps it should be more evident who's the 'top dog'? Chris then goes on with a very helpful and illustrative demo of how things work at Github, which is good stuff. However, at the end, he says something that I don't agree with:
It may seem strange, and perhaps even like a lot of work. Why should I have to check to see which is the most current? In the old model, there s always a canonical repository.
That's precisely the problem. It does seem like a lot of work, especially when your search space is not limited to Github, but may include other places like Sourceforge, RubyForge, Google Code, project specific sites, and so on.
In the old model, actionwebservice wouldn t have made it past 1.2.6. Welcome to distributed version control.
Plenty of 'old style' projects have survived beyond their founders' interest in the project. What happens is that you ask for permission to work on the project, and either :
  1. It's given to you, in which case you can keep working on the canonical code. For instance, someone could have asked DHH to work on the RubyForge version of actionwebservice. Did they? Did he say no? At the very least, he could have been asked to point the RubyForge actionwebservice page at some other site with a more current version of the code.
  2. You have to fork the project, and in that case, sure, you might as well have been using the Github model.
I've often found that people are happy to let you contribute to their projects, though, and part of my original point with all of this is that if people just go spitting out forks willy-nilly, it creates a "paradox of choice" type problem, and perhaps takes something away from the community aspect of open source projects. As people are fond of saying at the Apache Software Foundation, it's about the people, not necessarily about the code. I'm not saying that forks are always bad and that everything should be centrally done, but there's a balance to be struck between people just working on their own, and some sort of onerous, bureaucratic Central Project Authority. It's nice that people who want to improve the code make themselves heard on a mailing list/forum/whatever, and thus cover the "people" part of merging in new code and new ideas. More often than not, help and contributions are more than welcome. Design decisions and conversations recorded on mailing lists are available for people to peruse in the future when they have questions. Just to repeat something that bears repeating: I am not claiming that Github will lead to social disintegration of open source projects or anything drastic like that. However, I'm a bit wary of certain patterns I've seen. It's certainly possible that I'm wrong - as I mentioned, one error I might be making is that people are dumping code they simply wouldn't have shared on Github, because Github makes it so easy. I do hope my worries are unfounded, and in any case, it's a good thing that the Github guys are interested in the problem too, and will hopefully do things to alleviate it where possible.

David Welton: Github Part III

Since this seems to be fairly constructive, I'll keep going. Those not interested in Github, or the dynamics of open source code creation can safely tune out. Chris, the Github dude, has some more to say: http://ozmm.org/posts/forking_continued.html
I mentioned the Network Graph and Fork Queue but David mentioned neither. I think he doesn???t know what they are, probably because I didn???t explain what they are :)
I had had a look at them, and they're handy tools (I would never accuse Github of not doing good work, that's not the issue at all), but I would respectfully submit that perhaps Chris is looking at things from a very Github-centric perspective, in which it's second nature to go look at those. They aren't obvious, and certainly don't jump out at the user to say "hey, maybe this code your looking out isn't the latest and greatest!". For someone just cruising around, perhaps it should be more evident who's the 'top dog'? Chris then goes on with a very helpful and illustrative demo of how things work at Github, which is good stuff. However, at the end, he says something that I don't agree with:
It may seem strange, and perhaps even like a lot of work. ???Why should I have to check to see which is the most current? In the old model, there???s always a canonical repository.???
That's precisely the problem. It does seem like a lot of work, especially when your search space is not limited to Github, but may include other places like Sourceforge, RubyForge, Google Code, project specific sites, and so on.
In the old model, actionwebservice wouldn???t have made it past 1.2.6. Welcome to distributed version control.
Plenty of 'old style' projects have survived beyond their founders' interest in the project. What happens is that you ask for permission to work on the project, and either :
  1. It's given to you, in which case you can keep working on the canonical code. For instance, someone could have asked DHH to work on the RubyForge version of actionwebservice. Did they? Did he say no? At the very least, he could have been asked to point the RubyForge actionwebservice page at some other site with a more current version of the code.
  2. You have to fork the project, and in that case, sure, you might as well have been using the Github model.
I've often found that people are happy to let you contribute to their projects, though, and part of my original point with all of this is that if people just go spitting out forks willy-nilly, it creates a "paradox of choice" type problem, and perhaps takes something away from the community aspect of open source projects. As people are fond of saying at the Apache Software Foundation, it's about the people, not necessarily about the code. I'm not saying that forks are always bad and that everything should be centrally done, but there's a balance to be struck between people just working on their own, and some sort of onerous, bureaucratic Central Project Authority. It's nice that people who want to improve the code make themselves heard on a mailing list/forum/whatever, and thus cover the "people" part of merging in new code and new ideas. More often than not, help and contributions are more than welcome. Design decisions and conversations recorded on mailing lists are available for people to peruse in the future when they have questions. Just to repeat something that bears repeating: I am not claiming that Github will lead to social disintegration of open source projects or anything drastic like that. However, I'm a bit wary of certain patterns I've seen. It's certainly possible that I'm wrong - as I mentioned, one error I might be making is that people are dumping code they simply wouldn't have shared on Github, because Github makes it so easy. I do hope my worries are unfounded, and in any case, it's a good thing that the Github guys are interested in the problem too, and will hopefully do things to alleviate it where possible.

Y Giridhar Appaji Nag: The Mozart of Madras

I have been listening to music from the Laya project since a few days. It is a set of CDs I picked up from an interesting hippie-ish place called Psybabas on Castle street. Actually, one rarely gets to listen to such sounds. Ideas of similar music can be found scattered in the movies from the early 90s; Hai la sa reminds me of ETilOni sEpalanTa from donga donga. My favorite track though is LA ilAha ill-Allah which sounds very fresh and different from how one would expect it to be.

On a related noted, ETilOni sEpalanTa was composed by A. R. Rahman. I have great respect for the gentleman and recently H pointed me to an article in Tehelka titled The Mystic Master. While a lot has been written about him recently, mostly in the backdrop of The Golden Globe that he won, this article dwells on the person unlike probably anybody did before. Must read.

Adrian von Bidder: The Most Important Announcement of 2008

... and I completely missed it. I've been ranting on and off about the Linux desktop world needing a shakeup, about non-techies shaking their head and not understanding why a Linux Desktop needs further clarification so that anybody knows what it means. Seems I'm absolutely not the only one: KDE's aKademy conference and GNOME's GUADEC are to be held side by side as the Gran Canaria Desktop Summit 2009 in early July this year. I finally saw this in connection with LWN's coverage (subscriber only at this time, sorry) of the recent Qt relicensing by Nokia. The true Year of the Linux Desktop finally? I doubt it, seeing that many people with little computer skills are still completely unaware of what's happening. And currently, I share the pessimism about OpenOffice.org's future as shown in Michael Meeks' interpretation of the commit stats. A real killer in the collaboration platform space is still missing, as well: there are numerous commercial players, quite a few commercial pseudo-opensource packages, tons of real opensource frameworks, but none that can be recommended, in my opinion, without its share of doubts, either about the features, the licensing, or the future. Still, it's been the year of the Linux desktop for me since about 1997 (and that means Debian since not long after that), and I do see the situation improving year for year, so here's a big thank you to all working on it.

Daniel Kahn Gillmor: Trancendental Nonsense and the Functional Approach

Poking around the web site for Law in Contemporary Society, a class taught this semester by Eben Moglen, (who is counsel for the Free Software Foundation and founder of the Software Freedom Law Center), i found Felix Cohen's Trancendental Nonsense and the Functional Approach, which (according to wikipedia) is one of "the most-cited law review articles ever written". I haven't read the whole thing yet (and i'm neither a lawyer nor a philosopher) but it's fascinating reading. And from what i've read so far, it's a strong push toward directly addressing the values that lie hidden beneath our technical or mechanical decisions, and to avoid mistaking technical success or skill with a worthwhile outcome and clear goals at a societal level. This is something we software developers and system administrators struggle with as well (or at least i think we should). It's neat to get my head around these concepts from a different intellectual sphere, and a different era (74 years ago!) when the technical and mechanical tools i work with didn't exist in anything like their present form. This kind of reading makes me wonder what works from Computer Science or Systems Engineering or Information Technology will have this kind of exhortative power and social relevance so far into the future. Do you have a favorite (or abhorred?) text from your field that offers the kind of moral and technical challenges that Cohen's work does?Tags: law, moglen, philosophy

John Goerzen: Hope

Our power alone cannot protect us, nor does it entitle us to do as we please. . . Our security emanates from the justness of our cause; the force of our example; the tempering qualities of humility and restraint. - Barack Obama, inaugural speech, Jan. 20, 2009
This, right here, is why, for the first time in my life, I actually feel good about an American president. Why I have hope about our government for the first time in years. Why I m glad I used a vacation day to sit on the couch and watch TV yesterday. On the occasion, once every 4 or 8 years, that is a celebration of American strength, power, and pride, we see our new president speaking of humility, of peace, of moral leadership, this is something remarkable. Past presidents have used occasions such as these to speak of crushing our enemies, of wanting people dead or alive, of grand government promises that turned out to triple the national debt. Obama spoke of extending the hand of friendship to anyone that would unclench their fist. He spoke that we had kicked the can down the road too far, and now we ve reached the end of the road. We have to stop thinking that we can have everything: low taxes, expensive programs, and a large military, simply by mortgaging our future. And he leveled with us: we all are in this together, and all have to work to make it better. Conventional politicians assumed it would be political suicide to say even half of what Obama has said. Yet he went out there and did it. He was blasted during the campaign by people on both sides of the political spectrum for being just words . He s the first presidential candidate that meant what he said about bringing Americans, and their representatives, together. The shock in Washington has he invited gasp! both an openly gay bishop and an anti-gay evangelical minister to give prayers was telling. It s as if people were saying, Wait, he really MEANT that? Yes, he did. Let s hope he can pull it off. And as Rev. Lowry concluded with his benediction:
With your hands of power and your heart of love, help us then, now, Lord, to work for that day when nations shall not lift up sword against nation, when tanks will be beaten into tractors, when every man and every woman shall sit under his or her own vine and fig tree and none shall be afraid, when justice will roll down like waters and righteousness as a mighty stream. . . Let all those who do justice and love mercy say Amen. (amen) Say Amen! (Amen!) Say Amen! (AMEN!)

Joerg Jaspert: Bugs, Bugs, Bugs and a nice speed improvement

This all started when a DSA (Debian SysAdmin (those with root rights on all .debian.org machines)) wanted to upgrade the kernel running on our ftp-master host. It was shortly before dinstall, but hey, there it went, and the machine rebooted into a 2.6.28. Besides murphy taking his share making the machine fsck its huge filesystem that is all fine. What wasn t fine was the result we found. An odd one. Suddenly one tool we run during our dinstall run decided to blow up. Well, it did nt break, it just went dead-slow. Usual runtime had been about 5 minutes before, now we had over an hour - and only about 20% of the work was done. YUCK. Thats sure not going to work. Reboot in a 2.6.27 kernel did not show this problem, going back to .28 had it again. Which meant we had yet another reboot to get a working system. At which point investigation of the problem started. Turns out that pythons popen2.popen2 function is closing all available filehandles before it forks. Thats all fine and also what you usually want. Problem is (and all the glory to have found the cause goes to Peter weasel Palfrader) that the .28 kernel included a patch titled rlimit: permit setting RLIMITNOFILE to RLIMINFINITY (0c2d64fb6cae9aae480f6a46cfe79f8d7d48b59f) that allows, as the title implies, to set the limit for number of files to infinity. More citation from weasels mail: Closer investigation showed that the broken default ulimit did not apply to system processes (like stuff started from init). In the end I could establish that all processes that passed through pam_limit at one point had the bad resource limit. Apparently the pam library in Debian etch (4.0) initializes the limits to some default values when it doesn t have any settings in limit.conf to override them. Turns out that for nofiles this is RLIMINFINITY. Commenting out case RLIMITNOFILE in pam_limit.c:267 of our pam package version 0.79-5 fixes that - tho I m not sure what side effects that has. Debian lenny (the upcoming 5.0 version) doesn t have this issue as it uses a different pam (version). So, whatever the fix might be for etch, if any, there is no way we Ftpmaster can force DSA to live with a 2.6.27 kernel forever on our host. As the problem occurs when using popen2 - lets get rid of it. Luckily popen2 was used in dak by people that either did not know the gzip module python has, or it has been there since before that exists. Don t know, but that made removing popen2 a not too hard deal, done by our newest addition to the Ftpteam, Mike O Connor, stew (Thanks!). A pretty nice side effect is a huge improvement to the speed of the tool Prior, using popen2, it took around 5 minutes to do its job. Now using the gzip module we are down to some 44 seconds. Yes, below one minute, but well, must have some effect if you stop forking a thousand times and all that thousand times close all (1024) available filehandles But that alone isn t enough. There was a second tool also using popen2 (thankfully only once instead of a million times). Fixing that tool got its runtime from 2 minutes down to 0.7 seconds. Yes, less than one second, getting the same result out. Thats the gain you get from not going like get a tempfile, zcat foo > tempfile, filehandle=open(file), dowork including reading its content but foo=gzipfile.readitscontents, dowork(foo) . I like it. And am now sure that avoid popen2 at nearly all costs, if you can is a good motto. :)

21 January 2009

Joachim Breitner: darcswatch uploaded to hackage

I just made my first upload to hackage (not counting uploads I did during my work in Dresden). Don Steward repeatedly told me to package and upload darcswatch, so I just did that. Thanks to Gwern Branwen to contribute the first cabal file.There is little documentation on how to set up darcswatch yourself, so if you actually want to try it out, you most likely will have to get in touch with me. Note that you can just use the installation on http://darcswatch.nomeata.de/.If you, for some reason, feel like hacking on darcswatch, I d be interested in memory reduction. I currently process 916 mails containing 1867 patches and 47MB, as well as 13 repositories, some of which are rather large, and the numbers are increasing.

Axel Beckert: Tablet Amora runs on the OpenMoko FreeRunner (updated)

Amora ( A MObile Remote Assistant ) is a client/server suite which allows you to remote control an X desktop using a bluetooth enabled mobile phone. Initially there was only a Symbian client (running e.g. on nearly all Nokia E and N series phones), but J2ME clients are under developement, too. Then there is Tablet Amora (aka Tamora), an Amora proof of concept client for the Maemo platform which runs on internet tablets like e.g. the linux based Nokia N770, N800, and N810. Since Maemo isn t that far away from what runs on the OpenMoko, getting Tamora working on the OpenMoko, too, suggested itself. Maemo seems to use the deb package format, too, just slightly extended (e.g. by package icons), so it wasn t even that hard work to adapt the existing Maemo packaging to build, install and run on Debian, too. So that s how Tamora looks on the OpenMoko:
The packaging is still far away from Debian standards (throws tons of lintian warnings and the source package generation is b0rked), so yet there are no prebuilt debs available, but you can checkout amora-client from the Subversion repository and build the package from there:
 $ svn checkout http://amora.googlecode.com/svn/trunk/amora-client/maemo/ amora-client
 $ cd amora-client
 $ debuild -uc -us
 $ cd ..
 # dpkg -i amora-client_0.1-2maemo+openmoko_all.deb
For running and installing tamora you need packages from the pkg-fso APT repository on alioth. And to build it, you need the libedje-bin which is available from the pkg-fso repository for at least the armel architecture, or else from Debian experimental. You can add these repositories to your sources.list as follows:
 # PKG FSO repository
 deb     http://pkg-fso.alioth.debian.org/debian unstable main
 deb-src http://pkg-fso.alioth.debian.org/debian unstable main
 # Debian Experimental
 deb     http://ftp.ch.debian.org/debian experimental main
 deb-src http://ftp.ch.debian.org/debian experimental main
Since Tamora is yet only a proof of concept client, currently only the following remote functions are available: This should though at least suffice for a presentation with the OpenOffice.org Presenter. To use Tamora to remote control your Debian laptop, you need a bluetooth dongle (or builtin bluetooth support) and amora-server installed as with the Symbian S60 (3rd Edition) Amora client, too. Update, 23:51 libedje-bin seem not available in the pkg-fso repository for every architecture. You ll also find it in Debian experimental. Updated the sources.list section above appropriately. Thanks to Sebastian Montini for pointing out this problem.

Kyle McMartin: fudcon f11

I was in Boston last week for FUDcon F11. As usual, despite bringing several tonnes of camera gear, I couldn t be bothered to pull it out aside from a few (terrible) casual shots. But hey, I m not big on being spontaneous. Anyway, the two hackfest days were really productive (as were the days I managed to make it out to the Red Hat office.) Although sadly we didn t make it into MIT for the Sunday hackfest day, due to the weather and the Sunday bus schedule in Arlington. paul's intro session Instead of DaveJ doing his usual what s going on in the kernel for F$next I pitched that session and Dave held a session on dracut, he and Jeremy s new framework for building initramfs. My session was well attended and got a lot of questions about various things like the new drivers/staging policy (though, that s a post for another time.) dcbw and notting The rest of the time was productively spent poking at updates for the kernel for F9 and F10, rebasing them to 2.6.28, and poking at 2.6.29-rc1 for rawhide. This meant btrfs, while not ready for your critical data, was in mainline! After pushing out the new build, I spent most of the weekend doing some btrfs testing, and pushing out a new btrfsprogs build. Once they were composed into rawhide, I believe Fedora became the first to ship the mainline working btrfs in a distro. paul's closing session All said, it was a fairly productive weekend, and FUDPub on Saturday night was a great chance to catch up with a bunch of my coworkers who I rarely get to see. I kind of wish I had bothered to set up an umbrella and get some decent shots of my friends, colleagues and coworkers having a raucous good time, but oh well, there s always next release. off-topic
I absolutely hate being politic, and desperately hate posting about life or whatever, since I don t care about yours and don t see why you should care about mine, but the callous arrogance of these striking transit workers here in Ottawa is beginning to irritate me. These are people who ve threatened to picket students attempting to get to school if the universities accepted funding from the municipal government to continue to run replacement shuttles, and (though they ve reached a side agreement now) had threatened to picket for attempting to hire more drivers to increase their ParaTranspo service which provides shuttle services for the elderly and less-able-bodied residents of Ottawa. My point is, one of the shops I walked past on the high street yesterday said it best: Caution, possibly NSFW depending on your point of view. Given that I live in a (fairly) suburban part of Ottawa, this means I get to enjoy a forty minute walk to the nearest (competent) grocery store or coffee shop, and haven t bothered much. But hey, wonderful North American urban planning strikes again. Huzzah.

David Welton: More Github

Before I get started, I want to make it quite clear that I have no problems with Github - au contraire, they provide a very nice service. What my speculation centers around is the social dynamics of Github. One of the Github guys writes a nice response to my original post, here: http://ozmm.org/posts/linux_vs_classic_dev_style.html First of all, apologies for the comment bug. In theory, it has been fixed by the Typo guys, I just need to find the time to upgrade. Chris mentions that it's possible to create a "SourceForge style" project on Github. I see that it's possible to add collaborators, so I guess that's what he means. I still find it a bit ugly to have things at .../davidw/... but that's not very important if the URL is at least stable, rather than hopping around to whoever has the latest fork and updates of the code in question. In my other post, I talked about people being less interested in doing what it takes to contribute to existing projects, rather than forking them, unless it's really called for. Here's a concrete example of how things might go wrong. At my current consulting gig, we were looking at utilizing actionwebservice to do some SOAP stuff. That code is not part of Rails anymore, but that's not the problem - surely someone has decided to take up maintenance of the gem, right? Well, yes... but let's look:
root@fortrock:~# gem1.8 search -r actionwebservice
*** REMOTE GEMS ***
actionwebservice (1.2.6)
datanoise-actionwebservice (2.2.2)
dougbarth-actionwebservice (2.1.1)
nmeans-actionwebservice (2.1.1)
So we have the original, clearly out of date, and three others. Yuck... I guess we'll use the 2.2.2 one, but who knows if perhaps the others contain some good stuff too? Let's Google it. http://www.google.com/search?hl=en&q=actionwebservice The first link is to a RubyForge project, which is basically dead. A few links down, there is a link talking about a more recent version, at the Datanoise site. However, it's one of many. Confusing. If you go to the github page for the datanoise version of actionwebservice, the README has this:
The latest Action Web Service version can be downloaded from http://rubyforge.org/projects/actionservice
Hrm. We were just there and that doesn't seem quite right... Sure, it's an easy enough oversight to ignore, but it adds to the confusion. Now, this is not really a serious problem, but do you see how it could get worse over time, as various people fork the code, write blog entries, and so on? It would get harder for someone interested in utilizing the code in question to ascertain which is "the" version. It's not hard to imagine situations where two forks add different bits of useful code. Typically, in situations like this, new users, those who don't know the code at all, are also the people least able to look through all the diffs and changes and log entries and what not in an attempt to merge any changes that might be useful. This leads to a "paradox of choice" type of problem. Another consideration, this one more positive, is that perhaps people are putting code in Github that, in the past, might have simply remained on their own computers, with no effort whatsoever to share it, so in that sense, Github might be doing people a service by at least making the code public. However, even in that case, if the service fills up with code that people have simply "thrown over the wall", rather than creating a genuine open source project, with a community, communication channels, and so on, it could get a reputation for having code that you have to handle with care, as a lot of is just stuff slapped up there without much thought to quality or continuity. Anyway, the Github guys have done a nice job with the service, and I'm sure they'll continue to improve it. Who knows, perhaps they have some good ideas about mitigating some of these potential problems that they'll be rolling out soon.

David Welton: More Github

Before I get started, I want to make it quite clear that I have no problems with Github - au contraire, they provide a very nice service. What my speculation centers around is the social dynamics of Github. One of the Github guys writes a nice response to my original post, here: http://ozmm.org/posts/linux_vs_classic_dev_style.html First of all, apologies for the comment bug. In theory, it has been fixed by the Typo guys, I just need to find the time to upgrade. Chris mentions that it's possible to create a "SourceForge style" project on Github. I see that it's possible to add collaborators, so I guess that's what he means. I still find it a bit ugly to have things at .../davidw/... but that's not very important if the URL is at least stable, rather than hopping around to whoever has the latest fork and updates of the code in question. In my other post, I talked about people being less interested in doing what it takes to contribute to existing projects, rather than forking them, unless it's really called for. Here's a concrete example of how things might go wrong. At my current consulting gig, we were looking at utilizing actionwebservice to do some SOAP stuff. That code is not part of Rails anymore, but that's not the problem - surely someone has decided to take up maintenance of the gem, right? Well, yes... but let's look:
root@fortrock:~# gem1.8 search -r actionwebservice
*** REMOTE GEMS ***
actionwebservice (1.2.6)
datanoise-actionwebservice (2.2.2)
dougbarth-actionwebservice (2.1.1)
nmeans-actionwebservice (2.1.1)
So we have the original, clearly out of date, and three others. Yuck... I guess we'll use the 2.2.2 one, but who knows if perhaps the others contain some good stuff too? Let's Google it. http://www.google.com/search?hl=en&q=actionwebservice The first link is to a RubyForge project, which is basically dead. A few links down, there is a link talking about a more recent version, at the Datanoise site. However, it's one of many. Confusing. If you go to the github page for the datanoise version of actionwebservice, the README has this:
The latest Action Web Service version can be downloaded from http://rubyforge.org/projects/actionservice
Hrm. We were just there and that doesn't seem quite right... Sure, it's an easy enough oversight to ignore, but it adds to the confusion. Now, this is not really a serious problem, but do you see how it could get worse over time, as various people fork the code, write blog entries, and so on? It would get harder for someone interested in utilizing the code in question to ascertain which is "the" version. It's not hard to imagine situations where two forks add different bits of useful code. Typically, in situations like this, new users, those who don't know the code at all, are also the people least able to look through all the diffs and changes and log entries and what not in an attempt to merge any changes that might be useful. This leads to a "paradox of choice" type of problem. Another consideration, this one more positive, is that perhaps people are putting code in Github that, in the past, might have simply remained on their own computers, with no effort whatsoever to share it, so in that sense, Github might be doing people a service by at least making the code public. However, even in that case, if the service fills up with code that people have simply "thrown over the wall", rather than creating a genuine open source project, with a community, communication channels, and so on, it could get a reputation for having code that you have to handle with care, as a lot of is just stuff slapped up there without much thought to quality or continuity. Anyway, the Github guys have done a nice job with the service, and I'm sure they'll continue to improve it. Who knows, perhaps they have some good ideas about mitigating some of these potential problems that they'll be rolling out soon.

Miriam Ruiz: In support of Patio Maravillas

Patio Maravillas is a self-managed government-independent social center in Madrid, placed in a squatted building that long ago belonged to school. The place currently belongs to a Real Estate company, Grupo 2 Reunidos. According to the law, the place has to be used for providing services to the community, which hasn t happened for 10 years. Nobody knows what plans they do have for the building, but there are suspicions that it might be related to property speculation. Nothing new on the horizon. The police are throwing them out of the building tomorrow morning, incidentally coinciding with the opening of the Foro Social Mundial (World Social Forum), for which Patio Maravillas was going to be one of the hosting buildings. Madrid isn t really known for supporting social movements in general, and has a conservative government, so feel free to think that the coincidence is not random. Patio Maravillas has been giving courses and workshops to the community since July 2007, and is very well considered and supported by different organizations. Supposedly whatever happens tomorrow will be without violence, but knowing how the Spanish Police behaves in this situations that is not very likely. The event will be streamed and probably recorded, and information will be twittered, so hopefully nothing serious will happen. I really hope the best for them. I d love to be able to be there with them, but as it is really not possible for me, I m giving them all my support from here. Good luck! Keep up the good work!

Martin-Éric Racine: Uninformed shoppers blaming Ubuntu: a brief TODO list for Canonical

My own perception of the debacle about the end-user who decided to cancel her college enrollment because she could not get Microsoft products to install on Ubuntu is three folds: Personally, I think that Canonical needs to hire an individual that understands the above three aspects and, most of all, how to remedy them, as its next OEM channel Manager, if they truly want to increase Ubuntu's market penetration.

Robert McQueen: My new font rendering technique is unstoppable

You know it s time to call it a day and write your talk tomorrow when I just upgraded Gtk+, Cairo and Pango to the versions in Debian experimental while I was upgrading some Telepathy packages, and got this the next time I loaded OO.o. Magic. But seriously, anyone got any ideas what s going on? Update: I switched my Debian mirror to .au and downloaded OpenOffice.org 3.0.1~rc2, and installed the Gtk+ and GNOME stuff too, and not only did the fonts came back, but it no longer looks like the 80s. Score! Thanks for the tips. Back to my talk

Kartik Mistry: Sorry!


* Magically, my old post appeared on various Planets after I added one more relevant tag in it. I am really Sorry for that!

20 January 2009

Bdale Garbee: Debian GLX Bugs Closed

Yesterday, I closed Debian bug #211765 regarding material under the GLX Public License violating the DFSG. That's two less open bugs tagged lenny-ignore!

Next.

Previous.