Search Results: "ag"

28 July 2007

Jose Carlos Garcia Sogo: Crowdsourcing and Harry Potter translation

It is not fresh news, but I haven't had time to comment about it before. Very soon after launch of Harry Potter and the Deathly Hallows, which was only made available worldwide in its original English version, you can read a free and non-academic version in Spanish. Spanish Hallows project, built up by a bunch of Harry Potter fans have made completely ridiculous efforts of J.K. Rowling and hers publishers (Bloomsbury Publishing) to try to delay versions in other languages. Perhaps this was not made with other intention than to avoid early publishing of copies sent to translators, which, as you know yet, happened anyway. Once again we see how is not only impossible, but stupid, to try to keep information in this new environment. I am pretty sure that most of books, movies and music publishers will disappear soon. But not because of piracy: they are not being able to adapt their corporate business model to the new environment. And I am sure that there are little start-ups out there working in this new model, and some of them will succeed. But nothing new here... it is how business world has worked for years now.

Adeodato Sim : Checking for uninstallability on other architectures

Sometimes one has to debug why a package is uninstallable, or some other apt problem, in other architectures than their own. This can be done by running apt with that other architecture in its configuration. I use this function to help me:
 fakeapt()  
 root='/var/tmp/fakeapt'
 dist="$1" 
 shift
 arch="$1" 
 shift
 apt-get \
 -o APT::Get::List-Cleanup="false" \
 -o Dir::Cache=$root \
 -o Dir::State=$root \
 -o Dir::State::status=$root/status.empty \
 -o Dir::Etc::SourceList=$root/sources.list.$dist \
 -o APT::Architecture=$arch \
 "$@" 
  
And then one can run it like this (it’s a bit long, but that’s how one goes to find out why a package is uninstallable, recursively adding each broken package in the run):
 % fakeapt sid hppa update
 % fakeapt sid hppa install -s kdebase
 The following packages have unmet dependencies:
 kdebase: Depends: kdebase-kio-plugins (>= 4:3.5.7-2) but it is not going to be installed
 % fakeapt sid hppa install -s kdebase-kio-plugins
 The following packages have unmet dependencies:
 kdebase-kio-plugins: Depends: libopenexr2c2a (>= 1.2.2) but it is not going to be installed
 % fakeapt sid hppa install -s kdebase-kio-plugins libopenexr2c2a
 The following packages have unmet dependencies:
 kdebase-kio-plugins: Depends: kdelibs4c2a (>= 4:3.5.7-1) but it is not going to be installed
 % fakeapt sid hppa install -s kdebase-kio-plugins libopenexr2c2a kdelibs4c2a
 The following packages have unmet dependencies:
 kdelibs4c2a: Depends: libopenexr2ldbl (>= 1.2.2) but it is not going to be installed
 % fakeapt sid hppa install -s kdebase-kio-plugins libopenexr2c2a kdelibs4c2a libopenexr2ldbl
 The following packages have unmet dependencies:
 libopenexr2ldbl: Conflicts: libopenexr2c2a but 1.2.2-4.3 is to be installed
A bit of initialization is needed:
 % mkdir -p /var/tmp/fakeapt/ archives,lists /partial
 % touch /var/tmp/fakeapt/status.empty
 % for d in testing sid; do
 echo deb http://ftp.XX.debian.org/debian $d main >/var/tmp/fakeapt/sources.list.$d
 done

Russell Coker: Outsourcing

