[Biopython-dev] code credits

[Paul B]

I also agree completely. Adding value to the code deserves some form of credit, if desired by the contributor. I fixed a bit of code in a couple of the modules and received no credit... that made me a good bit less gung ho about contributing more.

--- On Thu, 12/17/09, Kyle Ellrott <kellrott at gmail.com> wrote:

From: Kyle Ellrott <kellrott at gmail.com>
Subject: Re: [Biopython-dev] code credits
To: "Marshall Hampton" <mhampton at d.umn.edu>
Cc: biopython-dev at lists.open-bio.org
Date: Thursday, December 17, 2009, 4:20 PM



I would agree with that.  Drawing from broad stereotypes, I would think that
a majority of contributors are academic and would be most interested in
adding things to their CV.  So acknowledgment would be of great value to
them at no real cost to the Biopython project.  Plus there's the old idea
that the more authors a paper has the more important it must be.

Kyle

I strongly encourage you to list anyone who has contributed a patch, no
> matter how small.  This has worked very well for the Sage project (
> www.sagemath.org) where credit is given to all contributors and reviewers
> (every patch must be reviewed by at least one other person).  For example
> see:
>
> http://groups.google.com/group/sage-announce/msg/bcf5591837068b5f
>
> Marshall Hampton
> Department of Mathematics and Statistics
> University of Minnesota, Duluth
>
>
_______________________________________________
Biopython-dev mailing list
Biopython-dev at lists.open-bio.org
http://lists.open-bio.org/mailman/listinfo/biopython-dev