Merge pull request #6967 from jupyterlab/Explain-Lockbot-in-contributing-guidelines

Updated CONTRIBUTING.MD

CONTRIBUTING.md

@@ -44,10 +44,17 @@ a keyboard shortcut or automatically on save.
 ## Submitting a Pull Request Contribution
 
 Generally, an issue should be opened describing a piece of proposed work and the
-issues it solves before a pull request is opened. This lets community members
-participate in the design discussion, makes others aware of work being done, and
-sets the stage for a fruitful community interaction. A pull request should
-reference the issue it is addressing.
+issues it solves before a pull request is opened. 
+
+### Issue Management
+Opening an issue lets community members participate in the design discussion, 
+makes others aware of work being done, and sets the stage for a fruitful community 
+interaction. A pull request should reference the issue it is addressing. Once the 
+pull request is merged, the issue related to it will also be closed. If there is 
+additional discussion around implemementation the issue may be re-opened. Once 30 days
+have passed with no additional discussion, the [lock bot](https://github.com/apps/lock) will lock the issue. If
+additional discussion is desired, or if the pull request doesn't fully address the
+locked issue, please open a new issue referencing the locked issue.
 
 ### Tag Issues with Labels
 

README.md

@@ -152,7 +152,7 @@ To be listed, please submit a pull request with your information.
 
 We encourage you to ask questions on the [Discourse forum](https://discourse.jupyter.org/c/jupyterlab). A question answered there can become a useful resource for others.
 
-Please use the [GitHub issues page](https://github.com/jupyterlab/jupyterlab/issues) to provide feedback or submit a bug report.
+Please use the [GitHub issues page](https://github.com/jupyterlab/jupyterlab/issues) to provide feedback or submit a bug report. To keep resolved issues self-contained, the [lock bot](https://github.com/apps/lock) will lock closed issues as resolved after a period of inactivity. If related discussion is still needed after an issue is locked, please open a new issue and reference the old issue.
 
 ### Weekly Dev Meeting