It’s interesting to see an eWeek article about outsourcing to Canada, apparently the US immigration laws are restrictive enough that US companies (such as Microsoft) are establishing offices there. It really makes sense, Canada seems like a much nicer place to live. It’s also interesting to see an eWeek blog post about reductions in outsourcing to India that claims that Indian salaries have increased so much that there are few benefits in outsourcing the work. I have previously blogged about my approval of outsourcing as a form of charity to developing countries which received this response in Spanish. An English translation of a section of that post is “Conclusion, outsourcing hurts and the damage to many individuals is permanent. In countries in the third world like the one where I live, the damage affects the majority of the population (80% of the population is very poor). It’s ridiculous that less than 10% of the Mexican population earn 8 to 10 thousand pesos per month which only allows them to survive and save a little to buy a car or a house“. I agree that the inequality in Mexico is a bad thing, but I think that outsourcing is more of a cure than a cause for such inequality. The competition for employees who are capable of doing such work will increase salaries for workers and create a middle-class. Also the net access which is needed for outsourced work will drive some political changes. When discussing these issues with Indians I never hear any complaints about outsourcing!

Christian Perrier: Bhutan: another step towards democracy

Some people reading this blog know that I'm growing a special link with the isolated kingdom of Bhutan in the Himalayas. This link is born with the DzongkhaLinux lanuch back in 2006 and the connections that were established then with the people working over there on their national Linux distribution at the Department of Information Technology. And more particularly with their lead developer in this, Pema Geyleg. In parallel to this, I developed a good "vibration" with that country and I realy plan to come back there in the future and visit it more deeply, including all friends I made there in very few days. The country is currently not what we, in the so-called western world, would call democratic. This is a monarchy and not, yet, a constitutional one. However, the former king, Jigme Singye Wangchuck, (who has been ranked among the 100 people who have more influence in the world, last year, by Time magazine) decided long ago that he would bring the country to democracy by following a long but probably needed process. He first resigned last year, surprising everybody in the country, in the favor of his son, Jigme Khesar Namgyel Wangchuck, who is currently the youngest head of state in the world. Democratic parliament elections are programmed for 2008. And, yesterday, as another step in this democratic process, the Prime Minister resigned along with 6 other ministers, to "enter politics" in preparation of these national elections in February/March 2008. Again, it's very interesting to watch this process from far and see whether the country will succeed in achieving this transition (Pema told me several times that, indeed, the majority of people in Bhutan are not particularly eager waiting for this transition, given the very special relation they have with the king (the buddhist religion playing of course a great role there). And, well, let's anyway hope that the future government and parliament will keep the push they're giving to the development of free software, currently.

Simon Richter: Productivity

The key to productivity is avoiding other work. The weekend has just started, and I've successfully hooked up a JTAG probe to a Linux box and implemented half of debian/xcontrol stuff. xcontrol is a preprocessor for control files that accepts an extended syntax and compiles that into a policy compliant debian/control file, losing bits of information on the way (but whoever cares can just look into the xcontrol file). For now, I am planning to support the following extensions:
Build-Depends-Tool:
An additional build dependency line useful in cross compiling packages. The normal “Build-Depends” is reinterpreted as packages required for the target architecture, while this line specifies packages required on the host during the build.
Build-Depends[release]:
This overrides the build dependencies for a certain release, and comes in handy when backporting. Of course, this is orthogonal, so -Indep and -Tool fields exist too.
Optional: yes
This package is not normally built; if you need it, you have to invoke the “build-package” and “binary-package” targets.
per-package Build-Depends*:
This allows specifying the build dependencies for “Optional: yes” packages without adding them to the main list.
The syntax is still debateable at this point. The non-orthogonality of Build-Depends-Tool is intended, by the way. :-) The transformations done to make this policy compliant should be obvious: Build-Depends-Tool is folded into Build-Depends, the release-specific Build-Depends are omitted (or selected if xcontrol is told to target a specific release), Optional is stripped out and the per-package build dependencies for all non-Optional packages are accumulated. I don't know whether I'm going to do templates yet, this will probably wait until the second release. More on the JTAG adapter when I have the gdb stub working. Now I'm going to go back to what I should really be doing.

Mike Hommey: DM GR

Following the current trend on planet… or not. Ganneff, I could not agree more with you, especially since it matches what I first replied to aj’s proposal. That went unnoticed, though.

Joerg Jaspert: The DM GR

