[core-workflow] Voting on possible subdomains for the devguide

[Ned Deily]

On Apr 11, 2017, at 18:12, Brett Cannon <brett at python.org> wrote:
> From my perspective there are a few reasons for thinking about moving. One is that low-maintenance isn't no-maintenance. Anything that helps take some load off the infrastructure team is a good thing in my opinion (especially when the PEPs and devguides are "unique snowflakes" in all of this as they are not built like the rest of docs.python.org). Two, getting changes to these machines isn't always easy or fast. As I pointed out to Elvis, we don't have Pygments installed so we can get source highlighting in PEPs and the PR to fix it has been sitting there for quite a while.

There are a number of people who could do that.  Perhaps pinging the issue would help?

> And because the infrastructure is custom not many people even know where to make changes to change things like what dependencies are installed are on the machines (I mean how many people even knew there are three machines before this email?). Three,  updates to any of these docs only happens a couple of times a day instead of instantly. Obviously not always a big deal, but for the PEPs it can be annoying when you want to email out the link to the rendered version and you can't simply because the cron job has not run yet.

Most of the scripting is on github:

https://github.com/python/docsbuild-scripts
https://github.com/python/pythondotorg

And any of the infra team can change the cron jobs to run more frequently :)

> So even if we can't get rid of docs.python.org and we don't move that over to RTD, at least getting python.org/dev/peps and docs.python.org/devguide to no longer be odd-ball infrastructure points is still a win in my book.

OK, I don't have a big problem with moving the devguide and/or the PEPs, though I do think Guido has a point about being mindful of adding burden to the RTD folks (although, yes, that's probably not a big deal for the devguide and probably not for the PEPs either).  And I don't think moving them is going to make any significant difference in the workload of the Python infra team as long as we do not outsource the main python.org web site components.  My big concern would be with trying to move the rest of the docs.  That is much more complicated and has implications for the release process and backward compatibility wrt URLs etc etc.  (Release managers handle a lot of the complexities of this behind the scenes.)  I would urge that we not make that (e.g. moving the rest of the docs) a goal for now.
  
--
  Ned Deily
  nad at python.org -- []