Fwd: [Orekit Developers] Distribution of orekit-python egg

2011-09-09 Thread Petrus Hyvönen
Hi JCC developers,

As this discussion could be of potential interest of others who makes python
modules using jcc I cross post it.

I am really not experienced in the licensing issues of open source, closed
source etc.

A JCC generated external java library .egg, do contain some JCC code, is
there something I need to do to ensure that the JCC license is fulfilled?

In my case the wrapped library is also in apache, so I guess it should not
be an issue to put the egg under apache?

Regads
/Petrus

-- Forwarded message --
From: Petrus Hyvönen petrus.hyvo...@gmail.com
Date: Fri, Sep 9, 2011 at 10:33 AM
Subject: Re: [Orekit Developers] Distribution of orekit-python egg
To: orekit-develop...@orekit.org


Hi Luc,

Good to hear, I think it is good with an easy-entry to the orekit through
python.

I really don't know much about the licensing stuff.

- My work in this process is rather minimal, issuing the right command line
parameters.
- The JCC tool that I use for wrapping is under apache 2.0 license as well.
http://pypi.python.org/pypi/JCC/
- orekit and common maths library are included in the egg. (common math
assumed to be under apache as well)

Microsoft compiler has been used in the process, but as I understand this
does not affect the licensing?

Please send me the paper and I can understand it better, I am not really
clear right now what the actual content of the authorization is about.

Regards
/Petrus




On Fri, Sep 9, 2011 at 10:04 AM, MAISONOBE Luc luc.maison...@c-s.fr wrote:

 Hi Petrus,

 Petrus Hyvönen petrus.hyvo...@gmail.com a écrit :


  Hi,

 This is mostly a legal/policy question,

 Would the license of orekit allow and would it be preferred that I create
 some python eggs (python installer packages) for orekit?


 The license allow it and it would be interesting to do.



  I am using JCC to
 wrap orekit java library so it is accessible from standard python. All
 instructions needed are on the orekit wiki.

 After an update to python 2.7 and rebuilding of the wrapping, I realized
 that there is some caveats involved on at least windows operating system
 (such that you need microsoft visual C installed) to create the wrapping,
 but not to run it.  When built I can easily make the eggs that could be
 put
 on the orekit or other webpage and easily installed, without the need of
 that compiler etc.


 If you want it and if you choose to have all additional wrapping code and
 packaging distributed under the sames terms as Orekit, i.e. the Apache 2
 Software License, then yes, we could host them here in the main Orekit site.
 You would of course be credited for that. Before we can really distribute
 your work, we would ask you to sign a Individual Contributor License
 Agreement which basically say you authorize us to distribute what you did.
 We follow exactly the same process as the Apache Software Foundation for
 that. I can send you the template of the paper.

 Thanks
 Luc



 Let me know what you think
 /Petrus




 --**--**
 This message was sent using IMP, the Internet Messaging Program.





-- 
_
Petrus Hyvönen, Uppsala, Sweden
Mobile Phone/SMS:+46 73 803 19 00



-- 
_
Petrus Hyvönen, Uppsala, Sweden
Mobile Phone/SMS:+46 73 803 19 00


Re: Fwd: [Orekit Developers] Distribution of orekit-python egg

2011-09-09 Thread Andi Vajda


On Fri, 9 Sep 2011, Petrus Hyvönen wrote:


As this discussion could be of potential interest of others who makes python
modules using jcc I cross post it.

I am really not experienced in the licensing issues of open source, closed
source etc.

A JCC generated external java library .egg, do contain some JCC code, is
there something I need to do to ensure that the JCC license is fulfilled?

In my case the wrapped library is also in apache, so I guess it should not
be an issue to put the egg under apache?


As the licenses are the same can't imagine an issue here.

In the LICENSE file - or is that the NOTICE file - of your distribution, you 
should include a copy of the Apache2 license for JCC.


That being said, I am not a lawyer...

Giving attribution to Apache JCC is always appreciated, though.

Thanks !

Andi..



Regads
/Petrus

-- Forwarded message --
From: Petrus Hyvönen petrus.hyvo...@gmail.com
Date: Fri, Sep 9, 2011 at 10:33 AM
Subject: Re: [Orekit Developers] Distribution of orekit-python egg
To: orekit-develop...@orekit.org


Hi Luc,

Good to hear, I think it is good with an easy-entry to the orekit through
python.

I really don't know much about the licensing stuff.

- My work in this process is rather minimal, issuing the right command line
parameters.
- The JCC tool that I use for wrapping is under apache 2.0 license as well.
http://pypi.python.org/pypi/JCC/
- orekit and common maths library are included in the egg. (common math
assumed to be under apache as well)

Microsoft compiler has been used in the process, but as I understand this
does not affect the licensing?

Please send me the paper and I can understand it better, I am not really
clear right now what the actual content of the authorization is about.

Regards
/Petrus




On Fri, Sep 9, 2011 at 10:04 AM, MAISONOBE Luc luc.maison...@c-s.fr wrote:


Hi Petrus,

Petrus Hyvönen petrus.hyvo...@gmail.com a écrit :


 Hi,


This is mostly a legal/policy question,

Would the license of orekit allow and would it be preferred that I create
some python eggs (python installer packages) for orekit?



The license allow it and it would be interesting to do.



 I am using JCC to

wrap orekit java library so it is accessible from standard python. All
instructions needed are on the orekit wiki.

After an update to python 2.7 and rebuilding of the wrapping, I realized
that there is some caveats involved on at least windows operating system
(such that you need microsoft visual C installed) to create the wrapping,
but not to run it.  When built I can easily make the eggs that could be
put
on the orekit or other webpage and easily installed, without the need of
that compiler etc.



If you want it and if you choose to have all additional wrapping code and
packaging distributed under the sames terms as Orekit, i.e. the Apache 2
Software License, then yes, we could host them here in the main Orekit site.
You would of course be credited for that. Before we can really distribute
your work, we would ask you to sign a Individual Contributor License
Agreement which basically say you authorize us to distribute what you did.
We follow exactly the same process as the Apache Software Foundation for
that. I can send you the template of the paper.

Thanks
Luc




Let me know what you think
/Petrus





--**--**
This message was sent using IMP, the Internet Messaging Program.






--
_
Petrus Hyvönen, Uppsala, Sweden
Mobile Phone/SMS:+46 73 803 19 00



--
_
Petrus Hyvönen, Uppsala, Sweden
Mobile Phone/SMS:+46 73 803 19 00