So, let’s join the postings about the currently running Debian maintainers GR. The short text of this post is I am against the proposal as it is right now and think it does more harm than good and so I did vote for Further Discussion. See below for a bit more about my reasoning, or just skip if you are already bored. :) The current proposal does look like a “yay, we have an idea thats not really thought through. And we do not want to get it into the currently existing procedures, that would involve more work and discussions. And anyway, everyone is ranting about the current procedures anyway, so lets take that bad mood against it to get this done”. (And yes, this is a bit exaggerated, so don’t take it personal, please). As you may have noticed I wrote that I am against the current proposal when it first was on vote. I was mostly on vacation back then and didnt want to read the whole thread, so I stayed mostly quiet. I am not against the DM concept itself. I am against it being seperate to the existing NM procedure. For me a proper solution has to be integrated with the existing procedures, not seperated. The main reasons why some support this proposal seem to be
  1. Slow NM process.
  2. Someone doesn’t want to go through NM
  3. Someone doesn’t want to be in the Debian community

Slow NM process I am part of this, and not a small one. And yes, I feel (very) bad about it, but already think about ways this can be changed, after I got the current backlog done. Anyway, for this DM thing my backlog isn’t the main reason that people feel NM is slow. It seems to be the general “I have to wait for an application manager and then answer to a lot of questions and between that wait and wait and wait”.
True. People have to wait at some points, and those waiting periods can be frustrating. We should do our best to eliminate those waiting places. The other point is that of the lot of questions. Yes, we have a really big set of questions in the templates, that cover a whole lot of the possibly areas a future Developer can work in. And most of those questions got added after a large set of existing Developers showed that they completly do not know something. That way the templates are constantly growing and still intend to give the future Developers the possibility to learn about things in Debian they might never have heard about. And there is the thought that, if you read about a topic and had to answer to it in the past, you will at least remember that there is something if you encounter it in the future. But - there is also the fact that an AM is NOT forced to use the templates for their process. AMs are, and have always been, free to do the process on their own. There are some questions every AM has to ask, but thats a minority. If you look at the templates you will spot the needed ones easily. Other than those every AM can freely do whatever he wants to do with his applicant (as long as the applicant agrees to do that stuff and its legal :) ). The AM only has to keep the following in mind: Both, FrontDesk and DAM, usually do not work together with the applicant. They might have heard the applicants name at some point, in some bugreport or some packages Maintainer: field. But they usually did not interact with them. Which means that the AM has to make sure that FD and DAM are able to build up their opinion of the applicant just by reading the mailbox of the AM->NM communication. Which usually means: read between 20 - 70 mails of a communication someone else had before you decide if someone should or should not enter Debian. (Leaving alone checking packages.qa, lintian, bug lists and a bit of google).
Someone doesn’t want to go through NM Erm. Well. Then use sponsors for your packages. Or is it because you think NM is too hard? NM isn’t that hard, everyone that can read and write english texts (even if the english is bad) and use google is able to pass NM. (For the bad english - if you fear joining NM because of that: Well. If I go and reread my own report from back when I joined - ugh. I hate my english. And I know native people still hate my english texts, its named en_GANNEFF for a reason. :) It is not necessary for your English to be perfect; you only have to be able to make yourself understood. If an AM doesn’t understand what you wrote they can simply ask for clarification). DM also doesn’t help for people that don’t want to pass NM. They have to pass the advocate, the ID check and the same minimum set of of questions NMs have (as written a bit above). So you already have a large part of NM for the future DMs.
Someone doesn’t want to be in the Debian community Then they shouldn’t be able to upload on their own. They can use sponsors. After all the only thing you must do as a DD is to read debian-devel-announce. And thats something a DM also must do, or you can’t seriously consider to package anything. And then DD only adds rights for you, like taking part in votes and so expressing your opinion and getting things changed in Debian that you may not like.
How to integrate a concept of DM then? First - by starting in the right area - getting it into the NM system by talking to all those involved. There is FrontDesk, DAM and also the NM-Committee, the latter should be the right point for a proposal and discussion. What I can imagine that would work and do something good is a system integrated into NM that gives future Developers upload privileges after they passed a few steps with their AM. That way they can upload early in the process, which can then be part of the T&S set, and the following steps in their NM process “just” slowly add more rights to the NM until its the set of rights every DD has. Seen from the current layout of the process it would be somewhere after the ID check and the first set of P&P, ie. at the time the AM sends the second P&P part. After that point the AM could recommend to those maintaining the DM list that the applicant should be added to it, together with a list of packages where the applicant is allowed to upload them. The maintainers of that DM list could be FrontDesk + DAM + maybe someone else, but thats something to discuss. And list of packages - while one could take the current limits the GR wants to set or simply a plain list, that can be amended during the time someone is a DM. Now, one can add a turnoff for people that do not want to pass through the rest of the process at this place. Im not sure its such a good idea, but thats something one can discuss. But if so it should be attached to some rules like - must read our debian-devel-announce list, is included in regular pings of activity similar to the wat ping.

