Ingo Juergensmann: Voting
I've not followed the current voting closely, because I was moving from Berlin back to Rostock last weekeend. But I find
it strange that the issue with firmwares is still not solved since Etch.
That's more than two years ago and within these two years nobody cared to solve the firmware blob issue. This leads me to the conclusion: nobody cares about unfree firmware in Debian except there is a release upcoming and then some people start shouting "UNFREE FIRMWARES!!! That's against the social contract!"
So, when it's against the SC, why hasn't this issues been resolved in the last two years? Apparently noone cared enough and therefore it's not that important to stop the current release, IMHO.
My point of view is: firmware blobs are part of the hardware and not some sort software that needs to be free. Of course it's nice if firmware blobs are actually free and open. But the alternative would be hardware with real ROMs that either can't be updated (because they're soldered onto the board) or, if they're socketed, extra costs because you'll need to buy ROM updates and exchange your little ROM chip by a newer version.
I prefer to have firmware blobs released with lenny soon, but maybe I'm missing some points...
That's more than two years ago and within these two years nobody cared to solve the firmware blob issue. This leads me to the conclusion: nobody cares about unfree firmware in Debian except there is a release upcoming and then some people start shouting "UNFREE FIRMWARES!!! That's against the social contract!"
So, when it's against the SC, why hasn't this issues been resolved in the last two years? Apparently noone cared enough and therefore it's not that important to stop the current release, IMHO.
My point of view is: firmware blobs are part of the hardware and not some sort software that needs to be free. Of course it's nice if firmware blobs are actually free and open. But the alternative would be hardware with real ROMs that either can't be updated (because they're soldered onto the board) or, if they're socketed, extra costs because you'll need to buy ROM updates and exchange your little ROM chip by a newer version.
I prefer to have firmware blobs released with lenny soon, but maybe I'm missing some points...
Last week I reported that
My home Asterisk configuration has been pretty static for a while. It works
well, and so I haven't had a need to mess around with it.
There's a couple of outstanding features I've wanted to implement for a
while though, and I've now got one of them out of the way.
All calls that come in from the local PSTN line, the Vonage ATA, and the SIP
connection to Engin, hit a menu, where the caller selects whether they want
to speak to Sarah or myself. The sole purpose of this is to determine what
to do with the call if no one answers (which voicemail box or cell phone to
send the call to). A convenient side-effect of this is that it defeats most
telemarketers.
Ages ago,
This is really ironic, I've been waiting for a long time to have the right
to vote in Debian. Now I have it, but I'm not sure if I want to exercise
it.
I don't think I need to explain much, many already did that before on
planet. It basically boils down to:

A while back, I wrote about this GObject-based Object/Relational
mapper that I wrote, which is called 'GNoDbify'. It isn't complete yet,
but parts of the library work; I use it for a project that I'm supposed
to commercially support. For those who don't know what that is: an O/R
mapper builds objects out of database tuples; so I can run a 'lookup'
function on the object class and get one (or more) objects representing
data from the database, then perform some modifications on that object,
and store it back in the database; my O/R mapper does all the SQL
magic.
Last week, I've been working on another object that takes an array of
GNoDbify objects, and presents them using the GtkTreeModel interface,
for easy viewing in a GtkTreeView:
Dato points me that the way I mentioned my vote is confusing and he's right.
By writing that I voted 5462371, I wanted to say that I ranked option 5 as first, option 4 as second, etc.
However, one could understand that I ranked option 1 as 5th, option 2 as 4th, etc.
...which is indeed the most common way we talk about our votes....
So, let's make it clearer. I voted: 7452136.
So the first option (freeness bigotry) is ranked below Further discussion.
I'll re-consider it in terms of strategy but I consider it honest: this is how I rank the various options altogether. I did not try to mke this vote "strategical" but I agree that this needs to be deeply thought. The issue is really important and can even be seen as a trap, yes.
Regarding the ballot currently before the Developers, Christian
Perrier
I have been always desiring to have a NAS adapter and printer server so I can easily share and use both my USB printer and a USB hard disk from every corner in the house. I was doing that when I had a home server, but when it died I losed that functionality. Once of the main reasons to buy a new one was to have this option again, but today I have discovered in
A variety of Debian tasks all lined up in the top priority - get it done now or not at all - work queue this morning. Two GR's, one RC bug fix and one long overdue experimental upload.
Hmm, again another general resolution. Yes, but this one seems to be
really tricky. During discussion, several almost unrelated options have
been merged into single vote, what really does not make it easy to
understand and choose preferred option. Yes they are related in the way
that they will affect time of Lenny release, but I think splitting it
into several votes would make more sense.
On the other side, Lenny release is getting delayed more and more and
boycotting this vote also does not seem as a good choice to me. Such
choice will practically delay Lenny release after another decision will
be made or all firmware issues will be solved. And neither of these
choices seems to be possible to happen in a timely manner...
I agree, this