<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<span>Ned Deily wrote:</span><br>
<blockquote cite="mid:0CE8ACDB-26F8-4596-99C0-D007145BE1C2@python.org"
type="cite">
<pre wrap="">On Apr 11, 2017, at 18:29, Carol Willing <a class="moz-txt-link-rfc2396E" href="mailto:willingc@willingconsulting.com"><willingc@willingconsulting.com></a> wrote:
</pre>
<blockquote type="cite"><pre wrap="">While RTD may or may not be right for docs.python.org, I think it's worth looking at least mirroring the CPython docs on RTD. An added benefit for hosting on RTD is that there is lots of documentation around for using Sphinx/RTD which provides an opportunity for attracting more contributors to documentation and community management.
</pre></blockquote>
<pre wrap=""><!---->
I guess I don't see the value of maintaining a RTD mirror for CPython docs as long as we are also serving the documents from docs.python.org, something which I think we need to continue to do. </pre>
</blockquote>
<br>
I'm not advocating moving to the current docs right now, but I do
believe there is value in having some form of the current master 3 docs
on RTD. The value comes from these benefits:<br>
<br>
- a place to begin simplifying the documentation workflow for both
maintainability (bus factor) and attracting a wider group of
contributors and reviewers <br>
- making the documentation development and review process simpler would
encourage people who are good writers and educators to contribute more
to the "how to use" sections of the docs<br>
<br>
While the reference sections of the docs are excellent, the tutorials
and "how to" sections could be more community focused.<br>
<br>
I'm throwing it out as a suggestion for improvement, not a distraction
or extra work. I'm happy to keep the status quo too.<br>
<br>
<blockquote cite="mid:0CE8ACDB-26F8-4596-99C0-D007145BE1C2@python.org"
type="cite">
<pre wrap="">There is a fair amount of work that goes on behind the scenes with each release for maintaining the docs, not all of which is included in the docs source itself, things like updating symlinks and redirects and what not. Adding the mirror seems like adding extra work for no gain. And how would Sphinx documentation not also apply to the current CPython docs as served on docs.python.org?
--
Ned Deily
<a class="moz-txt-link-abbreviated" href="mailto:nad@python.org">nad@python.org</a> -- []
_______________________________________________
core-workflow mailing list
<a class="moz-txt-link-abbreviated" href="mailto:core-workflow@python.org">core-workflow@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/core-workflow">https://mail.python.org/mailman/listinfo/core-workflow</a>
This list is governed by the PSF Code of Conduct: <a class="moz-txt-link-freetext" href="https://www.python.org/psf/codeofconduct">https://www.python.org/psf/codeofconduct</a>
</pre>
</blockquote>
<br>
</body></html>