pygccxml-development

[pygccxml-development] [release] setup.py need to be updated

[Roman Y. <rom...@gm...>]

Hi. Matthias and Allen, I hope I will be ready to release Py++ next week.
I would like to distribute contrib package too. There is small amount
of work that should
be done:

1. To update setup.py script: to add your packages and generate documentation.
2. License. Not all files/directories contains license.

Can you fix those issues?

Thanks.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

Re: [pygccxml-development] [release] setup.py need to be updated

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> Hi. Matthias and Allen, I hope I will be ready to release Py++ next week.
> I would like to distribute contrib package too. There is small amount
> of work that should
> be done:
> 
> 1. To update setup.py script: to add your packages and generate documentation.

I did that already when I was adding the contrib directory to the 
repository (actually it's not the setup.py script that I had to modify 
but the MANIFEST.in file).
So when you create a source distribution the contrib directory should 
already be part of it.

> 2. License. Not all files/directories contains license.

I added a short license information to pypp_api (but I don't think we 
have to be too picky here. I'm sure that every contributor who adds 
something to contrib doesn't have any objections when you redistribute 
that code with the Py++ sources. I couldn't imagine that someone is just 
adding code so that he can sue you as soon as you release that code... ;)

- Matthias -

Re: [pygccxml-development] [release] setup.py need to be updated

[Roman Y. <rom...@gm...>]

On 8/23/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > Hi. Matthias and Allen, I hope I will be ready to release Py++ next week.
> > I would like to distribute contrib package too. There is small amount
> > of work that should
> > be done:
> >
> > 1. To update setup.py script: to add your packages and generate documentation.
>
> I did that already when I was adding the contrib directory to the
> repository (actually it's not the setup.py script that I had to modify
> but the MANIFEST.in file).
> So when you create a source distribution the contrib directory should
> already be part of it.

I see, what about documentation? Don't you want to integrate to
setup.py script to build
pypp_api documentation?

> > 2. License. Not all files/directories contains license.
>
> I added a short license information to pypp_api (but I don't think we
> have to be too picky here. I'm sure that every contributor who adds
> something to contrib doesn't have any objections when you redistribute
> that code with the Py++ sources. I couldn't imagine that someone is just
> adding code so that he can sue you as soon as you release that code... ;)

I thought about different situation: there are people and\or
organization, that just can
not use the code, if license is not clear or it is not XYZ. This is
the only reason.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

Re: [pygccxml-development] [release] setup.py need to be updated

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> I see, what about documentation? Don't you want to integrate to
> setup.py script to build pypp_api documentation?

Actually, I'm against this as I think Py++ shouldn't be dependent on 
code in "contrib". After all, these are "only" user contributions that 
are not officially supported. And if something proves to be useful for 
every Py++ user it should be moved out of contrib and made part of the 
official Py++ package.
But as long as something has the "contrib" status it's the contributor 
who's responsible for the code and who has to provide enough information 
so that others can use the package (having said that I've just added a 
readme to pypp_api ;) And the main documentation for pypp_api is now in 
the wiki anyway...

>> > 2. License. Not all files/directories contains license.
>>
>> I added a short license information to pypp_api (but I don't think we
>> have to be too picky here. I'm sure that every contributor who adds
>> something to contrib doesn't have any objections when you redistribute
>> that code with the Py++ sources. I couldn't imagine that someone is just
>> adding code so that he can sue you as soon as you release that code... ;)
> 
> I thought about different situation: there are people and\or
> organization, that just can
> not use the code, if license is not clear or it is not XYZ. This is
> the only reason.

It depends on what exactly you mean with "use the code". Note that a lot 
of Open Source licenses only deal with the distribution and modification 
of software and not its mere usage. The following sentence is taken from 
the GPL:

"Activities other than copying, distribution and modification are not 
covered by this License; they are outside its scope."

So if a company only wants to make use of a GPL licensed software (e.g. 
a 3D modeler to create models for a commercial game) and do not have to 
distribute this software with their own commercial product, then it is 
my understanding that they may certainly do so without infringing anything.

In our case it means that it doesn't matter whether some code in contrib 
has a license like the GPL or not if a particular user only wants to 
"use" that code and only wants to distribute the output of Py++ and not 
Py++ itself.

(but of course, I'm no lawyer so don't count on the above if you're in 
court... ;)

- Matthias -

Re: [pygccxml-development] [release] setup.py need to be updated

[Matthias B. <ba...@ir...>]

Oops, I hit the send button too early...

> "Activities other than copying, distribution and modification are not 
> covered by this License; they are outside its scope."

Maybe I should also have quoted the subsequent sentence:

"The act of running the Program is not restricted, [...]"

Now I wonder if it would have been restricted if that sentence was 
missing...?

- Matthias -

Re: [pygccxml-development] [release] setup.py need to be updated

[Roman Y. <rom...@gm...>]

On 8/23/06, Matthias Baas <ba...@ir...> wrote:
> Roman Yakovenko wrote:
> > I see, what about documentation? Don't you want to integrate to
> > setup.py script to build pypp_api documentation?
>
> Actually, I'm against this as I think Py++ shouldn't be dependent on
> code in "contrib". After all, these are "only" user contributions that
> are not officially supported. And if something proves to be useful for
> every Py++ user it should be moved out of contrib and made part of the
> official Py++ package.

:-) I hope we will make pypp_api part of the Py++.

> It depends on what exactly you mean with "use the code". Note that a lot
> of Open Source licenses only deal with the distribution and modification
> of software and not its mere usage. The following sentence is taken from
> the GPL:
>
> "Activities other than copying, distribution and modification are not
> covered by this License; they are outside its scope."
>
> So if a company only wants to make use of a GPL licensed software (e.g.
> a 3D modeler to create models for a commercial game) and do not have to
> distribute this software with their own commercial product, then it is
> my understanding that they may certainly do so without infringing anything.
>
> In our case it means that it doesn't matter whether some code in contrib
> has a license like the GPL or not if a particular user only wants to
> "use" that code and only wants to distribute the output of Py++ and not
> Py++ itself.
>
> (but of course, I'm no lawyer so don't count on the above if you're in
> court... ;)

Thanks for the explanation. I am not a lawyer too. In the company I
work for, if the
license is not clear(  missing  ) we don't use( touch ) this software.
This is the case I thought to solve.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

Re: [pygccxml-development] [release] setup.py need to be updated

[Allen B. <al...@vr...>]

Roman Yakovenko wrote:

>Hi. Matthias and Allen, I hope I will be ready to release Py++ next week.
>I would like to distribute contrib package too. There is small amount
>of work that should
>be done:
>
>1. To update setup.py script: to add your packages and generate documentation.
>2. License. Not all files/directories contains license.
>
>Can you fix those issues?
>
>Thanks.
>
>  
>
I don't think I have anything in there right now.  (goodies is 
definitely *not* ready for release but it does have licenses in the files)

-Allen