> you are sure about this? thought the donation paper work is signed right?
Not yet as far as I know; last I heard was a week or so ago.
On Tue, Apr 24, 2018 at 1:41 PM, Slim Bouguerra
wrote:
>
> > On Apr 24, 2018, at 1:18 PM, Gian Merlino wrote:
> >
Do you mean the license headers? Those, I think, we shouldn't change until
the code is imported into Apache.
If it's possible to use Rat to audit dependency licenses without looking at
the license headers of our own files, that would still be useful at this
point.
On Tue, Apr 24, 2018 at 12:57
I can do this. I'll make an issue for this in Github and raise a PR.
Jihoon
2018년 4월 20일 (금) 오후 12:30, Gian Merlino 님이 작성:
> Does anyone have experience with RAT (https://creadur.apache.org/rat/) and
> a willingness to do a PR to set it up for us? I think we can do this
Does anyone have experience with RAT (https://creadur.apache.org/rat/) and
a willingness to do a PR to set it up for us? I think we can do this even
before migrating sources to Apache.
On Fri, Apr 20, 2018 at 10:52 AM, Slim Bouguerra
wrote:
> As Suggested above, RAT is
The main tool to use is Apache RAT. Definitely use that.
One of the hardest tasks is getting the contents of LICENSE and NOTICE right.
That is a manual task I’m afraid.
Julian
> On Apr 18, 2018, at 08:34, Gian Merlino wrote:
>
> Hi Slim,
>
> Do you know if ORC &
Hi Slim,
Do you know if ORC & Hive use this tool as part of their release process?
And if it's considered a good tool by itself for verifying we meet all of
the Apache licensing requirements, or if we'll need something else too?
On Tue, Apr 17, 2018 at 9:15 PM, Slim Bouguerra
One of the question last dev synch was about the generation of dependency
licenses.
Some projects (ORC and Hive) use the maven site plugin that can generates
reports with all the dependencies and licenses details.
I have run it on Druid and this is how it looks for Druid Api Module.
cmd
mvn