If you copy code then you should have Matt provide a software grant. You should file an ICLA for your own work. See http://www.apache.org/licenses for that.
Ralph On Mar 25, 2013, at 10:49 AM, Nick Williams wrote: > Permission obtained from developer of slf4j-taglib (Matt Humphreys) to use > code from that project. On previous projects I've worked on (Spring, > FasterXML) I've had to sign a contributor agreement before my code could be > accepted. If either Matt or I need to do this, please let me know. > > I'll get started on this right away. > > Nick > > Begin forwarded message: > >> From: Matt Humphreys <[email protected]> >> Subject: Re: Requesting permission to use source code from slf4j-taglib >> Date: March 25, 2013 12:35:55 PM CDT >> To: Nick Williams <[email protected]> >> >> Hi Nick, >> I'm happy for you to use all the code you want from slf4j-taglib - >> permission granted! >> >> Shout if i can be of any assistance :) >> Matt >> >> >> On 25 March 2013 17:30, Nick Williams <[email protected]> wrote: >> Hey, Matt. I emailed the SLF4J development list earlier, mistakingly >> believing they were in charge of slf4j-taglib. They told me I should email >> you instead. >> >> I'm working on a tag library module for the new Log4j 2 coming out >> (hopefully) later this year. Your slf4j-taglib sub-project is based on the >> Jakarta Commons Log Taglib, which was built for log4j and is retired. Log4j >> 2 is a vast improvement over Log4j, and some of its features were inspired >> by SLF4J. There is undoubtedly some very interrelated code history here, >> though I don't know the exact details of that on either side. >> >> Though the Log4j 2 tag library will obviously have some differences from >> slf4j-taglib, I can see how there may be some existing code that could be >> very useful to us. I'd like to go ahead and ask permission to use code from >> slf4j-taglib for this project. The licenses are compatible (both Apache >> 2.0), so that won't be an issue. All I need is an email from you granting us >> permission. >> >> Thanks in advance, >> >> Nick Williams >> >
