It's not that we're not sure of an answer...it's that we were all at ApacheCon at that time ;) and many of us are still at conferences, so our response times are quite long right now. It'll get better in the coming weeks.
If you need solid advice on licensing and compliance, I suggest you reach out to Justin McClean or Marvin Humphrey (both ASF and IPMC members), as they are very knowledgeable in this field. With regards, Daniel. On 10/05/2015 07:29 PM, Stephen Mallette wrote: > Just thought I'd bump this to the top of the list again. I'd really like > to get LICENSE/NOTICE solid for the next release. If there are no mentors > sure of an answer, I'll take the question to general@incubator and see if a > anyone in that larger audience has the answer. Or if there is a better > place to go than that, please let me know. > > > > On Mon, Sep 28, 2015 at 12:15 PM, Stephen Mallette <[email protected]> > wrote: > >> Mentors, >> >> I feel like I'm on the verge of getting LICENSE/NOTICE right in all >> respects. Seems like there's one piece that's out of place and could use >> some advice as I wasn't able to map anything I'd read in the Apache docs on >> this topic to my issue. We currently shade several libraries: Kryo, >> minlog, objenesis, and jackson, essentially re-packaging those dependencies >> in a jar called gremlin-shaded. >> >> As we didn't re-package the source code of these libs, I figured that the >> source LICENSE/NOTICE didn't need to change. They are of course in the >> binary distributions so I figured that the binary LICENSE should reference >> them in some way so I made entries in this fashion in LICENSE (left NOTICE >> unchanged): >> >> >> https://github.com/apache/incubator-tinkerpop/blob/5a8b61c09868e22a415c0469a2737d68acce9a4e/gremlin-console/src/main/LICENSE#L226-L228 >> >> Is that sufficient or is there a particular method that should be used to >> indicate our usage of these libs in gremlin-shaded? >> >> Thanks, >> >> Stephen >> >> >> >
