Search Results: "ron"

24 January 2006

Adam Rosi-Kessel: Massachusetts Healthcare and Dunkin Donuts

Those of you outside of Massachusetts (or the United States) may not have heard about our recent healthcare insurance debates. Left Center Left has some interesting entries on the lack of local political analysis and confusion about why the business community opposes the various legislative solutions where those solutions appear to be basically in their self interest. The proposed solutions are converging on a tax on employers who do not pay for their employees’ healthcare. That tax would help pay for statewide coverage of all or most citizens, and hopefully encourage employers to provide insurance for their employees to avoid the tax. (There is strong dissent, for example from the Massachusetts Taxpayers Foundation, as to whether the tax would actually raise any money). Critics argue that the tax will discourage employers from coming to Massachusetts. The two large employers singled out most frequently in the State for not providing healthcare benefits to their large work force are Wal-Mart and Dunkin Donuts. Is it even remotely possible that Wal-Mart and Dunkin Donuts would actually shut down (or stop opening up) stores if they have to insure their employees or pay an additional tax? Obviously increased labor costs (whether through tax or insurance) could cut into profitability—but is there any evidence at all that it would represent a “tipping point” that would cause these employers to shut down? (Note that despite Massachusetts’ reputation as “Taxachusetts,” a study last year that I can’t locate right now pointed out that the overall tax burden on Massachusetts citizens was about in the middle, compared to other states). Even if the health insurance mandate depresses wages, it’s worth noting that it is cheaper for the employer to buy group health insurance for its employees than it is for each of those employees to buy it individually—both because of the bulk buying power and for tax reasons. It is thus not a “zero sum game” where employees wages should be depressed by the exact amount of the increased health care costs. Finally, wouldn’t this measure actually encourage employers to come to Massachusetts who already insure their employees, since presumably the statewide insurance mandate should decrease costs to those already providing insurance as they will no longer be effectively subsidizing the uninsured who work for competitors and other employers? And aren’t those the kinds of employers we would like to attract, rather than more Dunkin Donuts and Wal-Marts? (In fact, wouldn’t fewer Dunkin Donuts lead to less heart disease, thus also cutting down our health care costs overall…?)

MJ Ray: World Economic Forum TV coverage

In 2006 as in past years, satellite TV channel SFinfo at 13e will be broadcasting some sessions of the World Economic Forum, with both German and Original (often English) soundtracks (I think Left/Right split). If you have a satellite set, you can see what the barons of big business are saying: sometimes depressingly hilariously irresponsible.

23 January 2006

Edd Dumbill: Lovely DITA, DocBook fades?

Sorry. Couldn't resist. Following on from my previous look at XTech proposals, I wanted to comment on one of the hot topics contributed to the Applications track. While this track will push all the buttons (we've got Rails, RSS, web services, content management and more) one of the really striking things was the number of proposals on the topic of DITA. If you're not a regular in the tech docs world, then DITA is probably at best just another acronym you've seen whizzing by. DITA stands for the Darwin Information Typing Architecture, and it's a new document format making waves in the world of technical documentation. From a casual documenter's point of view, the obvious question is probably "what does this mean for DocBook?" Does the mass of enthusiasm mean DocBook's on its way out? In short, no. DocBook and DITA compared  DITA and DocBook are actually rather different beasts. DocBook is a sound DTD for writing technical books and articles, with the structure that such forms imply. DITA is focused on creating modular technical documents, with the intent for easy reuse across varied delivery methods. It's intended for topic-oriented documentation, which may be chopped about and rearranged within a variety of contexts and for a variety of display devices. DITA is a DTD and a set of rules for writing online contextual documentation such as software help files. There's a lot more to it than I'll write here, but here a few more differences between DocBook and DITA: There's a real need for something like DITA, which addresses concerns that didn't really exist in the same way when DocBook first emerged at O'Reilly in the early 1990s. DITA and open source projects I'm looking forward to learning more about DITA, but one thing that immediately strikes me about it is its relevance to some of the documentation problems faced by open source projects. DocBook has never quite clicked as a documentation format for some collaboratively maintained projects, probably because the inevitable book-like nature of the result necessitates sole or restricted authorship, and heavy editing. Instead one of the increasingly popular ways for providing documentation has been the wiki. You guessed it, a topic-based architecture. What wikis seem to lack, however, is any way of providing a thought-out progression through the content. In essence, the information architecture side of things. Had I been able to attend every session from XTech last year, I'd have heard Paul Prescod talk about what DITA and wikis have in common.
There may be a downside, however. DITA looks impressively engineered, but it may be too industrial-strength for many. My initial investigations suggests that while there's emergent commercial tool support, there's not much going on in the open source field (although there is the DITA Open Toolkit, which looks to have been produced in close association with OASIS technical committee now in charge of DITA.)
As DocBook guru Norm Walsh observes, DocBook can play in this space too. With additions such as those Norm proposes, DocBook could play host to DITA's major features. (Norm writes "With a couple of hours of hacking, I've implemented on top of DocBook the four key features of DITA that I could identify.") Though these possibilities are intriguing, I think that, for open source projects, things need to get simpler rather than harder. More reading:

