Just as an aside - we seem to be crossing paths a lot on here... I think you should just hire me as your PR and/or developer guy ;). It's always good to have a

Just as an aside - we seem to be crossing paths a lot on here... I think you should just hire me as your PR and/or developer guy ;). It's always good to have a guy with a different perspective who thinks and plays outside the box. I mean inside the box is so boring.... > I do wonder how would you define the patch file? Something like.... > A patch file contains the modified file name, author of the change, date, hash with snippets of content recording the changes. A patch file cannot contain enough information to reconstruct the software in whole or modify the CE to include copyrighted features in the EE edition. The author must not knowingly introduce backdoors, exploits, or other code that introduces malicious intent. If the author is identified their gitlab EE license will be revoked irrevocably and permanently and requested to halt any use of gitlab EE. (However - a patch may still introduce features from the EE edition that were written with original code) > A patch may be released under whatever license or agreements the author wants without the requirement for permission from Gitlab if it satisfies the previous conditions. It might be good to add a clause: > By applying a third party patch you agree to not hold Gitlab liable for any damages or misconfigurations that might happen by applying the patch. You acknowledge by applying a third party patch that it may fix your problem, introduce a new problem, or open a tear in the space-time continuum. I'm sure you get the idea. I'm tired and I just watched an episode of Doctor Who - so I had to include something related to time :).