27 July 2007

Russell Coker: Red Hat virt-install and Partitions

I have recently been using virt-install on CentOS 5 to install some virtual machines (I previously posted a summary of the experience). One problem I had is the inability to do an install of Fedora to /dev/hda - it insisted on partitioning the disk and installing it on a partition. I have filed Red Hat Bugzilla #249837 about this problem. # n=1
# while true ; do dd if=/dev/vg0/orig of=/dev/vg0/dest bs=512 skip=$n count=1000 ; echo $n ; file -sL /dev/vg0/dest ; n=$(($n+1)) ; done After doing a CentOS or Fedora install I then have to fix things so that my desired option (of using a single unpartitioned virtual disk) is used. To do this I first needed to determine how many sectors at the start of the filesystem were used for the partition table. I used the above shell commands to test skipping different numbers of sectors and using file -sL to determine whether the result was recognised as an Ext2/3 filesystem. Below is part of the output: 62
/dev/vg0/dest: data
1000+0 records in
1000+0 records out
512000 bytes (512 kB) copied, 0.018812 seconds, 27.2 MB/s
63
/dev/vg0/dest: Linux rev 1.0 ext3 filesystem data (large files)
1000+0 records in
1000+0 records out
512000 bytes (512 kB) copied, 0.115528 seconds, 4.4 MB/s
64
/dev/vg0/dest: data
1000+0 records in
1000+0 records out
512000 bytes (512 kB) copied, 0.018623 seconds, 27.5 MB/s As you can see 63 sectors are used for the partition table and other boot blocks at the start of the disk. So I used the below command to fix it:
dd if=/dev/vg0/orig of=/dev/vg0/dest bs=512 skip=63 The next problem after this was booting. The pygrub program that is used by the CentOS Xen installation to boot DomU’s only works with partitioned block devices. This however is quite easy to solve, I merely had to copy the kernel and initrd from the Xen image to the Dom0 filesystem and use the files for booting. Of course every time I upgrade the kernel I will need to copy the files, but that’s not such a great inconvenience. I usually end up running multiple DomU’s with the same distribution so I can copy the kernel and initrd once and use it for all instances.

Michael Prokop: Use root=UUID on NSLU2

