As promised, today Google published the final results for the 2007 Summer of Code draft. Haiku is assigned 8 student who will all work on their own project (mentored by six members from the Haiku development team). Initially Haiku aimed for 7 places and received 42 applications. Here is a list of the projects that will be worked on:
The official development period starts on May 28 and will end on August 31, in the mean time the fresh developers have time to get to known the existing team and get familiar with the code-base. All in all huge boost of manhours to get R1 done!
Bryan Varner, long time Be community member and main developer of Transmission, posted a (very) short guide on how to get a working Haiku development environment running on Ubuntu. Althought the ‘guide’ does not really go into much detail, it pretty much sums up all the steps you have to take to end up with a bootable build of Haiku.
Read Bryan’s guide here, and Biffi’s post here.
According to BeOS France (and also ICO and OSNews) now even Jean Louis Gassée, former CEO of Be inc., has something to say about the issues around Zeta’s legality. JLG has confirmed to Remi from BeOS France that at the time that Palmsource was still the legal owner of the ip, yellowTab did not have any agreement with them. As we all know, JLG use to be a board member for Palmsource, and with his background it would likely that he would have known about such an agreement. Update: It seems that in the hurry of posting about the above I misread something. The statements by JLG are from an earlier time, they just were never posted. JLG didn’t actually respond to the recent troubles of Zeta like the title on this post suggests. The statements are still valid though, Remi explains:
Click below for a translation of the text on BeOS France. All the kudos for taking the time to translate it for me go to my Belgian friend Manette, as je ne parle pas Francais…
Sikosis and co. celebrate one year of Haiku podcasts with episode number nine. This episode is about the BeBits app of the year, the various Haiku presentations and much much more. Also there is an interview with Curtis and Urias from the distributed computing Team Haiku. Get the Haiku podcast #09 (in .mp3 format) here, oh and before I forget, Happy Easter!
There has been a lot of activity on the Haiku project website this Easter weekend. Let’s start with the news that Bruno will be giving a presentation titled ‘Introducing the Haiku Operating System’ in Brazil. The presentation will be held on Friday the thirteenth at the International Free Software Forum (FISL 8.0) in Porto Alegre.
Also in the news is an update on the Haiku GSoC adventure. Google has assigned 7 (preliminary) student slots to the project, the exact number of people the team intended to have. The students have been selected out of 42 (!) applications and on April 12 the final list of projects will be posted on code.google.com. Although the students will work on the projects during summer some of them can’t wait, look here! Update: I just came across this very interesting thread on the Haiku forums: Donation, Funding – organized campaign. Initiatives like these can make a difference, I’d love to own an original Haiku T-Shirt, and with buying it make a contribution to the project.
As the saga regarding ZETA’s legality continues, several new pieces of information have surfaced. In the comments for the OSNews “ZETA Timeline,” David Scheslinger has posted a response to some of the questions raised in the timeline article. Schlesinger’s response helps to clear up a few obvious questions – including why ACCESS chose the BitsOfNews.com comments section to make their first public statement on the matter. In addition to the timeline published by OSNews, Haiku developer Marcus Overhagen has written his own summary of the current situation and the events which led to it. Aside from providing a handy overview to those who haven’t followed recent events closely, it also contains English translations of several BerndsWorld.com posts that had previously only been available in German. And finally, there appears to have been some recent public discussion between Schlesinger and Korz. Schlesinger does mention an unsuccessful attempt to make a comment to Korz’s blog (and suggests that the comment was deliberately removed), but the post he mentioned was later visible on BerndsWorld.com. The site appears to be offline at the moment, however, and it’s currenty unknown if the outage is due to technical or legal reasons (the server itself appears to be online, but the page presently displays 403 permission errors).
There have several new developments in the wake of recent comments made by David “Lefty†Schlesinger of ACCESS Ltd.; he recently stated that Bernd Korz never had a legal right to distribute a BeOS derivative. Shortly following Mr. Schlesinger’s comments, Bernd Korz posted a brief response on his blog. The post contains little information beyond mentioning that Bernd is scheduled to consult a lawyer, but he does at least promise some clarification once the discussion has taken place. Schlesinger’s original comments were, in turn, a response to the announcement that Bernd was considering an open source release of some portions of ZETA. The situation has also prompted a response from MagnusSoft – who had still been distributing ZETA following the recent end of their business involvement with Bernd. But due to the statements made by Schlesinger, it was announced today that MagnusSoft will no longer distribute ZETA (1.21 or 1.5) – at least until the legal uncertainties have been resolved. And lastly, OSNews has posted a timeline summarizing the history of ZETA and ZETA development. While a few things are left out (there seems to be no mention of “BeOS NG,” the original product announced by yellowTAB), it does still provide a good overview of the past few years. Update: As 0033 mentions in the comments, there is some good news as well: Vasper from BeOS Max has written on his blog that he has been in contact with David Schlesinger from ACCESS. According to the post, they do not see a reason to interfere with BeOS Max development.
|
|||||||||||||||||
|