Re: Pulling Patch

2011-02-06 Thread Damjan Jovanovic
On Sat, Feb 5, 2011 at 5:48 PM, Shachar Shemesh shac...@shemesh.biz wrote:

 On 05/02/11 00:24, James McKenzie wrote:

  Actually, the latest patch is what I don't want reused.  And no, you don't
 put it in the LGPL until it is committed, which I don't expect AJ to do
 anyway.

 However, I'm moving in a different direction since my Mac needs more
 repairs than I'm willing to spend money on.

 Besides, I've been a big enough pain that my existence here is unwarranted
 and unneeded.

  As anyone who attended the last WineConf probably already knows, you have
 my complete sympathies in that regard. I also doubt very much anyone would
 use your uncommitted patches against your will, so in that respect, you
 probably have nothing to worry about.

 That said, I believe your claim to the right to demand no use is wrong. It
 is my understanding that by submitting your patches to wine-patches, you
 have placed them under the LGPL, which is a non-revocable license. Again, in
 all likely hood, this is a purely hypothetical question.


If the LGPL is non-revocable, is code you've placed under it still
re-licensable, by you, under another license, as long as you don't revoke
the LGPL in the process?

ie. could I submit a piece of code to Wine and to another project?


Shachar

 --
 Shachar Shemesh
 Lingnu Open Source Consulting Ltd.
 http://www.lingnu.com




Damjan Jovanovic



Re: Pulling Patch

2011-02-06 Thread Shachar Shemesh

On 06/02/11 11:13, Damjan Jovanovic wrote:



On Sat, Feb 5, 2011 at 5:48 PM, Shachar Shemesh shac...@shemesh.biz 
mailto:shac...@shemesh.biz wrote:


On 05/02/11 00:24, James McKenzie wrote:

Actually, the latest patch is what I don't want reused.  And
no, you don't put it in the LGPL until it is committed, which
I don't expect AJ to do anyway.

However, I'm moving in a different direction since my Mac
needs more repairs than I'm willing to spend money on.

Besides, I've been a big enough pain that my existence here is
unwarranted and unneeded.

As anyone who attended the last WineConf probably already knows,
you have my complete sympathies in that regard. I also doubt very
much anyone would use your uncommitted patches against your will,
so in that respect, you probably have nothing to worry about.

That said, I believe your claim to the right to demand no use is
wrong. It is my understanding that by submitting your patches to
wine-patches, you have placed them under the LGPL, which is a
non-revocable license. Again, in all likely hood, this is a purely
hypothetical question.


If the LGPL is non-revocable, is code you've placed under it still 
re-licensable, by you, under another license, as long as you don't 
revoke the LGPL in the process?


ie. could I submit a piece of code to Wine and to another project?

First, IANAL.

You do not give up your copyright when you license code under the LGPL 
(or any other open source license). You merely provide a license (which 
is irrevocable). As such, the answer is yes. You can license code for 
which you own the complete copyrights under as many licenses of any type 
you wish to as many recipients as you wish, even if the licenses conflict.


That said, if the copyright is only for derivative work, then you also 
need a license for the original work. The only license you have for the 
original work in the case of Wine is the LGPL, and THAT LICENSE is 
conditioned upon the fact that you license your own code under the LGPL 
only. As such, you cannot license changes to wine under another license, 
despite the fact you have the copyright for it, as that would leave you 
without the license to create your derivative work in the first place.


So the real question is how independent your code is that you wish to 
submit. As long as you do not copy code from wine, you can submit the 
same change to as many open source projects as you like (even if their 
licenses are conflicting), and even use it for a proprietary project. 
If, however, the code requires Wine code in order to make sense, then 
you are bound by the LGPL and need to only use the code in a compliant way.


Shachar

--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com




Re: Pulling Patch

2011-02-05 Thread GOUJON Alexandre

On 02/04/2011 07:13 PM, James McKenzie wrote:

Since my Mac is dying I have decided to return to the Windows world.

It's your choice so I can't comment it but I bet you know what I think.

Please remember what you wrote to me (May, 2010) :
Don't give up on it, just take a break away from it, please.  The 
solution might just come to you while you are working on something 
else.  I've been working on a patch for two years and the 
implementation was completely wrong.  I will go back to it in about a 
month, and actually fix two missing functions rather than one.  This 
was the benefit of a mandatory break insisted upon by Alexandre.  He 
does not want me to touch it until early October. 
That's fine.  Just don't let this get you into a negative spirial.  
Alexandre and others have very good advice.



