<div dir="ltr"><div><div><div>Hi Peter,<br><br></div>Nice idea, didn't know such a file existed. I can have a look at it today.<br><br></div>Cheers,<br><br></div>João<br></div><br><div class="gmail_quote">Em qua, 1 de abr de 2015 às 17:20, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>> escreveu:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Biopythoneers,<br>
<br>
Some of you may be aware of the GitHub convention of<br>
having a file name CONTRIBUTING (or CONTRIBUTING.md<br>
or I assume CONTRIBUTING.rst) in the root folder which gets<br>
shown to people automatically during a pull request etc:<br>
<br>
<a href="https://github.com/blog/1184-contributing-guidelines" target="_blank">https://github.com/blog/1184-<u></u>contributing-guidelines</a><br>
<br>
I think we should do this too, and can move/copy some<br>
of the content from the contributing chapter of the<br>
tutorial: Doc/Tutorial/chapter_<u></u>contributing.tex<br>
<br>
Assuming it works, I would prefer CONTRIBUTING.rst since<br>
we already use restructured text for Python docstrings etc.<br>
<br>
Given this is a plain text file, we could include it in the<br>
source code releases (via the MANIFEST.in file).<br>
<br>
Does this seem like a good idea? Does anyone want to<br>
write a draft (based on the LaTeX file)?<br>
<br>
Thanks,<br>
<br>
Peter<br>
<br>
P.S. At this point, is *.rst widely used enough that we<br>
could simply rename README to README.rst (and<br>
get rid of the symlink used to get it rendered on the<br>
main GitHub page?)<br>
______________________________<u></u>_________________<br>
Biopython-dev mailing list<br>
<a href="mailto:Biopython-dev@mailman.open-bio.org" target="_blank">Biopython-dev@mailman.open-<u></u>bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" target="_blank">http://mailman.open-bio.org/<u></u>mailman/listinfo/biopython-dev</a><br>
</blockquote></div>