Slashdot Mirror


VA Lays Off Mesa Developer

j7953 writes: "Brian Paul, the author of Mesa, was laid off by VA Linux. Here's his mail to the mesa3d-dev list." Other places are reporting that Keith Whitwell of the DRI project was also laid off. Presumably just two of many major contributors to open source, but honestly I don't really know who got the axe. So far Slashdot has been unaffected by the layoffs (VA owns Slashdot too in case you live in a box).

6 of 207 comments (clear)

  1. Just start over... by update() · · Score: 3, Interesting
    At this point, VA Linux, as such, is doomed to failure. Maybe they can scrape a profit out of Sourceforge, banner ads and hypercaffeinated beverages. But it's always going to be LNUX -- the first IPO record breaker, owner of the $320 share price, the creator of Surprising Wealth, the company that was going to challenge Dell and Compaq. There's simply nothing they can do to ever get back to the point of breaking even on expectations.

    Right now they have still have a lot of cash and assets, tangible and intangible. OSDN, according to someone who responded to one of my posts and seemed to know what he's talking about, is turning a profit. (No idea how - the ThinkGeek ad I'm looking at now isn't making any money.) It's not scaring Microsoft, but it's plenty to make for an extremely well-funded startup. Come up with a new plan that you think is going to work, change the name and make a clean break. Right now, they're just circling the drain.

  2. Just in Case... Slashdot Life Raft Plans? by idonotexist · · Score: 5, Interesting

    I'm not saying this is going to happen, but let's just say for the hell of it that VA goes under.

    What would become of Slashdot? I would assume Slashdot would sink with the ship considering Slashdot is a part of VA, however, am I wrong? Is there a 'contingency plan' if this horrible event were to occur? I would think such a plan would be important with the understanding that many companies have recently come to a very abrupt end and creditors rush to hold assets (domain names, software, site content, (gasp) user infomation, etc), leaving the potential for rebirth or independent continuation of a site by a third party virtually impossible.

    --
    "There ought to be limits to freedom"
  3. Profit? by laymil · · Score: 3, Interesting

    So, seeing as Slashdot is part of VA...does slashdot itself turn a profit? I mean, i know there are a lot of users, and a lot of banner ads, but really...i'd like to know.
    That said, layoffs are common anywhere, but they still suck ass.

  4. Sourceforge? by chrysalis · · Score: 5, Interesting

    VA Linux owns Slashdot and Thinkgeek, but also Sourceforge. Sourceforge is supposed to be a major source of profit.
    But is it, really? Sure, Sourceforge is a wonderful framework for developpers and users.
    But how many companies really *need* this instead of just installing a CVS server + a discussion board + a public FTP server?
    Out of these companies, how many really will *buy* this? Especially since Sourceforge is also an Opensource project?
    Not a lot IMHO. On the other hand, Slashdot and Sourceforge requires a lot of bandwidth and computers. Plus employees. That's expensive. Surely a lot much that incoming revenues.
    So, will Sourceforge survive?
    Sourceforge has already tons of unresolved bugs. All his mailing-lists are archived by Geocrawler that explicitely states that "Geocrawler is not longer being maintained" (check the "about" button in the home page) .
    If VA fires unique people like Mesa's leader, is it also the beginning of the end of Sourceforge?

    --
    {{.sig}}
  5. What a strange trip by zairius · · Score: 4, Interesting

    When I joined Andover.net they had just changed from selling software to making websites to puts ads on (slaughterhouse,mediabuilder, and andovernews). The strategy was to develop sites that would attract page hits that required very little actual day to day managing so the developers could go build other sites. To be honest I never understood how the news site could be 'worth it' since you had to pay someone everyday just to keep the page hits even. Well I came on board and my first major project was to make a bit Gifoptimizer then Gifwizard (since they had started charging for their service). I went on to write the backend code for Gifworks and the highly obnoxious 3dtextmaker. But then the day came to ramp up page hits by acquiring damn with the costs of actually maintaining it (gifworks and 3dtextmaker now happily chug away in a back closet somewhere with probably no one watching it.... about 3 million page hits a month whose only overhead is electricity and bandwidth).
    Well we got Slashdot to bolster our page hits and Freshmeat soon followed too. Then we got bought by VA Linux. After a while they decided that OSDN(Andover.net) was costing alot of money to run so they axed everyone who wasn't involved in Slashdot or Freshmeat it seems. I still wonder what it costs to run Slashdot. I stil somewhat regret not taking the offer of working on the Slashdot database... although the days when something goes wrong I'm glad I didn't. It is amusing to see that VA Linux is not mostly what is left of Andover.net... although what is left of Andover.net seems to be primarily what we had acquired... a lot of the stuff we built before our spending spree seems forgotten or discarded. Somewhat depressing.... I have this fear if the sites I helped with ever crash... no one will turn them back on and they will fade into oblivion. Oh well just some random thoughts.

    John Casey
    Gif Spinner

  6. Re:Does it matter by stripes · · Score: 3, Interesting
    Seems reasonable to fire the people who would work on a given project for free anyways.

    Yes, and no. You lose the ability to have influence over the direction of development. For example to decide which graphics cards get worked on first/next.

    If the developer gets a new job that isn't to keep working on the code, they will also (probably) work on it less. So if VA needed the code to keep evolving then they are at risk there too.

    There is also the chance that the new employer either doesn't allow OSS work, or has such an interesting project that the developer gives up on the old project...