As I wrote a few monce ago I’m owner of a NSLU2 device powered by Debian. Now I had to install another device (using di-nslu2-etch-4.0r0.bin - md5: db8e8ec3571aff8fb2132479f860f16b this time) and I wanted to change the setup from using /dev/sda2 to a UUID based one - to get a stable root device. Nothing really tricky (thanks to the existing documentation) but just as a reference (for myself and other users considering the switch as well) the relevant steps… First of all identify the root-device (/dev/sda2 in my case) and get its UUID:
# /lib/udev/vol_id -u /dev/sda2
a98ebb0f-84ae-4f7a-a070-b94ecee3f94a
Make sure initramfs-tools use the given UUID as ROOT-option:
# echo "ROOT=/dev/disk/by-uuid/a98ebb0f-84ae-4f7a-a070-b94ecee3f94a" > \
/etc/initramfs-tools/conf.d/root-device-hack
# update-initramfs -k all -u
Replace the /dev/sda2 line in your /etc/fstab with:
/dev/disk/by-uuid/a98ebb0f-84ae-4f7a-a070-b94ecee3f94a /               ext3    defaults,errors=remount-ro 0       1
Make a backup of the original mtdblock2 and install the one Martin Michlmayr thankfully provides:
# cat /dev/mtdblock* > mtdblock.backup
# cat /dev/mtdblock2 > mtdblock2.original
# wget http://www.cyrius.com/debian/nslu2/files/etch-modified-mtdblock2.bin
# md5sum etch-modified-mtdblock2.bin
e5154ceed8ad7de5bca83cc98fbb4d79  etch-modified-mtdblock2.bin
# cat etch-modified-mtdblock2.bin > /dev/mtdblock2
# apex-env printenv
... compare output with http://www.nslu2-linux.org/wiki/Debian/ChangeKernelCommandLine
Finally set the new kernel commandline:
apex-env setenv cmdline 'console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug rootdelay=10 root=UUID=a98ebb0f-84ae-4f7a-a070-b94ecee3f94a'
That’s it. Now after rebooting your system should use the UUID-approach instead of /dev/sd*. Check via:
# cat /proc/cmdline
console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug rootdelay=10 \
root=UUID=a98ebb0f-84ae-4f7a-a070-b94ecee3f94a
Ressources:

Michael Prokop: Linux on the Lenovo Thinkpad X61s

Lenovo X61s - picture Since about two days I’m proud owner of a Lenovo X61s notebook. It will become my main and new developer box for grml, featuring all that nifty stuff like 64bit support, hardware virtualization and so on… I managed to use all the important features with a very current version of grml. I’m using kernel 2.6.22-grml on a setup with LVM, cryptsetup-luks,… everything works fine so far (including Suspend-To-RAM - even in grml live-mode when booting from USB pen :-) - thanks for the excellent hibernate package, madduck!). As you won’t find useful and approriate information about Linux on the X61s yet (either pretty incomplete or wrong) I decided to put all relevant information on a webpage in the grml-wiki: Short version: the X61s rocks. I’ll provide information to thinkwiki as soon I checked out all the details…

Michael Prokop: Setting up your own jabber server: ejabberd

It was on my todo list since ages, finally I took some minutes to set up my own jabber server (reach me at mika@jabber.grml.org). I’m using ejabberd, a free and open source instant messaging server written in Erlang. Reference system: Debian etch (current stable), ejabberd version 1.1.2-6, installed via a simple:
# aptitude install ejabberd
Adjust the hostname in /etc/ejabberd/ejabberd.cfg (I suggest to use something like ‘jabber.$YOURDOMAIN’ so you can update jabber’s DNS SRV according on upgrades, downtimes, moves,…):
 hosts, ["jabber.yourdomain"] .
Register an account:
# /etc/init.d/ejabberd restart
# ejabberdctl register username jabber.yourdomain password
You might want to give your username admin permissions, so adjust /etc/ejabberd/ejabberd.cfg according:
 acl, admin,  user, "username" .
That’s it. If you want to disable registration of users just use (instead of the ‘allow’ line):
 access, register, [ deny, all ] .
Restart the server and make sure you have a running server:
# /etc/init.d/ejabberd restart
# ejabberdctl status
Now you should be able to point your browser to http://yourdomain:5280/admin/ and set up your new jabber account inside your jabber client.

Wouter Verhelst: Dear lazyweb,

When learning some code I didn't know before, my usual way to get familiar with it is to first find some documentation or a kind spirit to help me understand the big picture, and then to run the code in a debugger or to do something like '/bin/sh -x', or some such, so that I can understand how it actually flows. That works pretty well with most software. One of the things with which it does not work, however, is gcc's .md files. As far as I know, there are no debuggers for those files; and even though Simon helped me understand a few things about it at Debconf, I'm still not confident enough to just start editing stuff. Additionally, just randomly editing a 7k+ LOC file and expecting those edits to magically work is not something I consider very likely to succeed. So, dear lazyweb: how does one debug gcc's .md files?

