On 22/02/17 10:54, Antonio Quartulli wrote:
> On Wed, Feb 22, 2017 at 09:30:39AM +0100, Steffan Karger wrote:
>> On 22-02-17 08:39, Gert Doering wrote:
>>> On Wed, Feb 22, 2017 at 02:21:35AM +0100, David Sommerseth wrote:
>>>>>> >From d97f526a2ddbf2abe60a64260601ebd742fc00cc Mon Sep 17 00:00:00 2001
>>>>>> From: "Simon (simix)" <via-trac>
>>>>> Do we have a policy how to handle patches with missing author info?
>>>> I see no reason at all why we should not give proper credit with full
>>>> name.  
>>> That was only half the question - of course I *want* to give full credits,
>>> but is "not having this information available & no SoB line" a reason
>>> for rejecting a patch?
>>> The patch in question is quite obvious, so this is not something to bring
>>> in the lawyers - more a matter of general policy.
>> Same here.
>> For this specific patch:  I asked the reporter on trac for full name and
>> email last night.  We can wait for a bit to see if he replies.
>> In general: what do we do when we don't get a full name and email, but
>> do want to apply the patch?  Wait forever?  Claim authorship (but refer
>> to the trac ticket in the commit msg)?  Apply anyway?  ...?
> IMHO somebody has to take ownership of every piece of code release under a 
> given
> license (just to avoid any future problem). So the patch should not be applied
> as is.
> Then ...
> in theory, you can't take ownership of somebody else' work, but nothing 
> prevents
> you from re-writing a "very similar" patch and sign it yourself. In particular
> if the author did not show any interest in pursuing this any further.


kind regards,

David Sommerseth
OpenVPN Technologies, Inc

Attachment: signature.asc
Description: OpenPGP digital signature

Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Openvpn-devel mailing list

Reply via email to