Joerg Wendland: back on planet debian

Since I switched to pyblosxom Planet Debian had the wrong URL for my feed. That should be corrected by now. In case you don't see this very post, it isn't.

MJ Ray: Software Patents: he'll be back

"While the Terminator needed 7 years for a first reappearance, and another 12 for its second, the Terminator of European Economy (Mr Charlie McCreevy) only needed months to bring software patents back on the agenda."

You can't keep a bad idea down. Nice to see him get it up again while people are still hot. Maybe he's the EC's Mr Viagra?
"the first Terminator went down after a long and desperate struggle involving all sorts of fireworks"
Are we still dealing with the first one, damaged but not dead yet?
"even though the second Terminator was so much quicker, stronger and more well-prepared, we all remember the end of the second movie."
Where's a truck of liquid nitro and a steelworks when you need one? (quotes from Georg Greve's Freedom Bits).

Holger Levsen: splashy backport for sarge

Since I prefer quiet and relaxing work environments, I don't like to see the kernel boot messages if I'm not debugging something. So saturday I've installed splashy on my laptop.

As I couldn't find backported packages for sarge anywhere, not even on the skolelinux wiki (which explains the usage of splashy and is targeted at sarge (fixed now)) I've built them myself and provide them on my webpage to save other people from rebuilding them again and again.

I've asked to include them on backports.org but it's (not yet written) policy only accepts packages from unstable not from experimental. So no luck for now.

For other people's reference I use the following as kernel params for splashy on a R51 notebook: video=radeonfb:1024x768-32@100 vga=795

22 January 2006

Matthew Palmer: LCA 2006 -- The Early Years

So, I've arrived at LCA (linux.conf.au) 2006, in Dunedin, New Zealand. You're going to be getting a lot of these blog posts over the next few days, from me and other people, but it's only a week-long conference, so weather the storm. Plane trip over was... well, it was a plane trip. I can be thankful that I didn't lose my luggage (as one bloke has already had done to him). Beyond that, all aircraft interiors are identical, so no need to discuss that. At the stopover in Christchurch, we all headed for the bar (as geeks tend to do). I handed over a brightly coloured note in the local currency in exchange for my beer, and I get my change. What is part of my change? An Australian 10c piece. <sigh> Mad props to the conference organisers so far -- one of the organisers was at the gate (the only gate) at Dunedin airport to pick up speakers, but he gladly took us ruffian attendees into town, saving us all a few bucks in shuttle bus fairs. It was a nice guided tour in, as well, showing us all of the useful sights (like the pubs, 24 hour minimart, and eateries). He also dropped us off at the registration desk, so I got my conference schwag already (see my separate review of the schwag). Dinner involved walking into the octagon (a loop street with, unsurprisingly, 8 sides) and finding a place that serves you raw steak and a hot rock. It's like a portable BBQ construction kit. Amazingly tasty. We're going back tomorrow night for more of the same, as it's so tasty and fun -- you are legitimately allowed, even encouraged to play with your food. I also got a "barmate" (don't mispronounce that in front of your significant other) -- a yard-high glass cylinder with a tap at the bottom, filled with your choice of beer. Much merriment ensued amongst the assembled geeks, as we all plied ourselves with Speight's Gold Ale. I think it's about 8-10 pints worth of beer all up. Value. No Internet access yet, as they're still working out the kinks with the special conference network. I hope it's all up and running by tomorrow morning -- my mail queue is starting to seriously bulge with all of this outgoing mail.