John Goerzen: OSCon Friday

Fudge Update

Yesterday I blogged about the guy handing out fudge. He saw my post and explained why he was doing it. Today he was around handing out fudge, and I thanked him for his comment. He gave me two pieces of fudge for blogging about it.

Pineapple

At most of the breaks, they have this truly wonderful real (non-canned) pineapple. I think I have eaten more pineapple this week than any other week, ever. Very insidious, O'Reilly.

Conference materials

Slides of talks are available. Apparently keynotes are being posted on Youtube and Google Video, though they haven't provided a specific link AFAICT.

Philip Rosedale, Founder/CEO of Linden Lab

Second Life and the XPrize are two examples of escapism: you can escape to virtual earth, or escape the planet entirely.

In order for Second Life to grow, it has to become profoundly open. It has to be a standardized protocol. They are working on code to let people run their own servers. They are trying to make the server trusted and make it able to be open sourced as well. They see openness as the key way for it to grow.

If you are writing a web app that depends on the network effect -- such as Facebook -- you should open source everything right from the beginning. Not because it's best for humanity, but because you will win.

Jimmy Wales

He's trying to do open source search. Nice idea, could have been summarized in 45 seconds, I think.

Simon Wardli

Was going to talk about Zimki, which was going to open sourced, but they decided not to.

Funny and interesting talk, I sorta forgot to take notes while listening...

Nat Torkington

OSCon program chair.

Funny talk about Linux, an adolescent at 16 years old. Thinking about different languages and how they're doing. How the Linux community is organized: are we fighting battles, and do we need to?

James Larsson

This guy takes old hardware and makes insane devices out of it. 15,000 volts running over a coat hanger used as a "game controller", for instance.

In all, awesome keynotes today.

John Goerzen: OSCon Thursday Part 2: Linux on laptops

Matthew Garrett

A lot of background on the state of laptop support in Linux. It worked reasonably well in the 90s, but with the migration to ACPI, has become much more complicated and less reliable in general, especially with suspend/resume and video.

Emporer Linux and System 76 produce Linux supported laptops.

I wanted some more in-depth technical information and found Matthew later on at the Intel booth. Here's what I learned:

s2ram is little more than a wrapper around standard ACPI sleep that has options to do video mode save/restore

I asked him about all the many, many different userland laptop management tools. He recommends simple acpi-utils with the ondemand governor. laptop-mode-tools tries to do way too much, and there is little point to using a userland governor anymore.

I've been having a problem with my MacBook Pro (Core Duo) hanging on suspend about 10% of the time. I explained the symptoms and asked him how to go about debugging it. He suggested disabling console suspend and enabling PM debug in the kernel. I will give that a try and see what I get.

Julien Blache: pommed v1.8: Linux 2.6.22, MacBookPro3,1, new feature

This release of pommed adds a couple of new features: If you are running Linux 2.6.22 on an Intel machine, you need to upgrade to this release to get the ambient light sensors working again. Jan Larres contributed an icon for gpomme, included in this release. Thanks! I am not really pleased with the code for the nVidia backlight, as it pokes I/O ports directly. It works for now, but I’ll replace that code as soon as I’ll have something better, so if you run into something that could do it before I do, please let me know. Thanks go to Steffen Schulz for pointing me to this code (bl1.c from Nicolas Boichat, modified by Felipe Alfaro Solana). Have fun! Bug reports, ideas and patches at the usual place.

Gustavo Franco: Happy sysadmin day and AFD turns 20

Happy BOFH^W sysadmin day for you! For those who aren't sysadmins, don't ask stupid questions for him/her today. Come on, just give a gift and enjoy the reaction.

