[docs] How best to submit a change?

Carol Willing willingc at willingconsulting.com
Sun Jul 3 14:05:51 EDT 2016


On Jul 3 2016, at 6:38 am, Jim Belton <jim.belton at gmail.com> wrote:  

> Hi all:  


> I'm more than happy to hack some restructured text. How best to submit a
patch to a doc? I'm not going to take the time to improve unless I know how to
get my change included. I'd be hacking the 2.7 branch, since that's the
version I seem to be working in. Hopefully, 3 will start getting more traction
in real world dev.ops. environments soon.  


> Thanks,  


> Jim.  


Hi Jim,


The Python Dev Guide (https://docs.python.org/devguide/#full-table-of-
contents) would be a good resource to walk you through how to submit a patch
to the CPython docs:


  * Section 3: Life cycle of a patch
  * Section 6: Helping with documentation
  * Section 7: Documenting Python


Thanks for your interest in submitting a doc patch. We're looking forward to
contributions from you.





Carol Willing


Research Software Engineer

Project Jupyter @ Cal Poly SLO


Director, Python Software Foundation


_Signature strengths_

_Empathy - Relator - Ideation - Strategic - Learner_


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20160703/3fe43a1a/attachment.html>

More information about the docs mailing list