On 7/18/12 9:35 PM, Becksfort, Jared wrote: > My employer requires that we retain copyright. OK, that requires a patch to the (single) NOTICE.txt file in the project root. > The code will also be released in other packages at some point.
That does not require any special notice. It is allowed by the Apache License. > If neither of those requires that I modify the NOTICE file, then I won't > bother. Phil > > Jared > ________________________________________ > From: Phil Steitz [phil.ste...@gmail.com] > Sent: Wednesday, July 18, 2012 11:11 PM > To: Commons Developers List > Subject: Re: [Math] NOTICE file > > On 7/18/12 9:02 PM, Becksfort, Jared wrote: >> That may have been a dumb question. I was thinking there were multiple >> NOTICE files, but apparently there is only one. I guess it can be part of >> the patch unless I hear otherwise from someone on the list. > In general, there is no need to update the NOTICE file when patches > are contributed. This is only used for contributions that have been > previously released in other forms / under other licenses or when > there are other specific reasons requiring that we provide a NOTICE > to users of our software. Why exactly do you think this is > necessary for the patches you are contributing? > > Phil >> Jared >> ________________________________________ >> From: Becksfort, Jared [jared.becksf...@stjude.org] >> Sent: Wednesday, July 18, 2012 10:50 PM >> To: Commons Developers List >> Subject: [Math] NOTICE file >> >> Hello, >> >> I am ready to submit code patches for a few tickets. I will email the >> patches to JIRA. They include unit tests. Do I just email the NOTICE file >> also, or do I have to include it in the patch file somehow? >> >> Thanks, >> Jared >> >> Email Disclaimer: www.stjude.org/emaildisclaimer >> Consultation Disclaimer: www.stjude.org/consultationdisclaimer >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org