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 228339
To read all comments associated with this story, please click here.
Member since:

Lefty, all that being true, I wonder if some of the ex-Be engineers might not undertake the work as a labour of love? Surely they have the experience with the code to be able to open up small chunks at a time. Really, releasing chunks at a time could be more useful to Haiku, because it's possible to focus on the chunks that Haiku is missing or is currently "poorer" at. I heard mention of the VM subsystem, for example. Maybe by limiting the scope and by focusing on things Haiku would benefit from, your opensourcing of sections of the BeOS source could speed Haiku development up. The way I see it is that when Haiku is ready to call itself "R1", a lot more heat goes off of the owner of the BeOS sourcecode IP to do something with it publicly.

Another thought. Given the magnitude of the task you'd undertake to actually *do* anything with the BeOS sourcecode, would ACCESS ever consider licensing the code to a third party to develop? I did get the feeling that there are people out there that would love to *do* something with the code. For example, create an updated version of the PowerPC build with BONE and using GNU tools rather than Metrowerks. Though the PowerPC market is miniscule, currently probably in the region of "hundreds" of users, there are plenty of old Mac's out there that would run BeOS though, and a PowerPC version might be made to support newer hardware too. The problem at the moment is a lack of "free" PowerPC distribution.

One final plea: Is there any chance that ACCESS could release a free version of R5.03 (last release of BeOS)? Say, ISO for PowerPC and Intel? That would actually solve an awful lot of issues that have been raised. If the binaries were released under some kind of licenset that allowed "controlled" modification and re-distribution, BeOS MAX could then become legal.

Edited 2007-04-07 00:32

Reply Parent Score: 3