Linked by Thom Holwerda on Sat 20th Jan 2007 18:38 UTC, submitted by fylfot
RISC OS Castle and RISC OS Open discuss there plans for the gradual unveiling of an open source RISC OS over the next twelve months. They explain their reasoning behind some of the source code restrictions in their licence. "Castle's Jack Lillingston opened the presentation with a brief run through of his company's products before outlining the shared source initiative - which is designed to get the source code to RISC OS 5 out into the open for free, and encourage third party developers to improve it. Steve then took over to explain more about how the project will be organised, and how they need donations to keep going."
Permalink for comment 203971
To read all comments associated with this story, please click here.
Why is it so restrictive?!
by reduz on Sun 21st Jan 2007 08:25 UTC
Member since:

"encourage third party developers to improve it"
As said in previous posts, this is extremely selfish..

For example, a hobby developer may want to try new ideas, ports, improvements.. that even if not very benefical to castle, it may fix or improve other aspects of the OS, or in the end, just increase the amount of developers with good knowledge of the OS (which should also be vaulable to castle). But if they make the licensing so string, they will just not appeal to that many developers, and reduce their benefit in the end..

They are too overprotective.. isnt also their business making the machines? Do you see anyone else selling Solaris, or darwing for example?

Reply Score: 1