Of course, you can fork Haiku. All of the original Haiku code is MIT licensed, though you have to check with some of the subsystems, like AGG and FFMPEG etc. Also, please have a look at Haiku Inc.'s trademarks page. The Haiku name and logo are trademarked.
Yes,but expect very little help with your fork from the people working on the present one.
Note: If you have not done work on an OS before or don't have a team of people to help you, you will find it is not as easy as some people think or may have told you.
First: Get the source code to Haiku-OS
Second: Study it, then study it again, the study it once more. Do you understand the code?
Third: Ask yourself do I need to fork the OS to get what I want or can it be included into the present work?
If your answer is I have to fork, then good luck.
If your answer is it could be added to the present OS, then contact the developers and see what they think of your ideas.
Or do what I am doing. I am trying to develop my code first, test and polish it, then present it to the developers and see what they think.
For example Haiku-OS already has a ram drive and ram-fs that are better than my own ram drive, but I am interested in some ideas that Haiku's developers will not waste time on since it will take away from developing the present Haiku-OS towards R1. I want to finish developing my ideas then once I have STABLE - WORKING versions show them what I have. They may take my code, they may reject my code but take the ideas, or they may reject everything I write.
But I will have working code, and it will run on my machine so I have not lost out, and I can always put my code on the Haiku download sites for others to use.
Forking an entire OS just to say you did is dumb in my mind. It would be a lot of work with no gain.
If you have a good reason to fork, go ahead, but I can't imagine at this stage of development why you would want to do that.
What possible reason do you have to want to fork the OS now?
Of course, you can fork Haiku. All of the original Haiku code is MIT licensed, though you have to check with some of the subsystems, like AGG and FFMPEG etc. Also, please have a look at Haiku Inc.'s trademarks page. The Haiku name and logo are trademarked.
Can you please get in touch if you are interested in doing a fork? I am also interested to do the same for the art project and intellectual exercise (proof of concept), but would need help with this.
Comments
Re: Haiku Fork
Hi hydragon!
Of course, you can fork Haiku. All of the original Haiku code is MIT licensed, though you have to check with some of the subsystems, like AGG and FFMPEG etc. Also, please have a look at Haiku Inc.'s trademarks page. The Haiku name and logo are trademarked.
Regards,
Humdinger
Re: Haiku Fork
Yes,but expect very little help with your fork from the people working on the present one.
Note: If you have not done work on an OS before or don't have a team of people to help you, you will find it is not as easy as some people think or may have told you.
First: Get the source code to Haiku-OS
Second: Study it, then study it again, the study it once more. Do you understand the code?
Third: Ask yourself do I need to fork the OS to get what I want or can it be included into the present work?
If your answer is I have to fork, then good luck.
If your answer is it could be added to the present OS, then contact the developers and see what they think of your ideas.
Or do what I am doing. I am trying to develop my code first, test and polish it, then present it to the developers and see what they think.
For example Haiku-OS already has a ram drive and ram-fs that are better than my own ram drive, but I am interested in some ideas that Haiku's developers will not waste time on since it will take away from developing the present Haiku-OS towards R1. I want to finish developing my ideas then once I have STABLE - WORKING versions show them what I have. They may take my code, they may reject my code but take the ideas, or they may reject everything I write.
But I will have working code, and it will run on my machine so I have not lost out, and I can always put my code on the Haiku download sites for others to use.
Forking an entire OS just to say you did is dumb in my mind. It would be a lot of work with no gain.
If you have a good reason to fork, go ahead, but I can't imagine at this stage of development why you would want to do that.
What possible reason do you have to want to fork the OS now?
Please I would like to know.
Re: Haiku Fork
Hi hydragon!
Of course, you can fork Haiku. All of the original Haiku code is MIT licensed, though you have to check with some of the subsystems, like AGG and FFMPEG etc. Also, please have a look at Haiku Inc.'s trademarks page. The Haiku name and logo are trademarked.
Regards,
Humdinger
Also: http://haiku-os.org/about/trademark_policy and
http://www.haiku-os.org/community/guidelines_creating_haiku_distribution
Re: Haiku Fork
Hi Hydragon!
Can you please get in touch if you are interested in doing a fork? I am also interested to do the same for the art project and intellectual exercise (proof of concept), but would need help with this.
Best wishes - Zeljko