Search Results: "ag"

15 December 2008

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...

MJ Ray: British Residential ISP Censorship News

Last week I reported that 95% of British Residential ISPs Censor - but I think I m OK, so I d like to quickly update on what I ve seen happen since then:-

14 December 2008

Cyril Brulebois: Secretary? Epic FAIL

Debian has a secretary that: Epic FAIL. (I won t mention again the incredible decision of putting everything into a single vote, others have done so already. And that s of course the worst of all.) Update: Just for fun (or despair), I sent another ballot for the General Resolution: Project membership procedures vote. And guess what?
This is an acknowledgement for your vote [record msg00356.raw] for
the vote "Project membership procedures"
sent in on Mon, 15 Dec 2008 08:37:16 +0100, with the subject
"Re: Final call for votes: GR: Project membership procedures"
 
Your vote has been recorded as follows
 
I note that this is not your first vote.
The time now is Mon Dec 15 08:08:06 2008
Thanks for your vote.
I m lacking words, and running out of popcorn.

Andrew Pollock: [tech] Asterisk call notification

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, I set up caller ID announcement to my MythTV setup, so if we happened to be watching TV or a recording when a call came in, it briefly popped up on the TV. Fortunately, we're not huge square-eyes, and spend more time goofing off on our laptops, so I wanted a way to display notifications on our laptops when calls came in as well. I had this crazy design in my head of having a server process on my Asterisk box, and then clients on our laptops could connect to it, and be informed of new calls. Before I went on a coding frenzy, and did something with the Observer pattern and more socket programming than I really wanted to, I thought I'd check if this was solved problem. Turns out, it kind of is. I found the Notify application for Asterisk (which I've made a package for Debian Etch), which blats a UDP message to particular host as part of a dialplan. It's more intended to go in person-specific extensions, but as the majority of calls go into the main menu and never come out before hitting a person-specific extension, and I still wanted to know about them for my own perverse pleasure, I added multiple calls to the Notify application in the main menu dialplan. The site for the application also mentioned some third-party clients for Linux and MacOS, but I've been looking for an excuse to try and write something that used Growl, so I wrote my own Python application, initially on Linux, and then I essentially swapped out the pynotify code for the equivalent Growl code, and it worked just as well on Sarah's Mac. So it's not quite the solution that I had in mind, because it doesn't really scale, but for our two-user home setup, it's adequate. I might still try and write some middleware between a client for this application and an infinite number of observers, but there's no urgency. The dialplan for our main menu now looks something like this:
exten => s,1,Background(for)
exten => s,n,AGI(mythtv-cid.agi)
exten => s,n,Notify($ CALLERID(num) $ CALLERID(name) $ EXTEN /icarus)
exten => s,n,Notify($ CALLERID(num) $ CALLERID(name) $ EXTEN /iapyx)
exten => s,n,Set(TIMEOUT(digit)=5)      ; Set Digit Timeout to 5 seconds
exten => s,n,Set(TIMEOUT(response)=10)  ; Set Response Timeout to 10 seconds
exten => s,n,Background(names/sarah)
exten => s,n,Background(press-1)
exten => s,n,Background(for)
exten => s,n,Background(names/andrew)
exten => s,n,Background(press-2)
exten => s,n,WaitExten
A call comes in, hits the menu, and the caller ID info is displayed on MythTV (if something's being watched) and our two laptops (if they're awake). Unfortunately my Git-fu is atrocious, so I can't figure out how to link to a web-browseable repository that contains the source for my client, but if I figure that out, I'll update this with a link later. Update I managed to summon enough Git-fu to put the repository online. It's available at http://git.andrew.net.au/?p=asterisk-notify-client.git;a=summary Now I just have to use it properly.

Biella Coleman: Thinking Responsibily about the Drugs among Us

Next semester I am teaching a new undergraduate course tentatively titled Technology, Society, and Media: The Body under Transition, in Movement, and under (Massive) Transformation(s). As designed, the course should address technology and media in fairly broad stokes (which I do) but I narrow and control what is a truly unwieldy subject by framing the issues/readings in relation to the human body. Generally speaking, we will interrogate the ways in which technology engenders or erases bodily/human possibilities/capacities and especially the ethical and political ramifications that precipitate from the use/abuse of technology. We traverse a wide range of topics from the telegraph (and how it was used to speak with the dead) to the role of human enhancement technologies of today, to questions of surveillance and privacy, among many other topics. I am pretty far along with the syllabus and pretty happy with it. So far I think I have struck a nice balance between fun/light/accessible readings and some which are bit more theoretically dense. I am still looking for one or two pieces, perhaps one on tattoos and body modification and another about karaoke. If anyone knows any great articles on these topics, do pass along the information. I am probably most excited about the cluster of issues that address eugenics (and most students know next to nothing about America s central role in unleashing the Eugenics movement), disability rights activism, human enhancement technologies, and transhumanism. Considering human enhancement in light of previous efforts to enhance our population brings into relief the similar and distinct ethical issues that haunt this field. One of the most hot button issues of today concern the use of human enhancing drugs. The prestigious journal Nature has just published an editorial on the topic of cognitive enhancement drugs,Towards responsible use of cognitive-enhancing drugs by the healthy, which is a fairly interesting read and covers some of the main controversies. For me, however, the interesting issue is not only whether human enhancement is right or wrong though this is certainly important but what our embrace of these drugs tell us about the conditions under which our bodies live and labor. That is, I think we are actually missing out on posing some other important questions simply by framing this int terms of human enhancement. I suspect, and this is where ethnography would really help out, that many people turning to enhancement drugs may not be medically sick, in the technical sense but I don t think they are healthy either. Many who turn to these drugs feel pretty worn, pretty exhausted, pretty frazzled (the perfect word, I think, is agotado, Spanish for exhausted) and use these drugs as crutches, as band-aids, as an elixir to help out one preserver in tough work circumstances. I am sure there are folks who take these drugs feel fine and are just trying to push their limits and capacities but I troll many many many patient support sites and it also seems to me that many people live under a state of low-grade chronic state of unwellness. Given the pace of society, given what and how we eat, given the extraordinary rates of depression in our society ,given the fact that babies are born with 200 + chemicals in their bodies (what a way to start out life) I am skeptical that enhancement really captures what is going on with these drugs. I have not yet come up with the right term, but I am trying to come up with a phrase that would reflect the ways in which these drugs are not used as therapies for a discrete condition (Type 1 diabetes) but how they are a collective response to a state of low grade chronic unwellness that seems to mark the lives of a whole lot of people. This, I think, would be one responsible approach to human enhancement technologies that would contextualize their use within a much broader frame, one that is attuned to how bodies have been made, remade, and limited under actual material conditions of labor and life in the 21st century.

Martín Ferrari: On voting

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: So, I second Noodles' proposal, to make this sillyness go away for good. Meanwhile, I have to decide if voting 2..21 or not voting at all. Tags: Planet Debian, Debian, Pol tica

Joerg Jaspert: Removals RSS feeds

My pretty old removals rss feed is now also moved to the new /rss/ location directly within FtpMaster hands. The old location has a permanent redirect, but please update your feedreader to the new one, which is http://ftp-master.debian.org/rss/removals.rss

Jaldhar Vyas: Vote

- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
[ 5 ] Choice 1: Reaffirm mango as the only acceptable flavour for lassi [3:1]
[ 7 ] Choice 2: Allow gulab jamun but only if you clear your plate what do you think I'm made of money or what?
[ 6 ] Choice 3: Allow gulab jamun but give what you can't eat to your sister I'm never bringing you here again
[ 3 ] Choice 4: Empower the release team to order extra naan
[ 4 ] Choice 5: Assume the green bits are really spicy
[ 2 ] Choice 6: Exclude nutritional info -- trust me you don't want to know
[ 1 ] Choice 7: Further Discussion
- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-

David Welton: langpop update

One of the things I have noticed running http://www.langpop.com is that, pulling data from different sources, the odds are surprisingly hight that at any given point in time, one of the sources will be out of wack, often in a subtle way that's hard to see in the results. For instance, in the December 2nd run, the Amazon results were a bit wonky, and Delicious has been gradually falling out of the Yahoo search results (weird, that). I decided to go with screen scraping for Delicious, even though, frustratingly, Delicious can't tell the difference between C, C++ and C#, so while we wait and hope that that gets fixed, those languages are all going to show nearly identical results. I have updated the site.

David Welton: langpop update

One of the things I have noticed running http://www.langpop.com is that, pulling data from different sources, the odds are surprisingly hight that at any given point in time, one of the sources will be out of wack, often in a subtle way that's hard to see in the results. For instance, in the December 2nd run, the Amazon results were a bit wonky, and Delicious has been gradually falling out of the Yahoo search results (weird, that). I decided to go with screen scraping for Delicious, even though, frustratingly, Delicious can't tell the difference between C, C++ and C#, so while we wait and hope that that gets fixed, those languages are all going to show nearly identical results. I have updated the site.

Cyril Brulebois: First times

First time So far, so good. But after having voted in reply to a possible abuse of position, now we have a vote with another abuse of position, as pointed several times on debian-vote@. Too bad we haven t seen any reply from the DPL. Yet? In the meantime, I was pointed (thanks!) to a marvellous secretary sucking page, best viewed with a CSS3-enabled browser. Screenshot from midori follows (note that it could be even worse with konqi from experimental, at least so am I told): Secretary (page!) sucks Oh, and another first time but not Debian-related:

Wouter Verhelst: -lgnodbify-gtk

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:
my @customers = Vpbs::Db::Customer->get_all();
my $model = GNoDbify::ListStore->new_from_array(@customers);
my $view = Gtk2::TreeView->new_with_model($model);
my $renderer = Gtk2::CellRendererText->new();
my $column = Gtk2::TreeViewColumn->new_with_attributes("Name", $renderer, "text", $model->get_column("name"));
$view->append_column($column);
And there you have it: a treeview showing all the names of all the customers in the database. On the classical approach, one would have to use DBI or some such to fetch data from the database, create a GtkListStore or something similar, and then append the data one row at a time to that. Of course that still happens here, in a manner of speaking, but it all happens behind the scenes. It also means that in an application which wants to show a load of data, I don't have to do the same thing all the time. The magic happens in the second line, and in the second-to-last line. GNoDbify::ListStore->new_from_array is pretty much self-explanatory, really. It takes an array of GNoDbify objects, and returns a GNoDbify::ListStore. The second-to-last line shows how to add a column to a GtkTreeView. With GtkListStore and GtkTreeStore you basically define yourself what column gets what number; however, with GNoDbify, that isn't as easy (it depends on the implementation of the GNoDbify subclass), so the ->get_column returns the number of a column as represented by the model, and wants the name of the field that you want the column of. Everything else is really the same. It won't stop here, though. The original plan for GNoDbify was that it could detect changes in the database, and update the tree model accordingly. Most of that has already been implemented in GNoDbify (though not yet in the ListStore thing), but just needs some debugging. The fun thing is, the above six lines of code would not have to change at all for that. Of course all this juicyness comes at a price. In order to generalize this much, I had to do a lot of extra stuff; so there's some performance loss. Especially in perl; most of GNoDbify is written in C, and converting perl arrays to and from C arrays is a process that can only be done by looping over the perl array (or the C array) and creating the other side of the equation. Obviously, that's a costly approach, performance-wise; an obvious optimization of the above example could be to have a subroutine that returns Customer objects already in a GtkTreeView in one API call. We'll see.

Christian Perrier: Clarification about my own vote

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.

Daniel Burrows: On voting to release Lenny

Regarding the ballot currently before the Developers, Christian Perrier writes:
Moreover, the proposal is worded and was pushed in a way that all (but one) options that would allow us to release lenny will need a 3:1 majority, which is obviously very hard to achieve (and as, there are several such proposals, the vote will be spread out among all of them). So, those folks who make the release of lenny their priority are now facing an interesting tactical choice: how the ..... should we vote for this to happen? I personnally did choose to vote this way: 5462371.
I agree with Christian's goals, but in my opinion, the ballot he has cast actually makes less likely that the winning option will allow us to release lenny. In Debian, we run a two-round election using a single ballot. In the first round, any options that need a 3:1 majority must defeat the default option by a 3:1 majority. Options which fail this test are eliminated and dropped from further consideration. In the second round, a winner is chosen from the remaining options using a Condorcet method as usual. The upshot of this is that the votes for the 3:1 majority cannot be spread out, unless people habitually place only one of the 3:1 options over Further Discussion. Furthermore, voting everything below Further Discussion benefits the options that don't require a 3:1 majority over the ones that do. For a real example, let's say that we have a ballot like this:
[ ] Choice 1: Omelette [3:1]
[ ] Choice 2: Quiche [3:1]
[ ] Choice 3: Toast
[ ] Choice 4: Further Discussion
Suppose that we don't like the ballot at all, but we want an egg-based breakfast. What happens if we vote like this?
[2] Choice 1: Omelette [3:1]
[3] Choice 2: Quiche [3:1]
[4] Choice 3: Toast
[1] Choice 4: Further Discussion
This ballot can be read as: I don't think that omelettes or quiche should pass the 3:1 majority requirement. But if they do, I prefer them to toast. Unless 75% of the remaining voters vote omelette and quiche above toast, those two options will be thrown away, and the vote will be determined by whether half the voters placed toast over further discussion. If you want to make sure that toast doesn't win, you have to vote (insincerely) like this:
[1] Choice 1: Omelette [3:1]
[1] Choice 2: Quiche [3:1]
[3] Choice 3: Toast
[2] Choice 4: Further Discussion
Sadly, there is no way to vote against the vote without effectively also voting for toast!
I wonder if it was a mistake to combine the supermajority vote and the Condorcet vote on a single ballot. Maybe it would be better to write both ballots out explicitly:
Some options on this ballot must be approved by a 3:1
supermajority of the electorate.  Please enter 'Y' next to the
options that you approve of and 'N' next to those you disapprove
of.  Ballot options on which 75% of voters vote 'Y' will proceed
to the next round (below).
[ ] Choice 1: Omelette [3:1]
[ ] Choice 2: Quiche [3:1]
Rank the ballot options below:
[ ] Choice 1: Omelette [3:1]
[ ] Choice 2: Quiche [3:1]
[ ] Choice 3: Toast
[ ] Choice 4: Further Discussion
That would allow people who want to vote against the vote without privileging any of the options over the others to do so: vote Y to all 3:1 options, then vote 2221 on the rest. On the other hand, I suspect people would be confused in different ways by a voting system that was this complicated, voting Y in places where they should write a number and writing numbers where they should write Y or N. I guess all this mess is why we still use First Past the Post for votes in the real world...

Kurt Roeckx: Debian vote about firmware and the Lenny release

Today the voting period starts for this general resolution about firmware and the Lenny release. As many have pointed about before this is very complex vote with many orthogonal issues. The issues and some of the options: And then we're going to decide all of that in 1 single vote. I interpret the options we have as: Choice 1: Choice 2: Choice 3: Choice 4: Choice 5: Choice 6: Choice 7: So in my opinion, options 2, 3, 4, 5 and 6 all decide on 1 of the 4 questions, and only 2 of them about the same question. I also don't see any bugs filed against the linux-2.6 package about any issues the kernel might have with firmware, so I have to wonder why we're voting about this. My current vote is "2222221". I'm not sure it's the best options, but I currently don't see a better one.

Jose Carlos Garcia Sogo: NAS adapter

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 Xataka a little device: Addonics NAS Adapter. This is just what I wanted: NAS adapter, little size, can power 2.5 inch. HDD directly, and USB print server. Files are shared by Samba or FTP client, and can act also as DHCP server. As a bonus it has a little bittorrent client which can track 4 torrents at a time, and download them to attached USB device. The only thing I would like to know if is using an USB hub both a printer and a HDD can be attached at the same time. If that can be done, then for only $55 we have a winner. The only last wish that it uses Linux in their core (probably).

Neil Williams: A Debian morning

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.
All I'm saying about the first GR (the "anti-ganeff" vote) is 2212. That was the most ridiculous GR I've come across so far, until vote3 which is just politics gone insane. My own opinion? 7235146 which disagrees quite a lot with bubulle even though I have the same aims as bubulle - that alone indicates the nature of the vote. The options are illogical, the vote is pointless, the subject matter is moot, the initial proposal doesn't have any understanding or relation to the real world and the amendments have been unnecessarily divided in such a way to make it all but impossible to be logical in the vote priorities. The abuse of votes by a vocal minority undermines the process itself. All in all, we desperately need an option that basically says stop being pathetic and get something useful done in all future GR's - as well as making it harder to make a GR in the first place. Over use of referenda is as poisonous to democracy as under use - just ask Ireland.
After all that political spin and muck spreading, I had to just do something useful as a partial compensation. So, after a ping from the MIT BSP I've fixed 507316.
I've also made the tslib experimental upload that has been quietly developing on my own system for a few days.
Right, now I'm getting back to adding more packages to Emdebian Grip - so far, we have enough packages for a basic XFCE/Gtk system with an email client, a blog client, a few GPE games and Thunar as file manager. Now need to add iceweasel and dependencies. Once that is done, I'll be switching my Acer Aspire1 from Debian Lenny to Emdebian Grip unstable and creating a testing repository for Grip. Once I've got some figures from that switch, I'll post some more details to debian-embedded@lists.debian.org.
Sigh. Emdebian Grip was meant to go alongside Debian Squeeze - it looks now as if Emdebian Grip will be released before Debian Lenny - it's even likely to use the Lenny installer and debian-live support. I hope the pedants are happy because I'm not.

Michal Čihař: Lenny Release General Resolution

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...

Bastian Venthur: Lenny Release General Resolution

I agree, this vote is one of the worst formulated I can remember. I think votes should be as easy as possible to understand, so that the voter is absolutely clear about what he s going to vote. The current vote is the perfect example how not to design such a vote. Reading and understanding the ballot is very exhausting, the wording sounds polemic and given the options, it somehow feels like a trap. Example: The first option is Reaffirm the social contract . Sounds nice, of course we want that, but in the footnotes it says
[ ] we will delay the release of Lenny until such point that the work to free the operating system is complete (to the best of our knowledge as of 1 November 2008).
So you re actually voting on delaying the release of Lenny until some technical details are cleared. This is really crap, why not name the option Delay Lenny until foo in the first place? I guess to motivate people a bit more to rank this option above all others. I m very disappointed. Next vote, fever options and clearer wording please.

Joerg Jaspert: Planet Debian again

So after my first post I got some comments, and now we also have an atom feed of Planet available, for those that dislike RSS. And now we also feature those link href= /something rel= alternate links, so that your browser can directly let you subscribe to a feed. Or whatever they may also be used for. Anything else thats so easy to add which we not have yet? :)

Next.

Previous.