News for hackers. Stuff that matters.
Re:When 'open core' projects reject contributions for compet... by zellyn on Sunday March 10, 2024 @10:38AM (#39659474)
What this makes me wonder is whether there could be a way for GitHub or its equivalents to make the concept of “a fork by patching” a first-class concept.

I’ve definitely done this for company-internal forks by trying to keep the changes as a clean list of linear commits that can be rebased as easily as possible, but it’s interesting to imagine what purpose-built tooling could do to facilitate maintaining such a patch-based fork.

Re:When 'open core' projects reject contributions for compet... by Karellen on Sunday March 10, 2024 @10:43AM (#39659530)
Re:When 'open core' projects reject contributions for compet... by PartiallyTyped on Sunday March 10, 2024 @11:41AM (#39660049)
I think at some point you will diverge to the point that sync-ing or submitting patches is unmanageable.

I heard stories of projects where every X weeks a person gets assigned to syncing, and it's almost guaranteed that the person will quit soon after. The team even had a tool to assist with the process.

Re:When 'open core' projects reject contributions for compet... by foxhop on Sunday March 10, 2024 @10:55AM (#39659642)
a set of patches to run on the Repo works but it breaks when a big refactor happens upstream.