By the way, Guns N' Roses - Appetite for Destruction (AFD) turned 20, six days ago so real, raw, unique! Unlike autotuned crap all over the place that we hear today from non musicians... "But Appetite was also among the last classic rock records to be mastered with vinyl in mind, to be edited with a razor blade applied to two-inch tape, to be mixed by five people frantically pushing faders at a non-automated mixing board. "We used classic instruments and classic amps," says the album's producer and engineer, Mike Clink."

Thijs Kinkhorst: Debian Maintainers

I voted for further discussion rather than accepting the Debian Maintainers proposal. My opposition is that it's a new procedure while I think the existing structures should be able to handle the people that want to contribute to Debian. The proponents intend to solve the following problems.
NM takes too long
Agreed that it takes too long (useless waiting is a waste of time) but creating a new procedure does not fix it. Apparently there's a group of people that want to develop software for maintaining a keyring group-wise, and want to do the work actually maintaining such a keyring. Great. My suggestion would be to apply their technology and time to the existing DAM position so the work can be shared and we can reduce the waiting time.
Some people do not want to go through NM
NM is not as complicated as it is sometimes regarded, and a large part of it can consist of actually contributing to Debian rather than answering boring questions. I do not see it as a bad thing that uploading on your own requires some commitment.
There has been talk about people only interested in a small set of packages. There are already many specialised teams which those people would be welcome to join. I've also yet to see a significant number of people having trouble to find a sponsor. Sponsoring is a bit less convenient, sure, but not unbearable. Extra checking also has added value for Debian.
Some people do not want to associate themselves with Debian
Fine with me, but I don't think we need to facilitate an entire procedure for the less than a handful of people that chose to resign as DD but still want to upload. Sponsoring works for them.
I support sponsoring, and I think Rapha l Hertzog was right to introduce it. It works. With sponsoring on the one hand and being a DD on the other, we have two avenues of contribution that complement each other quite nicely.

Martin Zobel-Helas: chinese-big5 list moderator wanted

The chinese-big5 is moderated since quite some time, because of to much unfilterable spam. Now the last remaining listmoderator asks for help as won’t be able to do listmoderation in near future. If you are able to read/write chinese-big5 and want to do listmoderation, please contact listmaster@lists.debian.org and/or write to 434837@bugs.debian.org.

Raphaël Hertzog: Is forking NM good?

In a discussion with Bdale, he suggested that DM is seen as forking NM. And some people do not like forks. They are not opposed to DM in principle but do not want it outside of the current NM team. Obviously DM tries to respond to cases that NM is not prepared to handle. Furthermore, the DM discussion has been active for quite some time and the various members of the NM team (Frontdesk, DAM) have not participated much in the public discussion. Only when it comes to a vote do we hear some more (negative) opinions. I don’t see that as a sign of willingness to integrate DM or something similar in the current NM structure. So people who are requesting DM to be integrated in NM, please take it up with the frontdesk/DAM… and don’t oppose the principle just because of organizational matters. Internal organization always change and adapt themselves to the situation. Joey is right when he compares this to the introduction of the sponsorship process. I was one of the main actor in that process. I introduced the concept without the consent of the NM team (James Troup, Martin “Joey” Schulze) at that time. It was a fork, a new way to proceed and it became mainstream with the creation of the current NM process. It’s the natural way of doing things in a free software project. That said, I’m not opposed to improving our NM process. It really needs to be reworked in a “Membership Process” and be open to various kinds of contributors. That’s why I created a dedicated wiki page: http://wiki.debian.org/Projects/ReformedMembershipProcess Let’s see if we’re ready to really fix that! I hope to have comments from all the people who look to be so eager to fix the NM process. :-)

MJ Ray: SPI Elections

I'm standing in the SPI elections on a very clear platform including cooperative values and principles and reviewing SPI against the good practice standards (last done in June 2005) so please go vote for me if you're an SPI voting member. Voting closes Saturday. The last turnout I saw was a disappointing 15%.

Next.

Previous.