On Wed, May 9, 2018 at 2:29 PM, David Kiarie <davidkiar...@gmail.com> wrote:

>
>
> On Wed, May 9, 2018 at 1:56 PM, John Ferlan <jfer...@redhat.com> wrote:
>
>> [...]
>>
>>
>> >     > >> Suse copyright notice has been on this file since the day this
>> >     file got
>> >     > >> merged. To be honest, I did most of the original work so why
>> >     should Suse
>> >     > >> copyright appear here while me doesn't ?
>> >     > >>
>> >     > >
>> >     > > Contrary to the fact that most libvirt developers work for a
>> >     company, this
>> >     > > was mostly independent work.
>> >     > >
>> >     >
>> >     > And I totally don't have a problem with Suse copyrighting the file
>> >     but why
>> >     > can't I do the same ?
>> >
>>
>> Sooo... without GSOC and SUSE's support through their employee Jim
>> Fehlig would you have written that code on your own and tried to have it
>> included in libvirt? I would think SUSE has a stake in the written code
>> as their resource(s) were being used. Yes, they benefit from it, but so
>> did you as you can point to that code as being authored by you.
>>
>>
> I did this project in 2014 - to be honest, at the time, at least, most
> student were evaluated on merit.
>

GSoC is just a totally wasted project since Carols left :-(


>
>
>> I don't think anyone is indicating you didn't write the code. Using a
>> pseudonym is not allowed as part of the project's policy.
>>
>> >     You can have Copyright line on any file you made non-trivial
>> >     contributions
>> >     too. It is upto the person contributing patches to add Copyright
>> line if
>> >     they wish to. The Suse copyright is there simply because their patch
>> >     author chose to add it when they contributed to that file.
>> >
>> >     > Or, would you rather I use the pseudonym 'Oneko Ltd'  instead of
>> just
>> >     > 'Oneko' ?
>> >
>> >     Copyright lines need to use legal real names, or company name, not
>> >     pseudonyms.
>> >
>> >
>> > In which case you mean that if I write a patch copyrighting these file
>> > on the company name 'Oneko and sons'  you will merge that patch ?
>> >
>> >
>>
>> INAL, but altering a copyright after the fact to include a "new" company
>> name that was either not involved in the authorship of the code or not a
>> company at the time of authorship could result in legal issues. Does
>> SUSE decide/desire to release their copyright claim to the new company?
>> Does the new company stand to gain something by the copyright claim?
>>
>
> We don't have a new company here. We have an almost four year old cat.
>
>
>>
>> John
>>
>
>
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to