On 07/10/2018 19:36, Tamás Zolnai wrote:
As I see LO's license is not compatible with LLVM license [1], as LLVM
license is a more permissive license which allows to make the code part
of a proprietary software for example. So I just wonder what is the best
way to integrate things to clang from
Hi All,
Thanks for the feedback and ideas. It might be a good idea to discuss this
on ESC and make decision how to relicense the compilerplugins code (if
relicense at all) and also how to avoid to get different licensed files
under compilerplugins folder later.
For now I'm OK with asking the
On Wednesday 10 of October 2018, Kaganski Mike wrote:
> On 10/10/2018 10:53 PM, Tamás Zolnai wrote:
> > With this new information I agree that it would be the best to clear the
> > licensing and use LLVM in every source file under compilerplugins
> > folder. So the question is what is the best way
On 10/10/2018 10:53 PM, Tamás Zolnai wrote:
> With this new information I agree that it would be the best to clear the
> licensing and use LLVM in every source file under compilerplugins
> folder. So the question is what is the best way to do that. What is the
> best way to ask every authors
Hi Lubos, all,
Thanks for the feedback. I did not notice that a lots of compilerplugins
source files are actually licensed with LLVM license, not only the plugin.*
files. I expect that it happened as you described, LO header template was
just copied without considering what is the right license.
On Sunday 07 of October 2018, Tamás Zolnai wrote:
> Hi all,
>
> I plan to work on clang static analyzer in the next monthes and I'm
> wondering whether how we can move some of the LO's compiler plugins to
> upstream.
>
> As I see LO's license is not compatible with LLVM license [1], as LLVM
>
Hi Noel,
It's good idea to pick up one plugin first and discuss with the authors and
relicense that plugin only. I think this also means that we'll need to
change the license header of the plugin's source file to LLVM license so
it's unambigous what is the license of this specific plugin. The
IANAL, obviously, but possibly you could pick the plugins you want and ask
all the people who worked on that plugin to re-license their work (there
are not that many, and they are mostly still around)
For the record, for anything in compilerplugins/ that I have touched, I
grant you permission to
