Re: [libvirt] [PATCH] xenconfig: Remove references to my name and email

On Wed, May 9, 2018 at 3:24 PM, Michal Privoznik <mprivozn(a)redhat.com&gt; wrote: > On 05/09/2018 01:51 PM, David Kiarie wrote: > > On Wed, May 9, 2018 at 2:29 PM, David Kiarie <davidkiarie4(a)gmail.com&gt; > wrote: > > > >> > >> > >> On Wed, May 9, 2018 at 1:56 PM, John Ferlan <jferlan(a)redhat.com&gt; > 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 What SUSE resource ? > . > >>> > >>> > >> 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'm not going to get into authorship discussion, enough has been said. > But being org admin for libvirt since 2013 I've been dealing with both > Carol and Stephanie and frankly both of them are awesome and try/tried > their best. At every Mentor summit we have a discussion what went well > and what we can do better. They collect ideas and put them in practice. > > And despite your comments I think GSoC has been a great success for > libvirt too. We have students coming back, students who stay after > program ends and contribute afterwards, students whose code is still > used (I just used wireshark dissector the other day).

> Michal >