Add links to core-workflow issue tracker (#154)

pep-0512.txt

@@ -433,6 +433,9 @@ decision compared to the rejected approaches outlined in the
 seems to have the right balance of flexibility and potential tooling
 out of the various options while solving the motivating problem.
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/6.
+
 
 Handling Misc/ACKS
 ''''''''''''''''''
@@ -452,6 +455,9 @@ The script should also generate a list of all people who contributed
 since the last execution. This will allow having a list of those who
 contributed to a specific release so they can be explicitly thanked.
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/7.
+
 
 Create https://git.python.org
 '''''''''''''''''''''''''''''
@@ -491,6 +497,9 @@ The bot would then generate cherry-pick pull requests for each label
 and remove the labels as the pull requests are created (this allows
 for easy detection when automatic cherry-picking failed).
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/8.
+
 
 Pull request commit queue
 ''''''''''''''''''''''''''
@@ -525,6 +534,9 @@ request can be made in IRC to try a patch from
 bugs.python.org [#b.p.o]_. The results can be viewed at
 https://ci.centos.org/job/cPython-build-patch/ .
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/1.
+
 
 Test coverage report
 ''''''''''''''''''''
@@ -537,6 +549,9 @@ There are a couple pre-existing services that provide free test
 coverage for open source projects. In the end, Codecov [#codecov]_ was
 chosen as the best option.
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/2.
+
 
 Notifying issues of pull request comments
 '''''''''''''''''''''''''''''''''''''''''
@@ -582,6 +597,9 @@ as then the site can have an unofficial mirror on
 `Read the Docs <https://readthedocs.org/>`_, e.g.
 http://cpython-devguide.readthedocs.io/.
 
+Work for this is being tracked at
+https://github.com/python/core-workflow/issues/9.
+
 
 Link web content back to files that it is generated from
 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''
@@ -592,6 +610,9 @@ page which points back to the file on GitHub [#github]_ that stores
 the content of the page. That would allow for quick pull requests to
 fix simple things such as spelling mistakes.
 
+Work for this is being tracked at
+http://bugs.python.org/issue28929.
+
 
 Splitting out parts of the documentation into their own repositories
 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
@@ -645,6 +666,9 @@ developers. This work doesn't even necessarily require GitHub
 integration as long as the committer field in all git commits is
 filled in properly.
 
+Work is being tracked at
+https://github.com/python/core-workflow/issues/10.
+
 
 Status
 ======