Linked by Thom Holwerda on Wed 4th Apr 2007 21:29 UTC
Zeta A lot of things have happened in the past few days concerning Zeta, BeOS, and Haiku. In order to create some order in the chaos, Eugenia and I have created a rough timeline of what happened the past 6-7 years. Read on for the timeline and some more thoughts on the matter. Update: Magnusoft ceases distribution of Zeta. Update II: Access answered the questions posed in the article.
Permalink for comment 228331
To read all comments associated with this story, please click here.
Lefty
Member since:
2007-04-05

I've answered this question at least a couple of times, most recently in email. As a time saver (for me) I'll reproduce that response and give it a catchy title in the hopes that more folks will read it:

Releasing anything to open source requires a considerable amount of due diligence to ensure that the code being released is not encumbered in any way.

The BeOS sources amount to roughly 3/4 of a gigabyte of code. Having anyone "just come in" and do whatever to it would take a considerable amount of time and effort, and I'd still have to be involved myself and involve my engineering staff, who'd have to take the time to familiarize themselves with that 3/4 of a gig of stuff which we're don't, and don't stand to, derive any income from.

Preparing code for open source release takes considerable work, and it's not simply engineering work, either. There's no quick 'n' dirty way to make it happen--not without my company taking on what I'd consider to be significant and unacceptable risk. Since I am the open source compliance officer for the corporation, I'm required to go through the due diligence necessary to ensure that I'm not placing my employer in a problematical position. That's not a task I can take on lightly, particularly when my time is quite well-filled with activities which are directly relevant to our actual business activities, something that, as I've indicated, BeOS is not. Sorry: them's the facts.

So, I won't make any statement one way or the other as to whether we'll release the BeOS sources. And--in all sincerity, not to aggravate you further--if we decide to, you'll know about it when we do it, and not before: I donít want to create expectations in the community which I can't, ultimately, fulfill. For similar reasons (and issues of security, exposure to NDA'd third-party intellectual property, and the like aside), I'm hesitant to involve a raft of engineers, unknown to me, of uncertain quality, whose work I'd have to oversee anyway.

Operating systems are complex, as I'm sure I don't have to inform people here. You can't "just" do anything. Sorry, again, but that's a fact, too. You don't have to like it, but I can't change it.

I hope this clarifies my position and situation and provides some context.

Reply Parent Score: 5