[drmaa-wg] Re: Schedule::DRMAAc, and a DRMAA python module

[Tim Harsch]

Hi Enrico,
    This is most excellent!  Thank you.  I've been hoping someone would do 
exactly what you've done here.  I'm copying the DRMAA working group because 
I think they too would be very excited to see that DRMAA now has a Python 
binding.

    To the group I'd like to ask if anyone knows more about the GPL such 
that they could advise on how to stay true to its form...  Does anyone know 
what Enrico must do to meeat all the requirements he needs to in order to 
release his code?   I think maybe he has, because all he need do is to 
include a copy of the license agreement and reference the original work... 
but I'll need to contact my employer resources, regarding the licensing.  I 
know that by releasing under the GPL you are entitled to re-release with 
modifications, but I think there may be some specific legal mumbo-jumbo that 
has to be included to satisfy University of California.  I'll find out for 
you soonest.

Thanks again for doing this Enrico, it is very exciting for DRMAA to get 
Python support!

PS  I've not included Enrico's code attachment, for anyone wishing to view 
it please ask him directly...

----- Original Message ----- 
From: <enrico.sirola at statpro.com>
To: <harsch1 at llnl.gov>
Sent: Friday, October 21, 2005 2:38 AM
Subject: Schedule::DRMAAc, and a DRMAA python module


> Hello Tim,
> I wrote a python module for the DRMAA library starting from your SWIG
> file I would contribute to the open sourcecommunity. Since I started
> from your swig file, the module will be released under the GPLv2 and
> I'd like to be sure that you agrees on the copyright notices I wrote.
> If you can take a look at the package I'd appreciate it a lot. If
> agree with license, credits etc please let me know it so I will post
> it somewhere. The whole stuff is a few kilobytes only, to I attached
> it here.
> Thanks in advance,
> enrico
>
>


--------------------------------------------------------------------------------


>
>
> -- 
> Enrico Sirola <enrico.sirola at statpro.com>
>
>