[drupal-devel] Licence issues using GPL'ed SquirrelMail code in mailhandler.module?

K B kbahey at gmail.com
Sun May 22 16:00:34 UTC 2005

The other issue is long term maintainability.

Their code will change, and we might do the same to what we borrowed from them.

So, do we have to do periodic sync ups? Or do we not change anything
and just get an update from them every now and then?

Whichever way we choose, we have to understand the implications of it long term.

On 5/22/05, Gordon Heydon <gordon at heydon.com.au> wrote:
> Hello,
> On Sun, 2005-05-22 at 13:23 +0100, Mark Leicester wrote:
> > I'm making improvements to the mailhandler (and fixing the
> > drupal_special_chars problem by replacing with check_plain).
> > SquirrelMail already implements a very thorough URL parser, attachment
> > handler, and mail re-wrapper. SquirrelMail is GNU GPL, so I'm wondering
> > if I can re-use that code rather than reinvent. What are the licence
> > implications? Do we simply need to credit the SquirrelMail project and
> > redistribute the licence intact?
> You should be able to, they are both squirrel mail and drupal are gpl,
> and you will be compiling with the terms of the licence in that you have
> to distribute the source with the product.
> The only thing I am not sure about but I think will be a problem is that
> you have to keep the copyright messages in tack, but because you are
> only taking snippets you may need to transfer the copyright messages.
> Gordon

More information about the drupal-devel mailing list