Slashdot Mirror
NetBSD Branches pkgsrc-2005Q1
jschauma writes "NetBSD's Alistair Crooks has
announced the availability of the new stable branch pkgsrc-2005Q1 of the
NetBSD Packages
Collection (aka pkgsrc). This branch
includes all the updates to the thousands of existing and additions of
hundreds of new applications since the hereby obsoleted pkgsrc-2004Q4 branch.
Some noteworthy infrastructure changes applicable to all 13 operating systems
for which pkgsrc is available include the support for multiple digests to
check the integrity of the distribution files as found on the Internet
(triggered by the recently-found
problems with the SHA-1 algorithm) and the so-called alternates
framework."
In other BSD news, the FreeBSD 5.4-BETA1 is out as well.
I know it's been around for a few months now, but does anyone else think NetBSD's new logo sucks?
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It
I just read the news on the drudge report -- vegetable/sex slave Terri Schiavo is dead. No other details were available. Even if you didn't argue that she should be allowed to live, you probably argued that she should be put out of her misery. Truly an abortion rights proxy icon.
29 March 2005
Atkinson is working on BSD sequel
Rowan Atkinson is to return to the big screen as the pathologically clumsy BSD.
Variety reports that Atkinson is working with Simon McBurney, the actor-director behind acting troupe Theatre de Complicite, to develop the film.
Theatre de Complicite is well-known for its fusion of physical theatre and comedy.
The film is likely to begin shooting later this year.
It will run on a SPARC 2000 Cluster and will make kittens explode on contact with a small mars lander in contact with the head of a large kitten dancing in one million meow moew moew moew meow!!!
WOOF said the dog - what did the cat say?
NIG JHARY BOLLOESF