diff --git a/pep-0581.rst b/pep-0581.rst
index 091af8275..04da9fff7 100644
--- a/pep-0581.rst
+++ b/pep-0581.rst
@@ -161,9 +161,24 @@ The current CLA process itself is not ideal. Currently, contributors to
 devguide, peps, and core-workflow need to sign a CLA, and it requires a bpo
 account. A bpo account should not be required for those projects.
 
-Currently, the CLA process requires personnel to manually check the records.
-Question: Will it be possible to completely automate the CLA process, so
-it does not require human intervention?
+There is an ongoing effort to start using our own instance of CLA assistant
+instead of the current CLA process in place. Discussion about this has been
+started in `core-workflow mailing list <https://mail.python.org/archives/list/core-workflow@python.org/thread/JBV3XJVD2DLDX5DY7TZEA6CO5YPNHJ2C/>`_ as
+well as on `Discourse <https://discuss.python.org/t/using-cla-assistant-for-python/990>`_.
+
+
+Create Bug Triage Team on GitHub
+--------------------------------
+
+The bug triagers on bpo are valuable to the core Python workflow, and we
+definitely would need even more help with triaging issues on GitHub.
+
+It has been `proposed on Discourse <https://discuss.python.org/t/proposal-create-bug-triage-team-on-github/992/5>`_
+for us to create a "bug triage" team on GitHub to help with closing issues,
+notifying the appropriate parties, as well as applying labels to issues
+and pull requests. We can grant the "write" permission to the "bug triage"
+team, while limiting merging pull requests to "CPython core developer" team
+on GitHub.
 
 Create labels for issue triage
 ------------------------------
@@ -184,6 +199,9 @@ We will create the corresponding labels::
 
 In addition, we'll create a ``needs triage`` label.
 
+The final "labels" to be created can be decided at a later time when
+it is time to start switching to GitHub issues.
+
 Create issue templates
 ----------------------