I'm on an organization's Bylaws Committee and am using a (currently private) GitHub repository to track our proposed changes/amendments. Once the committee's work is complete, the intent is to make the repo public so other sister organizations can use it as a starting point.

I was considering including a Free/Open Source license like CC0 to make things official, but it occurred to me that we'd like to make sure that anyone reading a modified copy of the bylaws knows these are not the official bylaws of organization X.

Is there a simple way to concretely require that any modified version either remove references to my organization, or that it be clearly indicated in some way that the content has been modified? Is there an existing FLOSS-like license that would be a better fit than CC0? Should I even bother including a license at all?


For example, the TeX license states that any modified version has to be distributed under a different name. This is allowed by the Open Source Initiative.

But please read and understand David Wheeler's "Make Your Open Source Software GPL-Compatible. Or Else.". The essay is oldish, but still very much relevant. Knitting your own license is (a) a task for an expert, (b) creates an island that can't share anything with other work (unless done very carefully), thus isolating it.

  • Regarding your last paragraph, note that the OP is most likely storing documents in the repository, not software. That makes the essay essentially irrelevant. – Bart van Ingen Schenau Mar 22 at 7:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.