APE 1 Modification: Added relevant review periods and clarified start of final review process

APE1.rst

@@ -18,6 +18,7 @@ revised-by:
 * Lia Corrales, Thomas Robitaille, Erik Tollerud - 2021 February 26 - Added APE modification process
 * Pey Lian Lim - 2024 February 5 - Added APE numbering process
 * Thomas Robitaille, Pey Lian Lim - 2025 Oct 27 - Modify APE process to merge APEs that are in the discussion stage
+* Kyle Westfall - 2026 Jan 20 - Added relevant review periods and clarified start of final review process.
 
 Abstract
 --------
@@ -111,10 +112,13 @@ the `@astropy/ape-editor-team <https://github.com/orgs/astropy/teams/ape-editor-
 should be mentioned in the pull request, and
 the APE will then undergo an editorial review which focuses on wording,
 spelling, grammar, and clarity, but does not focus on the substance of the APE.
-The editorial process ideally should not take longer than a month.
+**Ideally, the editorial process should not take longer than a month.**
 Once the APE editors are happy with the APE, they will:
 
-#. Make sure the APE has a status of "Discussion".
+#. Make sure the APE has a status of "Discussion".  In the status section of the
+   APE header, also include the earliest date when the discussion period can end
+   (at least two weeks from when the email is sent to astropy-dev that starts
+   the discussion period, see below).
 
 #. If additional files are attached with the APE in the PR, make sure the
    file sizes are reasonable.
@@ -134,9 +138,9 @@ Once the APE editors are happy with the APE, they will:
 #. Merge the pull request.
 
 #. Send an email to `astropy-dev <https://groups.google.com/g/astropy-dev>`_
-   with a link to the APE and a short summary to kick off the discssion period.
+   with a link to the APE and a short summary to kick off the discussion period.
    Emphasize that the proposal should be discussed on the mailing list, not the
-   pull request.
+   pull request.  **The discussion period should be at least two weeks.**
 
 As the discussion proceeds, the authors can choose to update the APE at any point via
 new pull requests, which are as before, subject to editorial review before merging.
@@ -161,15 +165,22 @@ APE Review
 ..........
 
 Once the authors feel that they have reached as close to a consensus as they
-will get (i.e., the community discussion on the APE has wound
-down), they can contact the Coordination Committee, who are
-responsible for making a final decision. The decision can be to:
+will get (i.e., the community discussion on the APE has wound down), any final
+edits should be made and a PR should be submitted for editorial review.  They
+must then notify the Coordination Committee that the APE is ready for full
+review and a final decision.  Note that any APE to be reviewed must be in the
+main branch of the repository with its status set to "Discussion."
+
+**The review period is expected to be 2-3 weeks**, beginning when the CoCo is
+notified by the APE authors.
+
+The decision can be to:
 
 * accept the APE,
 * reject the APE, or
 * suggest to the authors to continue the discussion before re-submitting the APE for a decision.
 
-One of the Coordination Committee members should then:
+One of the Coordination Committee members should create a new PR and then:
 
 #. Fill in the "Decision rationale" section of the APE with a description of why
    the status was chosen, including a summary of the community's discussion as relevant.

APE23.rst

@@ -8,7 +8,7 @@ Authors (alphabetical): Jeff Jennings, Adrian Price-Whelan, Nathaniel Starkman,
 :date-last-revised: 2026 01 23
 :date-accepted: 202x xx xx
 :type: Standard Track
-:status: Discussion
+:status: Discussion (earliest discussion end date: **13 Feb 2026**)
 
 Abstract
 --------

README.rst

@@ -9,33 +9,33 @@ formally. Please consult `APE Purpose and Process`_ for full details.
 APEs
 ^^^^
 