Edd Dumbill: Firebug: neutralizes nasty niffs

Sometimes, coding for the web is like having a co-worker with a body odor problem. Everyone's far too polite to say anything, so you all put up with it and nobody tells the poor smelly soul. Meanwhile, they sense something's wrong but don't know what. Web browsers are so insanely great at making sense of tag soup, that if you code only for the end-result--a reasonable strategy, adopted by most when starting out--you can get into all sorts of tangles. Misery ensues: you're stuck with days of fiddling in the dark. You know something's up, but it's hard to see what's going wrong. In that sense, browsers are lousy at one half of Postel's law. They get the "liberal in what you accept" bit right, but they don't help the developer one bit in implementing "be conservative in what you do." Using three or four different validators for HTML, CSS, etc. often helps a lot, but the state of the browser as an integrated development platform leaves something to be desired. Firebug is a Firefox extension that goes a long way to providing integrated web application debugging. It is a full-featured error console that shows your errors in Javascript, CSS (a godsend!) and XML. Not only that, but it does full logging for XMLHttpRequest calls, so it's a powerful tool for debugging AJAX applications as well. Firebug also manages to bundle in a DOM inspector, and a command line for evaluating Javascript. With these features, Firebug should let me throw out about four separate extensions I already had installed that do a similar thing. The final star turn in Firebug's act is a Javascript call to log information to its console, the equivalent of the all important debugging printf() call in C. I hope this means this will make it easier to deploy things such as unit test frameworks for AJAX applications. Firebug in action on the BBC home page Although its author Joe Hewitt cautions us to remember that Firebug is still an alpha release, I'd still recommend rushing to install it. If you're developing anything for the web browser this year, it's the most important tool you'll find. While it won't rid you of the problems of cross-browser compatibility, Firebug will speed you in uncovering the smelly bits of your web application.

Eric Dorland: I *knew* this quiz was out to get me...

Your Social Dysfunction:
Paranoid


You show pervasive and unwarranted suspiciousness, and mistrust of others. You are overly sensitive and prone to jealousy.

Take this quiz at QuizGalaxy.com

Please note that we aren't, nor do we claim to be, psychologists. This quiz is for fun and entertainment only. Try not to freak out about your results.

Eric Dorland: Spins a web, any size...

Nice, he's my favorite: Your results:
You are Spider-Man
Spider-Man
85%
Hulk
75%
Green Lantern
70%
The Flash
65%
Superman
60%
Robin
55%
Iron Man
45%
Catwoman
45%
Batman
45%
Supergirl
43%
Wonder Woman
28%
You are intelligent, witty,
a bit geeky and have great
power and responsibility.
Click here to take the "Which Superhero are you?" quiz...

Miguel Gea: Experiences with oracle in Debian

I few months ago I decided to add support to Oracle database to dbconfig-common frontend. At that moment, I began learning how to install it and how to manage it.

My work:
1.- Download Software. My first surprise: Oracle -> 685M, Postgres -> 15,8M
2.- Read Manuals: A lot of them, with a high quality but... I can't find how to install in Debian. Google solves it: Desktop Survival Guide. Tricky but works!
3.- Manual database create/remove/test/dump...:
* create/dump: dbca is a graphical frontend than help to it; the --silent parameter let it works without graphical frontend.
* dump: exp works nice. The first test: to dump a complete void database (1 user, 1 table), takes 9 minutes and 12Mb!!!; Postgres -> 9 sec. and 200k for 100 tables/triggers.

