Null If you go the fork route, try to upstream/keep in sync as much as possible. The more the fork deviates from the source, the more problems it will create.
Problems for us or for them? In another post you mentioned that your computer no longer boots after an update. If we just automatically sync with Haiku, that kind of errors get synced as well. Of course we can see what they are up to and adopt any good ideas. But "keeping in sync" can't be a goal in its own right.
If we take the idea of a fork seriously, then Haiku would not be "upstream" in the sense that the GNU Project is "upstream" for the core utils. The two projects would exist side-by-side from that point forwards. That may seem like a mere semantic issue, but any code transfer would be one way, from there to here, on a case-by-case basis. The Haiku devs have made it abundantly clear that they won't even look at code that may have been in contact with an LLM.
Null Just look at Linux and its surrounding ecosystem as an example of what can happen when you fork. You get thousands of different distributions with thousands of different software creating a non-cohesive user experience that wastes millions upon millions of individual man hours.
We are a very, very long way from that situation. We all wish this conversation was not necessary. But we are having it, and we are talking about ONE fork.
Null If it is possible release tweaks of the system instead. A PowerToys for Haiku if you will.
If we are not even allowed to mention it on the official channel, in our little separate ghetto, without a zealot starting another flamewar with the moderators looking on and doiing nothing, then it is time to talk about a clean break.
