Maybe use codex (or claude) to from time to time merge bonsai main to bonsai pr , so will be always bonsai main + pr , not become forks but root would be always bonsai main + pr like today 0.8.5 + PR tomorrow 0.8.6 + PR
And if some PR makes problem and there is no easy fix on new main ask developer to port pr to new main
@sjb007 said:
Perhaps we borrow from Linux core developers
^this seems like a really good idea to me. In terms of open-source projects the Linux kernel is probably the largest in number of contributors of any open source project and for the most part the Linux kernel development seem to have found a very positive collaborative way of working.
I would be more inclined to use BonsaiPR if it periodically (documented somewhere how often) rebase on top of bonsai main.
One thing the strikes me is that maybe "forks" are not the best with AI as it would seem the risk that is already being seen is that the fork drifts too far away and it becomes more and more difficult to merge back together. Maybe the solution does not have to be invented new as Git already has the functionality to create ".patch" files for changes which stem from the past where contributors would send the maintainer their "patch" on a mailing list rather than through Github, Gitlab, etc. Just my two cents.
Comments
Maybe use codex (or claude) to from time to time merge bonsai main to bonsai pr , so will be always bonsai main + pr , not become forks but root would be always bonsai main + pr like today 0.8.5 + PR tomorrow 0.8.6 + PR
And if some PR makes problem and there is no easy fix on new main ask developer to port pr to new main
And then as always have high standards for main release
Maybe something to take in account for AI generated contributions?
https://github.com/github/spec-kit
Cheers!
^this seems like a really good idea to me. In terms of open-source projects the Linux kernel is probably the largest in number of contributors of any open source project and for the most part the Linux kernel development seem to have found a very positive collaborative way of working.
I would be more inclined to use BonsaiPR if it periodically (documented somewhere how often) rebase on top of bonsai main.
One thing the strikes me is that maybe "forks" are not the best with AI as it would seem the risk that is already being seen is that the fork drifts too far away and it becomes more and more difficult to merge back together. Maybe the solution does not have to be invented new as Git already has the functionality to create ".patch" files for changes which stem from the past where contributors would send the maintainer their "patch" on a mailing list rather than through Github, Gitlab, etc. Just my two cents.