The Linux Action Show! Season 10 Episode 9

The Linux Action Show! Season 10 Episode 9

This Week on, The Linux Action Show!

We go over Google’s new Chrome OS, cover why Amazon went all 1984 on 1984, we find out who contributes the most code to the Linux kernel, and WE WILL TELL YOU ALL ABOUT IT!

Then we break down why sometimes open source projects just never get it right, and it’s not what you think!

Thanks for using our code LINUX & LINUX20 at GoDaddy.com when you checkout!

All this week on, The Linux Action Show!

You can stream the video, or download the many fancy versions below:

THIS WEEK’s LINKS:

The US Postal Service, Runs Linux

Google Chromium gains native theming support on Linux

Google Announces Open Source Operating System

Nokia adopts Qt toolkit for next-generation Maemo platform

Maemo switches to Qt

Intel claims No. 2 Linux contributor spot

Microsoft issues patent promise, dispels Mono legal concerns

Why Amazon went Big Brother on some Kindle e-books

4 Responses to “The Linux Action Show! Season 10 Episode 9”

  1. tempzzilla Says:

    Possible solution to lack of leadership in opensource development (opensource devs dont like having managers – like in the the waterfall model):

    You need to explain to the devs, (and the leaders) that the dev team is like a bunch of tugbats pulling with cables a big sluggish barge trough water, if they pull in diferent directions, the pulling power is disipated, and advancement is slow, they need to pull all in one direction. That means they would have to perhaps give up some of sidetrack features they would like to implement, and instead move as a team, on only the features that are decided colectivelly by the team. Also this requires maturity of the devs, else you have a bunch of children saying “if this feature isnt impemented, I pick up my toys and leave”. By all mens, let them leave. In the long term, it is better for the project.

    Also you need the manager to give them this speech (and perhaps draw them two pictures, for better effect, one with two tugboats pulling at a large angle from eachother, and one with them pulling in the same direction, or on a small angle).

    The new management and leadership paradigm slash metaphor would be that they need somebody to stay behind and keep an eye on the tugboats, and tell them when they are gettting off-course. This is the manager performing the role of a valuable helper, and not as a slave driver-boss. The manager`s role would be like that of a rudder, providing help and valuable service to the team, and not that of the traditional manager viewed as making demands.

    Sort of like the saying Jesus: let the one who wants to be greater among you be a servant. The manager would be focused on providing service and help, as oposed to the traditional view of the manager providing demands and stress.

    Also the devs have to realize that they have to sacrifice some of their ideeas for features that are too off course from the main thrust, for the sake of working as a team. So the features would be discussed at the beggining and selected by team vote or something, and also perhaps they woud have to discuss features to leave out (features that perhaps are great, but are too divergent from the main direction of development, and thus focusing on them would lessen the momentum of the main thrust)

  2. tempzzilla Says:

    Possible solution to lack of leadership in opensource development (opensource devs dont like having managers – like in the the waterfall model):

    You need to explain to the devs, (and the leaders) that the dev team is like a bunch of tugbats pulling with cables a big sluggish barge trough water, if they pull in diferent directions, the pulling power is disipated, and advancement is slow, they need to pull all in one direction. That means they would have to perhaps give up some of sidetrack features they would like to implement, and instead move as a team, on only the features that are decided colectivelly by the team. Also this requires maturity of the devs, else you have a bunch of children saying “if this feature isnt impemented, I pick up my toys and leave”. By all mens, let them leave. In the long term, it is better for the project.

    Also you need the manager to give them this speech (and perhaps draw them two pictures, for better effect, one with two tugboats pulling at a large angle from eachother, and one with them pulling in the same direction, or on a small angle).

    The new management and leadership paradigm slash metaphor would be that they need somebody to stay behind and keep an eye on the tugboats, and tell them when they are gettting off-course. This is the manager performing the role of a valuable helper, and not as a slave driver-boss. The manager`s role would be like that of a rudder, providing help and valuable service to the team, and not that of the traditional manager viewed as making demands.

    Sort of like the saying Jesus: let the one who wants to be greater among you be a servant. The manager would be focused on providing service and help, as oposed to the traditional view of the manager providing demands and stress.

    Also the devs have to realize that they have to sacrifice some of their ideeas for features that are too off course from the main thrust, for the sake of working as a team. So the features would be discussed at the beggining and selected by team vote or something, and also perhaps they woud have to discuss features to leave out (features that perhaps are great, but are too divergent from the main direction of development, and thus focusing on them would lessen the momentum of the main thrust)

  3. 3vi1 Says:

    I think no one freaks out about Samba because it doesn't “infect” (most) other apps and set them up to have the chair kicked out from under them. I actually like the idea of Mono… and have written lots of Win C# code. But, I can't fault anyone for being wary, given MS's track record.

    I use NFS myself, so I don't care about Samba one way or the other.

  4. Love-dress Says:

     

    Evening dresses on
    sale
    http://www.edressesonsale.com/

    prom dresses
    http://www.promdressforever.com/

    wedding dresses
    http://www.zarabridal.com/

    cheap wedding dresses
    http://www.weddingsvogue.com/

    dresses
    http://www.dressupforever.com/

    dresses
    http://www.mylove-dress.com/

    wedding dresses
    http://www.weddingdressesparty.net/

    cheap wedding dresses
    http://www.lightweddingdresses.com/

Leave a Reply