View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0029170||mantisbt||customization||public||2021-10-13 03:55||2021-10-15 08:43|
|Summary||0029170: Configurations covered by GPL?|
MantisBT is covered by GPL, so I need to allow access to the source, which is basically given by not removing the link to mantisbt.org.
Now my question:
Again, I appologize, if that's not really the right place to post that question.
|Tags||No tags attached.|
Are you actually distributing your customized version of MantisBT (i.e. the source code) to your clients, for them to install ? Or just hosting a MantisBT instance with your customizations for them to use ?
My understanding is that if you're not selling or redistributing the code, then there is no need to make your changes available. Per wikipedia:
If you are redistributing the software, then GPL applies and forbids doing so under a non-disclosure agreement. But even then your specific case is debatable, because config_inc.php and custom_strings_inc.php are not part of the original distribution, and therefore IMHO not covered by the GPL.
That said, I am not a lawyer... And speaking for myself here, I'm definitely not going to sue you over this ;-)
Anyway... it looks like we will not write a NDA anyway, just because even if we would, there's almost no way how to prove that the customer disclosed information to others: Too many ways to configure mantis the same way or slightly different (e.g. they could use the database instead).
And even if they do: we (and especially you guys as developers) can be proud, that this wonderful piece of software get distributed all over the place to solve all sorts of problems.
A big shout-out to you! Thanks!
Issue can be closed in my eyes (except if you would like to continue the discussion)...
Oh, just wait with closing the issue for a while.
Will paste answre to this issue for later references