You're right, we should've released before the PM merge. Oh well, too late for that now. Instead we'll content ourselves with straightening out the mess that is HaikuPorts and deciding what and when the next release should be. And what the blockers are.
And I hope I can get such a distribution out by Christmas...
I truly apologize that the above-mentioned claim I made earlier has not happened yet; I wanted to remind everyone that I completely remember this and have not forgotten about it. Right now, I'm still working on the design for various features of the fork/distro, but nothing is ready to present yet as any type of public release, alpha or not. I hope to reply back once I do reach that point... until then, I do apologize and hope to reach my goal(s) soon.
Happy New Year! (And I truly hope everyone had a happy Christmas!)
All of the features you listed on "what a fork should have" (e.g. EFI[64], theming) we want in Haiku, and most of them are WIP already. The problem of GNU/Linux "distributions" and the fragmentation it creates is exactly what most of us wanted to avoid by choosing Haiku over Linux. While certainly there were other factors (C++, not C? BMessages? packagefs? Heck yes!) I think that the unification of efforts & communities was a (very) significant selling point, at least for me anyway.
So, in short: Get involved with development! Help finish the things we've already begun! Don't fragment the community and force users to choose between Haiku and [insert name of some distro here].
On the other hand, if all you want to do is add software, by all means create a package repository. We wanted/hoped HaikuWare would do that, but they didn't, so we're the only ones with a significantly sized one now. Although I hear there's a Russian one with some repackaged BeOS software, somewhere...
Thank you for your reply; I definitely will take your outlook on this into consideration. Perhaps it is a good thing my fork is not yet presentable, but I can tell you that it's not just new features or a new theme/look/etc. like what plague Gnu/Linux today -- it truly would be different when/if you see it.
To be frank with everyone, I was going to reply with a passionate, long defense for it, but have decided to instead be quietly patient and just write this...
Back in 2010, some here may remember I discussed the idea of making a fork. I quit and left due to concerns like the one above. I continued learning quietly after that, and finally, earlier this year, I boldly decided to mention working on a fork again -- only this time, I actually am working on making it a reality. However, before I release anything, I believe in conscience and want to do so knowing I'm not causing dissension or ill will by my past, present, or future actions. And I will end by mentioning the previous comment is showing me I may need to rethink what I am doing -- but only if others express similar feedback as well. I would hate to quit because of just one or two negative feedbacks, as I truly believe this has the possibility to affect change.
If you really want a working build that I think will be finished a month late, please mention it. If not, please mention it. I'm genuinely open to ALL feedback, good or bad. Thank you all. And have a happy new year!
As long as you follow the rules with regards to trademark use (basically, you can't call your fork/distro "Haiku" or something similar), we can't prevent you from doing whatever you want with the sourcecode.
If you fix some bugs, or add some new features, please try to do it in a way that can be merged back in the main Haiku sources. This should be enough to prevent fragmentation of the development efforts. I'm personally fine with making Haiku more modular and appropriate for more uses than its current ones, as long as it doesn't break existing functionality.
Back in 2010, some here may remember I discussed the idea of making a fork. I quit and left due to concerns like the one above. I continued learning quietly after that, and finally, earlier this year, I boldly decided to mention working on a fork again -- only this time, I actually am working on making it a reality. However, before I release anything, I believe in conscience and want to do so knowing I'm not causing dissension or ill will by my past, present, or future actions. And I will end by mentioning the previous comment is showing me I may need to rethink what I am doing -- but only if others express similar feedback as well. I would hate to quit because of just one or two negative feedbacks, as I truly believe this has the possibility to affect change.
If you really want a working build that I think will be finished a month late, please mention it. If not, please mention it. I'm genuinely open to ALL feedback, good or bad. Thank you all. And have a happy new year!
Please go for it.
If you have really created something different and better, I am all for it.
If my posts in the past seem very negative, it is because most people talking about forks seem to be in it just to say they have their own personal fork (selfish pride), following some latest trend (fashion) or expecting other people to do the real work (want to be the big boss).
It sound like you did all the real work yourself. If you have major improvements (even if they can not fold back into the main Haiku-OS) then I am interested in seeing your work. I hope you can meet your schedule and we can see something from you in February.
I would like to start by mentioning thank you to Haiku_Programmer and to everyone who replied with feedback; I have read it and taken ample time to contemplate it. Per the official Guidelines, I genuinely have "thought long and hard about doing so" and have ultimately decided that I will proceed and finish this endeavor that I have started as promised.
For those following this post, I think at this point in time, I cannot put a definitive deadline on when I will be ready to release anything. My original goal was Christmas, and later, I had hoped it would be at the end of this month, but there is still a lot to be done before I would be comfortable presenting anything. For now, I realistically see my actual goal as being anywhere between March-April, depending on how much spare time I have to work on it, but I am committed to this and do hope to get it done. It just appears that it will take somewhat longer than I had originally surmised.
Comments
Re: Distro based on Haiku
Re: Distro based on Haiku
And I hope I can get such a distribution out by Christmas...
I truly apologize that the above-mentioned claim I made earlier has not happened yet; I wanted to remind everyone that I completely remember this and have not forgotten about it. Right now, I'm still working on the design for various features of the fork/distro, but nothing is ready to present yet as any type of public release, alpha or not. I hope to reply back once I do reach that point... until then, I do apologize and hope to reach my goal(s) soon.
Happy New Year! (And I truly hope everyone had a happy Christmas!)
Re: Distro based on Haiku
All of the features you listed on "what a fork should have" (e.g. EFI[64], theming) we want in Haiku, and most of them are WIP already. The problem of GNU/Linux "distributions" and the fragmentation it creates is exactly what most of us wanted to avoid by choosing Haiku over Linux. While certainly there were other factors (C++, not C? BMessages? packagefs? Heck yes!) I think that the unification of efforts & communities was a (very) significant selling point, at least for me anyway.
So, in short: Get involved with development! Help finish the things we've already begun! Don't fragment the community and force users to choose between Haiku and [insert name of some distro here].
On the other hand, if all you want to do is add software, by all means create a package repository. We wanted/hoped HaikuWare would do that, but they didn't, so we're the only ones with a significantly sized one now. Although I hear there's a Russian one with some repackaged BeOS software, somewhere...
Re: Distro based on Haiku
Thank you for your reply; I definitely will take your outlook on this into consideration. Perhaps it is a good thing my fork is not yet presentable, but I can tell you that it's not just new features or a new theme/look/etc. like what plague Gnu/Linux today -- it truly would be different when/if you see it.
To be frank with everyone, I was going to reply with a passionate, long defense for it, but have decided to instead be quietly patient and just write this...
Back in 2010, some here may remember I discussed the idea of making a fork. I quit and left due to concerns like the one above. I continued learning quietly after that, and finally, earlier this year, I boldly decided to mention working on a fork again -- only this time, I actually am working on making it a reality. However, before I release anything, I believe in conscience and want to do so knowing I'm not causing dissension or ill will by my past, present, or future actions. And I will end by mentioning the previous comment is showing me I may need to rethink what I am doing -- but only if others express similar feedback as well. I would hate to quit because of just one or two negative feedbacks, as I truly believe this has the possibility to affect change.
If you really want a working build that I think will be finished a month late, please mention it. If not, please mention it. I'm genuinely open to ALL feedback, good or bad. Thank you all. And have a happy new year!
Re: Distro based on Haiku
As long as you follow the rules with regards to trademark use (basically, you can't call your fork/distro "Haiku" or something similar), we can't prevent you from doing whatever you want with the sourcecode.
If you fix some bugs, or add some new features, please try to do it in a way that can be merged back in the main Haiku sources. This should be enough to prevent fragmentation of the development efforts. I'm personally fine with making Haiku more modular and appropriate for more uses than its current ones, as long as it doesn't break existing functionality.
Re: Distro based on Haiku
Back in 2010, some here may remember I discussed the idea of making a fork. I quit and left due to concerns like the one above. I continued learning quietly after that, and finally, earlier this year, I boldly decided to mention working on a fork again -- only this time, I actually am working on making it a reality. However, before I release anything, I believe in conscience and want to do so knowing I'm not causing dissension or ill will by my past, present, or future actions. And I will end by mentioning the previous comment is showing me I may need to rethink what I am doing -- but only if others express similar feedback as well. I would hate to quit because of just one or two negative feedbacks, as I truly believe this has the possibility to affect change.
If you really want a working build that I think will be finished a month late, please mention it. If not, please mention it. I'm genuinely open to ALL feedback, good or bad. Thank you all. And have a happy new year!
Please go for it.
If you have really created something different and better, I am all for it.
If my posts in the past seem very negative, it is because most people talking about forks seem to be in it just to say they have their own personal fork (selfish pride), following some latest trend (fashion) or expecting other people to do the real work (want to be the big boss).
It sound like you did all the real work yourself. If you have major improvements (even if they can not fold back into the main Haiku-OS) then I am interested in seeing your work. I hope you can meet your schedule and we can see something from you in February.
Quick update
I would like to start by mentioning thank you to Haiku_Programmer and to everyone who replied with feedback; I have read it and taken ample time to contemplate it. Per the official Guidelines, I genuinely have "thought long and hard about doing so" and have ultimately decided that I will proceed and finish this endeavor that I have started as promised.
For those following this post, I think at this point in time, I cannot put a definitive deadline on when I will be ready to release anything. My original goal was Christmas, and later, I had hoped it would be at the end of this month, but there is still a lot to be done before I would be comfortable presenting anything. For now, I realistically see my actual goal as being anywhere between March-April, depending on how much spare time I have to work on it, but I am committed to this and do hope to get it done. It just appears that it will take somewhat longer than I had originally surmised.
Thank you, all.