Please pull any and all patches.  I have envoked the right to 
copyright and none of my code can or will be used in Wine.
Life's hard, unfair and never goes as we thought. Does it worth the 
fight ? Yeah, of course !

Just as you told me, don't give up and have a break, have a K*t K*t.
Every mail and patch you sent is now archived and may be referred when 
relevant.

I'm sure you did great things and whatever you think, you're part of Wine.
We don't often say good job ! because it often imply something in 
return (mostly money) but we should.

It's always pleasant to see our work useful and that makes us proud.

So Good job !, have a nice day and take care.



Re: Pulling Patch

2011-02-05 Thread Shachar Shemesh

On 05/02/11 00:24, James McKenzie wrote:

Actually, the latest patch is what I don't want reused.  And no, you 
don't put it in the LGPL until it is committed, which I don't expect 
AJ to do anyway.


However, I'm moving in a different direction since my Mac needs more 
repairs than I'm willing to spend money on.


Besides, I've been a big enough pain that my existence here is 
unwarranted and unneeded.


As anyone who attended the last WineConf probably already knows, you 
have my complete sympathies in that regard. I also doubt very much 
anyone would use your uncommitted patches against your will, so in that 
respect, you probably have nothing to worry about.


That said, I believe your claim to the right to demand no use is wrong. 
It is my understanding that by submitting your patches to wine-patches, 
you have placed them under the LGPL, which is a non-revocable license. 
Again, in all likely hood, this is a purely hypothetical question.


Shachar

--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com





Pulling Patch

2011-02-04 Thread James McKenzie

Since my Mac is dying I have decided to return to the Windows world.

Please pull any and all patches.  I have envoked the right to copyright 
and none of my code can or will be used in Wine.


Thank you.

James McKenzie





re: Pulling Patch

2011-02-04 Thread Dan Kegel
James McKenzie wrote:
 Since my Mac is dying I have decided to return to the Windows world.

 Please pull any and all patches.  I have envoked the right to copyright
 and none of my code can or will be used in Wine.

Sorry to see you go, but... why would you want to prohibit people from
using your patches?

(I only see two typo changes committed:
http://source.winehq.org/git/wine.git/?a=searchh=HEADst=authors=James+McKenziesr=1
Presumably you don't mean those, since they were trivial comment changes.)

I guess you mean patches like
http://www.winehq.org/pipermail/wine-patches/2010-June/089537.html

When you sent those to wine-patches, weren't you placing them
under the LGPL?
- Dan




Re: Pulling Patch

2011-02-04 Thread James McKenzie

On 2/4/11 1:18 PM, Dan Kegel wrote:

James McKenzie wrote:

Since my Mac is dying I have decided to return to the Windows world.

Please pull any and all patches.  I have envoked the right to copyright
and none of my code can or will be used in Wine.

Sorry to see you go, but... why would you want to prohibit people from
using your patches?

(I only see two typo changes committed:
http://source.winehq.org/git/wine.git/?a=searchh=HEADst=authors=James+McKenziesr=1
Presumably you don't mean those, since they were trivial comment changes.)

I guess you mean patches like
http://www.winehq.org/pipermail/wine-patches/2010-June/089537.html

When you sent those to wine-patches, weren't you placing them
under the LGPL?
Actually, the latest patch is what I don't want reused.  And no, you 
don't put it in the LGPL until it is committed, which I don't expect AJ 
to do anyway.


However, I'm moving in a different direction since my Mac needs more 
repairs than I'm willing to spend money on.


Besides, I've been a big enough pain that my existence here is 
unwarranted and unneeded.


James McKenzie





Re: Pulling Patch

2011-02-04 Thread Dan Kegel
James McKenzie wrote:
 Actually, the latest patch is what I don't want reused.

This one?
http://www.winehq.org/pipermail/wine-patches/2011-January/098431.html

Why don't you want it reused?

 And no, you don't put it in the LGPL until it is committed,

That's interesting.  I always thought it was LGPL'd as soon as
it was sent to the patches list... maybe we should add a note to
the mailing list description clarifying this.

 Besides, I've been a big enough pain that my existence here is
 unwarranted and unneeded.

Sounds like you're sore from beating your head against the wall
trying to get patches in.  Sorry to hear it.   So long!
- Dan