dandelion to Open Source@lemmy.ml • 3 years agoAudacity introducing a Contributor License Agreement (CLA)github.comexternal-linkmessage-square20fedilinkarrow-up134arrow-down10file-text
arrow-up134arrow-down1external-linkAudacity introducing a Contributor License Agreement (CLA)github.comdandelion to Open Source@lemmy.ml • 3 years agomessage-square20fedilinkfile-text
minus-square@Echedenyan@lemmy.mllinkfedilink2•3 years agoWhat if community contributions were released as a series of patches not integrated directly? A package maintainer could download audacity source, then the community patches and make a release with them for your distribution.
minus-square@ozoned@lemmy.mllinkfedilink2•3 years agoNot sure I’m understanding the question here. Yes… they could do that, but will they? You could also do that yourself by pulling the code and cherry picking patches you want and don’t want.
minus-square@Echedenyan@lemmy.mllinkfedilink1•3 years agoThe idea is not just a fork, but a community project consiting in a series of patches.
What if community contributions were released as a series of patches not integrated directly?
A package maintainer could download audacity source, then the community patches and make a release with them for your distribution.
Not sure I’m understanding the question here. Yes… they could do that, but will they? You could also do that yourself by pulling the code and cherry picking patches you want and don’t want.
The idea is not just a fork, but a community project consiting in a series of patches.