[Python-checkins] peps: Add some open issues.

[barry.warsaw]

https://hg.python.org/peps/rev/2fb211ea5cb1
changeset:   6104:2fb211ea5cb1
user:        Barry Warsaw <barry at python.org>
date:        Wed Sep 30 16:32:56 2015 -0400
summary:
  Add some open issues.

files:
  pep-0507.txt |  28 ++++++++++++++++++++++++++++
  1 files changed, 28 insertions(+), 0 deletions(-)


diff --git a/pep-0507.txt b/pep-0507.txt
--- a/pep-0507.txt
+++ b/pep-0507.txt
@@ -278,6 +278,34 @@
 possible to submit and commit changes.
 
 
+Open issues
+===========
+
+* What level of hosted support will GitLab offer?  The PEP author has been in
+  contact with the GitLab CEO, with positive interest on their part.  The
+  details of the hosting offer would have to be discussed.
+
+* What happens to Roundup and do we switch to the GitLab issue tracker?
+  Currently, this PEP is *not* suggesting we move from Roundup to GitLab
+  issues.  We have way too much invested in Roundup right now and migrating
+  the data would be a huge effort.  GitLab does support webhooks, so we will
+  probably want to use webhooks to integrate merges and other events with
+  updates to Roundup (e.g. to include pointers to commits, close issues,
+  etc. similar to what is currently done).
+
+* What happens to wiki.python.org?  Nothing!  While GitLab does support wikis
+  in repositories, there's no reason for us to migration our Moin wikis.
+
+* What happens to the existing GitHub mirrors?  We'd probably want to
+  regenerate them once the official upstream branches are natively hosted in
+  Git.  This may change commit ids, but after that, it should be easy to
+  mirror the official Git branches and repositories far and wide.
+
+* Where would the GitLab instance live?  Physically, in whatever hosting
+  provider GitLab chooses.  We would point gitlab.python.org (or
+  git.python.org?) to this host.
+
+
 References
 ==========
 

-- 
Repository URL: https://hg.python.org/peps