Re:Should Bountysource allow committers to delist their proj...
by dllthomas on Tuesday November 11, 2014 @12:05PM
(#8590863)
'I don't think every such occasion should warrant a new name like under the traditional definition of "fork", though.'
Well, I certainly think it warrants clarity as to who is responsible for issues. That needn't take the form of "a new name" though, I agree.
Nobody is obligated to accept any patches, no matter their provenance, no matter if they were paid for. My two parties above in a mutually beneficial agreement could decide to keep the patches between themselves if upstream rejects them. I suppose that could be called a fork. I don't think every such occasion should warrant a new name like under the traditional definition of "fork", though.