On Mon, Aug 29, 2016 at 05:41:10PM +0100, Emil Velikov wrote:
> Hi all,
>
> On 24 August 2016 at 06:46, Vladimir Zapolskiy
> <vladimir_zapolskiy@xxxxxxxxxx> wrote:
>
> > MODULE_AUTHOR("Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>");
> > MODULE_AUTHOR("Andy Yan <andy.yan@xxxxxxxxxxxxxx>");
> > MODULE_AUTHOR("Yakir Yang <ykk@xxxxxxxxxxxxxx>");
> > +MODULE_AUTHOR("Vladimir Zapolskiy <vladimir_zapolskiy@xxxxxxxxxx>");
> Don't meant to start a flame-war or alike but to educate myself:
> Where does one draw the line about adding new author(s) of said
> module/subsystem ?
>
> Afaict this is the most common (?) driver in DRM where the list has
> grown over time. Should we do the same with others ?
... and I'm responsible for just over half the commits in the mainline
kernel and I haven't added myself. I generally only add myself if I'm
creating new code or been involved in adding new code, I don't add if
I'm merely modifying existing code unless I've replaced a large
quantity of the code. I think the question people need to ask is:
"Have I contributed a significant set of changes to be able to claim
shared authorship of that code?"
You wouldn't claim authorship of a 500 page book if you suggested a
few edits here and there.
Looking at co-authorship in google, I came across:
http://www.southernfriedscience.com/to-co-author-or-not-to-co-author/
which has an interesting list of points on this subject, although more
biased to research papers, which is where this problem normally arises.
That seems to back up my idea of "significant contribution" not just
a few minor changes.
The question then becomes... what is a significant contribution. :)
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
