Woof! On Mon, 03 May 2010 15:50:20 -0400, George Niculae <[email protected]> wrote:
> --- On Sat, 5/1/10, George Niculae <[email protected]> wrote: > I've posted the patch - have a license question to ask, originally > raised by Woof!: I have copy-paste some Acegi code - see > SipxDigestProcessingFilter and SipxDaoAuthenticationProvider in the > provided patch - not sure if this will be in conflict with the license > (http://acegisecurity.org/acegi-security-tiger/license.html). Should we > at least keep the Acegi Copyright and mark sipxconfig changes only? Well, stripping off Acegi's copyrights and replacing them with Avaya's is certainly not nice. Those files have a pedigree, and they should be maintained as such. Some years from now I don't want to see some Avaya PHB sue Acegi for copyright violation as 'their' code (copyrighted Avaya) magically showed up in Acegi's code base. While WE all know it was the other way around, consider what could happen when Avaya hires Darl McBride to run the SCS project. Also, see section 4(b) of the Apache license: 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: ... (b) You must cause any modified files to carry prominent notices stating that You changed the files; and So please include the original copyrights, and please include the original file names and pointers to where they came from. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