I always hear than Oracle is the best database, but now I'm not to sure.

- The installation is too tricky.
- Create databases is slow (minutes)
- 9 minutes and 12mb to dump a complete void database? Slow!!!!!
- To work correctly you need to manually define 7 environment variables. No comments.
- It needs a big server. 500Mb Ram, 1Gb Swap, minimum.
- It's not possible to create a database remotely because it's necessary to create manually directories locally.

I was thinking about create debian packages for the new Oracle Database 10g Express Edition Beta Release , but It will be a lot of work. Maybe an alioth project?

About dbconfig-common... It will be probably finished this week, but it will need a lot of test/verify before release it.

21 January 2006

Norbert Tretkowski: Ubuntu did it again

I just prepared and uploaded ipython 0.7.0-1 for Debian, and stumbled across some undocumented changes in the Ubuntu package... tretkowski@kyllikki:~% interdiff -z ipython_0.6.15-1.diff.gz ipython_0.6.15-1ubuntu2.diff.gz wc -l
501
They disabled the python2.2-ipython package, which is documented in the changelog. But there were two more patches added, which aren't mentioned in the changelog, there's just a mysterious "Resynchronise with Debian" entry. One of these two patches was integrated upstream a while back already.

Bartosz Fenski aka fEnIo: text-mode mp3 player

Speaking about text-mode mp3 player. I'm using moc (available in archive) and its main advantage over orpheus is that it is NOT a frontend, so it can easily rewind/forward songs. Try it ;)

Bartosz Fenski aka fEnIo: new computer

I've finally bought notebook. It's Compaq Presario V2000, Pentium 1,66GHz Centrino, 512MB of RAM and 80GB disk. The most funny thing is that I couldn't install sarge on it. Running installation with 2.4 kernel caused oops of kernel, while running it with 2.6 worked quite well but ethernet card didn't work, although it was detected nicely.
Anyway I started from woody, then sarge and now I've got sid on it. Everything seems to work nice (I didn't try suspend-to-something yet, but it's not so important for me). I had to use hotplug for my Intel 2200BG wireless card. The only thing which makes me scared is:
(root@lapik)~#lsmod   wc -l
109
(root@lapik)~#
I've never had so many modules and it's mainly because hotplug tries to detect everything on startup. Do we have some hotplug replacement? Something which could be used only for loading firmware to wireless card.
Sound card works with i810_audio modules, so I suppose that's not alsa, but oss. Couldn't figure out yet what's wrong with alsa modules.
Anyway I'm quite happy the way Linux works on my new toy ;)

Simon Richter: Here be dragons

I have ventured into the realms of packaging kernel modules again. It hurts a lot less than it used to, but still isn't that straightforward. The biggest WTF was certainly the toplevel Makefile telling gcc to look for include/linux/autoconf.h . While this works fine from the toplevel of an actual kernel tree, it does less so when only the include directory of said tree is on the path, as there is no include/include directory. Some minor problems are the powerpc arch name transition (which makes asm symlinks go wrong) and that kbuild wants to create dependency files and temporaries in the source tree.

20 January 2006

Brian Nelson: What does removing GFDL documents accomplish?

