[Biopython-dev] code credits
Marshall Hampton
mhampton at d.umn.edu
Thu Dec 17 18:42:33 UTC 2009
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
> Message: 1
> Date: Wed, 16 Dec 2009 22:43:16 +0000
> From: Peter <biopython at maubp.freeserve.co.uk>
> Subject: Re: [Biopython-dev] Code freeze for Biopython 1.53
> To: Brad Chapman <chapmanb at 50mail.com>, biopython-dev at biopython.org
> Message-ID:
> <320fb6e00912161443q30f82120of1c98b073136c3f6 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Brad wrote:
>>> Brad - could you run a sanity test before uploading to pypi?
>>
>> Looks good to me, and uploaded to pypi.
>
> Great, thank you.
>
>>> Draft text below - any comments?
>>
>> As a thought for next time, what do you think about adding the
>> names of people who have worked on the items mentioned in the
>> release? This would give a bit more public recognition for the
>> contributions, especially to people who only look at the release
>> notes and not mailing list traffic.
>
> Its too late for the emails and the source code bundles, but
> the nice thing about the NEWS file (in the repository) and
> the OBF news server is we can update them even now.
>
> Of course, quite where to draw the line is debatable - a simple
> patch probably doesn't warrant it (or does it?), but solving a
> more complex bug or adding some new functionality does.
> If any existing core developers want more "recognition" we
> can do that too.
>
> For example, Kyle, would you have like to be named with
> regards to the Jython work? I almost put you in anyway,
> but in the end just mentioned it on twitter:
> http://twitter.com/Biopython/statuses/6502469425
>
> Another idea to showcase new features would be for the
> author(s) to prepare a (credited) blog post with some
> examples (to put on our news server). I have already done
> a few like this, and think it would also be a good thing in
> general.
>
> Peter
More information about the Biopython-dev
mailing list