Finalize contributors section

Author: dccowan

notebooks/contributing/formatting.md

@@ -178,7 +178,7 @@ import os
 
 Each section (or subsection) is constructed using a combination of Markdown and code cells. The structure and formatting of these are discussed below.
 
-### Cell 1: Header and Summary
+### Header and Summary
 
 Each section (or subsection) begins with a Markdown cell containing the header and a summary.
 Here, the contributor must:
@@ -249,26 +249,29 @@ source_field = gravity.sources.SourceField(receiver_list=receiver_list)
 survey = gravity.survey.Survey(source_field)
 ```
 
-### Comments on Plotting
+### Plotting Requirements
 
-The author is required to plot data, models, etc... When generating plot, please ensure:
+The contributor is required to plot data, models and other quantities that are best understood visually.
+Due to its widespread use, figures should be generated using [matplotlib](https://matplotlib.org/) package.
+When generating a figure, please ensure:
 
-* the figure renders at an appropriate size for display
-* the code used to generate the plot is compact
-* text and features within the plot are legible
+* the figure renders at an appropriate size when building the website
+* the code used to generate the figure is compact whenever possible
+* the text and features within the plot are legible
 
 
 ## Check Style of Notebooks
 
-We can check the code style of our notebooks using [`ruff`][ruff] and
-[`nbqa`][nbqa]. Simply run the following command to check the style of the
-notebooks:
+We can check and autoformat the code style within the notebooks using [`ruff`][ruff] and
+[`nbqa`][nbqa].
+
+To check the style of the notebooks:
 
 ```bash
 nbqa ruff notebooks
 ```
 
-And run this to autoformat them:
+To perform auto reformatting on the notebooks:
 
 ```bash
 nbqa ruff --fix notebooks

notebooks/contributing/pull_request.md

@@ -1,10 +1,12 @@
 GitHub Pull Request and Review Process
 ======================================
 
+Here, we describe the pull request and review process for bring new tutorial notebooks into the SimPEG user tutorials repository.
+
 Requirements Checklist
 ----------------------
 
-The following is a useful checklist for determining whether a new tutorial notebook follows our guidelines:
+The following is a useful checklist for determining whether the tutorial notebook has satisfied formatting and structure requirements:
 
 * **The introduction is complete:**
     * Title and author added to notebook
@@ -13,9 +15,48 @@ The following is a useful checklist for determining whether a new tutorial noteb
     * Summary paragraph describing the tutorial has been added
     * Learning objectives have been listed
     * Hyperlinks to other tutorial notebooks added if necessary
-* **For each section:**
-    * Short summary of what is being done
-    * Newly introduced functionality is explained or a link is provided to a relevant notebook
+* **For sections and subsections:**
+    * A header and short summary of what is being done
     * Links to API documentation added for all classes and functions that are used
-    * Data, models, etc... are plotted appropriately 
-	* Coding cells have been linted according to the [style guides](https://docs.simpeg.xyz/latest/content/getting_started/contributing/code-style.html).
+    * Newly introduced functionality is explained or links provided to relevant notebooks
+    * All figures are legible and rendered appropriately
+    * Coding cells have been linted according to the [style guides](https://docs.simpeg.xyz/latest/content/getting_started/contributing/code-style.html).
+
+Stages of a Pull Request
+------------------------
+
+When you are ready to submit your tutorial notebook review, you will make a 
+GitHub pull request (PR). If your pull request is not ready for a final review,
+but you require feedback, please mark it as a draft pull request. Once you
+feel the pull request is ready for a final review, you can convert the draft PR to
+an open PR by selecting the ``Ready for review`` button at the bottom of the page.
+
+Once a pull request is in ``open`` status and you are ready for review, please
+ping ``dccowan`` and ``santisoler`` in a github comment to
+request a review. At minimum for a PR to be eligible to merge, we look for
+
+- Structure and formatting requirements are observed.
+- The notebooks runs properly using the latest release of SimPEG.
+- All reviewer comments (if any) have been addressed.
+- A developer approves the PR.
+
+After all these steps are satisfied, a ``@simpeg/simpeg-admin`` will merge your
+pull request into the main branch (feel free to ping one of us on Github).
+
+This being said, all SimPEG developers and admins are essentially volunteers
+providing their time for the benefit of the community. This does mean that
+it might take some time for us to get your PR.
+
+Merging a Pull Request
+----------------------
+
+The ``@simpeg/simpeg-admin`` will merge a Pull Request to the `main` branch
+using the `Squash and Merge
+<https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits>`_
+strategy: all commits made to the PR branch will be _squashed_ to a single
+commit that will be added to `main`.
+
+SimPEG admins will ensure that the commit message is descriptive and
+comprehensive. Contributors can help by providing a descriptive and
+comprehensive PR description of the changes that were applied and the reasons
+behind them. This will be greatly appreciated.