One thing I just don’t understand about the whole GFDL debacle is why it’s so urgently important to purge all GFDL documents from Debian. For those documents with invariant sections, I can kind of see the point. Invariant sections clearly violate DFSG3, and we’re obligated by the social contract to abide by the DFSG. Granted, we’ve been distributing non-modifiable documents since Debian’s inception, so that’s a rather shocking change in policy. Thanks to some “editorial changes” to the social contract, the Debian distribution has to change in fundamental ways. What’s even more suprising is that the changes in policy are going far beyond the requirements in the DFSG. According to the draft position statement, there are two problems in addition to the invariant sections–the “DRM” restriction and transparent and opaque copies. Note that in the GR proposal, the invariant section problem is explained by quoting DFSG3. However, the other two problems are not given any reference to the DFSG, and for good reason–there is no clear DFSG violation in either one. Sure, they’re icky, worded poorly, and no one particularly likes them. But since when is that grounds for removal from Debian? Even worse, overriding the interpretation that these problems are DFSG violations will require a 3:1 super majority thanks to the secretaries opinion on the matter. Apparently, we are being strong-armed into purging all GFDL documents from Debian, which little chance of reversing this decision. So, what does this accomplish? The only positive benefit I can see is that some people get some warm fuzzies for sticking it to the FSF and interpreting our foundation documents as strictly as possible. Is that really worth it? Instead of crippling Debian, why not work gradually to improve the state of documentation? We could work on gradually convincing upstreams to dual-license documentation, which is particularly desirable given the GPL/GFDL incompatibility. We could setup a project to produce “really free” documentation to replace current GFDL documents. We could try to educate a wider audience on the problems of the GFDL–you do realize that most of the outside free software community views us as wacky license nazis, right? Producing a totally free operating system should be a goal, not an absolute requirement. It’s something we should strive for, but realize we’ll never achieve perfection since there will always be license problems in a set of software the size of Debian. But what are we going to do instead? Just remove the stuff that’s currently irritating us while ignoring the big picture. Good bye users, good bye useful operating system. It was nice knowing you.

Eric Dorland: I *knew* this quiz was out to get me...

Your Social Dysfunction:
Paranoid


You show pervasive and unwarranted suspiciousness, and mistrust of others. You are overly sensitive and prone to jealousy.

Take this quiz at QuizGalaxy.com

Please note that we aren't, nor do we claim to be, psychologists. This quiz is for fun and entertainment only. Try not to freak out about your results.

Eric Dorland: Spins a web, any size...

Nice, he's my favorite: Your results:
You are Spider-Man
Spider-Man
85%
Hulk
75%
Green Lantern
70%
The Flash
65%
Superman
60%
Robin
55%
Iron Man
45%
Catwoman
45%
Batman
45%
Supergirl
43%
Wonder Woman
28%
You are intelligent, witty,
a bit geeky and have great
power and responsibility.
Click here to take the "Which Superhero are you?" quiz...

Amaya Rodrigo: ZzZzZzZzZz

For the first time in more that 10 days, I slept like a baby last night. It might hurt the xlibs-dev transition, but I hope it actually helps in the long run, I will make less mistakes, bug vorlon and dato a bit less, be more aware and awake. Now I just need to keep a balanced sleeping schedule again. I think have good allies.

I have started a small experiment that is against all rules but might spread some package love. So far, I have been successfully working with Victor Seva, Justin Pryzby, Thomas Viehmann and Nico Golde. Join us if you care about this transition!

On the other hand, I find recent threads in debian-devel, debian-private and several posts in debian-devel-announce very distracting. Although I am strongly opinionated on the subjects being discussed, I'd rather remain semi-silent and work in my "NMU love".

Amaya Rodrigo: Blow up in my face



The stressful situation I am going through, one day before my talk at Debconf-es II can be described as:

* SAPFU - Surpasses All Previous Fuck Ups
* SNAFU - Situation Normal: All Fucked Up
* SUSFU - Situation Unchanged, Still Fucked Up
* FUMTU - Fucked Up More Than Usual
* FUBB - Fucked Up Beyond Belief
* TARFU - Things Are Really Fucked Up
* TOFU - Things Ordinary: Fucked Up
* GFU - General Fuck Up
* SAMFU - Self Adjusting Military Fuck Up
* TUIFU - The Ultimate In Fuck Ups
* IHTFP - I Hate This Fucking Place
* DILLIGAF/DILLIGAS - Do I Look Like I Give A Fuck/Shit?

Thanks to h01ger for the pointer to the wikipedia entry that describes what my work situation turned into this Tuesday (the 13th).

While I bang head on my keyboard, I have been heard to mutter "Morons... I am sourounded by morons".

Next.

Previous.