On 09/02/2019 21:33, Kaganski Mike wrote:
Hmm... I'm sorry for not being clear. My point was that since our
patches (in our tree) were changing Firebird, they *automatically*
IANAL - but I suspect this process very much depends on the license in
question, and the contribution policy for firebird - as an aside the:
https://firebirdsql.org/en/get-involved/
has an unhelpful 404 for "contributing patches" today.
Either way this is certainly -not- the right forum to discuss legal /
licensing questions.
As a general yard-stick, (and depending on the project) - encouraging
those who create the patches to submit them up-stream themselves is a
good idea. We really do want to get these things up-stream - so it's a
great initiative Julien.
ATB,
Michael.
--
michael.meeks@collabora.com <><, GM Collabora Productivity
Hangout: mejmeeks@gmail.com, Skype: mmeeks
(M) +44 7795 666 147 - timezone usually UK / Europe
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.