-=== ================================================================= =========== ============ ============
-#   Title                                                             Date (last  Status       DOI
-                                                                      revised)
-=== ================================================================= =========== ============ ============
-0   `The Astropy Project Governance Charter`_                         2021-Feb-19   Accepted   |APE 0 DOI|
-1   `APE Purpose and Process`_                                        2025-Oct-27   Accepted   |APE 1 DOI|
-2   `Astropy Release Cycle and Version Numbering`_                    2013-Dec-11   Accepted   |APE 2 DOI|
-3   `Configuration`_                                                  2013-Dec-10   Accepted   |APE 3 DOI|
-4   `Astropy Setup Helpers`_                                          2014-Jun-28   Accepted   |APE 4 DOI|
-5   `Coordinates Subpackage Plan`_                                    2014-Jan-22   Accepted   |APE 5 DOI|
-6   `Enhanced Character Separated Values table format`_               2015-Jan-26   Accepted   |APE 6 DOI|
-7   `NDData Plan`_                                                    2014-Dec-17   Accepted   |APE 7 DOI|
-8   `Astropy Community Code of Conduct`_                              2025-Oct-06  Superseded  |APE 8 DOI|
-9   `Timeseries object for Astropy`_                                  2023-Oct-20   Accepted   |APE 9 DOI|
-10  `Roadmap for Python 3-only support`_                              2016-Aug-22   Accepted   |APE 10 DOI|
-12  `Using Cookiecutter for the package-template`_                    2017-Mar-28   Accepted   |APE 12 DOI|
-13  `Vision for Astropy Spectroscopic Tools`_                         2017-Dec-12   Accepted   |APE 13 DOI|
-14  `A shared Python interface for World Coordinate Systems`_         2018-Nov-09   Accepted   |APE 14 DOI|
-15  `An Updated Model for the Affiliated Package Ecosystem`_          2018-May-14   Accepted   |APE 15 DOI|
-17  `A roadmap for package infrastructure without astropy-helpers`_   2019-Dec-12   Accepted   |APE 17 DOI|
-18  `Adopt NEP 29 for CPython and Numpy Version Support`_             2024-Jul-12   Accepted   |APE 18 DOI|
-19  `Distributing Astropy Project Funding`_                           2022-Feb-28   Accepted   |APE 19 DOI|
-20  `Formatting Code with Black`_                                     2022-Sep-23   Accepted   |APE 20 DOI|
-21  `Ending Long Term Support Releases`_                              2023-May-31   Accepted   |APE 21 DOI|
-22  `Astropy Affiliated Packages with pyOpenSci`_                     2024-Jan-29   Accepted   |APE 22 DOI|
-23  `Removing data storage (representations) from coordinate frames`_ 2026-Jan-23  Discussion     
-=== ================================================================= =========== ============ ============
+=== ================================================================== =========== ============== ============
+#   Title                                                              Date (last  Status         DOI
+                                                                       revised)
+=== ================================================================== =========== ============== ============
+0   `The Astropy Project Governance Charter`_                          2021-Feb-19   Accepted     |APE 0 DOI|
+1   `APE Purpose and Process`_                                         2025-Oct-27   Accepted     |APE 1 DOI|
+2   `Astropy Release Cycle and Version Numbering`_                     2013-Dec-11   Accepted     |APE 2 DOI|
+3   `Configuration`_                                                   2013-Dec-10   Accepted     |APE 3 DOI|
+4   `Astropy Setup Helpers`_                                           2014-Jun-28   Accepted     |APE 4 DOI|
+5   `Coordinates Subpackage Plan`_                                     2014-Jan-22   Accepted     |APE 5 DOI|
+6   `Enhanced Character Separated Values table format`_                2015-Jan-26   Accepted     |APE 6 DOI|
+7   `NDData Plan`_                                                     2014-Dec-17   Accepted     |APE 7 DOI|
+8   `Astropy Community Code of Conduct`_                               2025-Oct-06  Superseded    |APE 8 DOI|
+9   `Timeseries object for Astropy`_                                   2023-Oct-20   Accepted     |APE 9 DOI|
+10  `Roadmap for Python 3-only support`_                               2016-Aug-22   Accepted     |APE 10 DOI|
+12  `Using Cookiecutter for the package-template`_                     2017-Mar-28   Accepted     |APE 12 DOI|
+13  `Vision for Astropy Spectroscopic Tools`_                          2017-Dec-12   Accepted     |APE 13 DOI|
+14  `A shared Python interface for World Coordinate Systems`_          2018-Nov-09   Accepted     |APE 14 DOI|
+15  `An Updated Model for the Affiliated Package Ecosystem`_           2018-May-14   Accepted     |APE 15 DOI|
+17  `A roadmap for package infrastructure without astropy-helpers`_    2019-Dec-12   Accepted     |APE 17 DOI|
+18  `Adopt NEP 29 for CPython and Numpy Version Support`_              2024-Jul-12   Accepted     |APE 18 DOI|
+19  `Distributing Astropy Project Funding`_                            2022-Feb-28   Accepted     |APE 19 DOI|
+20  `Formatting Code with Black`_                                      2022-Sep-23   Accepted     |APE 20 DOI|
+21  `Ending Long Term Support Releases`_                               2023-May-31   Accepted     |APE 21 DOI|
+22  `Astropy Affiliated Packages with pyOpenSci`_                      2024-Jan-29   Accepted     |APE 22 DOI|
+23  `Removing data storage (representations) from coordinate frames`_  2026-Jan-23 **Discussion**     
+=== ================================================================== =========== ============== ============
 
 .. _The Astropy Project Governance Charter: https://github.com/astropy/astropy-APEs/blob/main/APE0.rst
 .. _APE Purpose and Process: https://github.com/astropy/astropy-APEs/blob/main/APE1.rst