@@ -133,7 +133,7 @@ In a nutshell
133133-------------
134134
135135+--------------------------+-----------------------------+----------------------------+
136- | Step | pyOpenSci | Astropy (pre-APE 24 ) |
136+ | Step | pyOpenSci | Astropy (pre-APE 22 ) |
137137+==========================+=============================+============================+
138138| Editorial infrastructure | Editor-in-Chief, | Editor, reviewer |
139139| for a single review | editor (domain specific), | |
@@ -158,11 +158,11 @@ In a nutshell
158158.. _pyOpenSci Editorial Board : https://www.pyopensci.org/about-peer-review/#our-editorial-board
159159.. _Astropy team roles : https://www.astropy.org/team#roles
160160
161- As of July 2023, Astropy had the following `pre-APE 24 Affiliated Package review guidelines `_
162- and followed this `pre-APE 24 Affiliated Package review process, with templates `_.
161+ As of July 2023, Astropy had the following `pre-APE 22 Affiliated Package review guidelines `_
162+ and followed this `pre-APE 22 Affiliated Package review process, with templates `_.
163163
164- .. _pre-APE 24 Affiliated Package review guidelines : https://github.com/astropy/astropy-project/blob/1afe5df1728e86dac51b9b87bc30a7c2cdb289ac/affiliated/affiliated_package_review_guidelines.md
165- .. _pre-APE 24 Affiliated Package review process, with templates : https://github.com/astropy/astropy-project/blob/1afe5df1728e86dac51b9b87bc30a7c2cdb289ac/affiliated/affiliated_package_review_process.md
164+ .. _pre-APE 22 Affiliated Package review guidelines : https://github.com/astropy/astropy-project/blob/1afe5df1728e86dac51b9b87bc30a7c2cdb289ac/affiliated/affiliated_package_review_guidelines.md
165+ .. _pre-APE 22 Affiliated Package review process, with templates : https://github.com/astropy/astropy-project/blob/1afe5df1728e86dac51b9b87bc30a7c2cdb289ac/affiliated/affiliated_package_review_process.md
166166
167167Meanwhile, pyOpenSci has its own
168168`submission guide for package authors <https://www.pyopensci.org/software-peer-review/how-to/author-guide.html >`_,
@@ -181,7 +181,7 @@ collaborations with different communities (e.g., Astropy). They are also:
181181Is open review a deal breaker?
182182------------------------------
183183
184- We do not think so! In the pre-APE 24 process, the reviewer was anonymous by default
184+ We do not think so! In the pre-APE 22 process, the reviewer was anonymous by default
185185because we modeled the process after traditional astronomical journals.
186186Even then, the reviewer had the option to reveal themselves if they wanted to.
187187Given that the Astropy ecosystem is open-source anyway, it makes sense for us
@@ -287,7 +287,7 @@ reviewer for Affiliated request, namely:
287287
288288* familiarity with the Astropy project,
289289* ability to judge whether a package integrates well with the Astropy ecosystem
290- (as per pre-APE 24 guidelines), and
290+ (as per pre-APE 22 guidelines), and
291291* having domain expertise in the area of the package (e.g., galaxy evolution).
292292
293293pyOpenSci and Astropy both ask editors/reviewers disclose any potential conflict of interest (COI)
@@ -352,7 +352,7 @@ are the bare minimum for a package being able to go through the pyOpenSci review
352352Listing on websites
353353-------------------
354354
355- The pre-APE 24 `Astropy Affiliated Packages `_ listing are listed by alphabetical order
355+ The pre-APE 22 `Astropy Affiliated Packages `_ listing are listed by alphabetical order
356356with hard-coded badges. While these badges are color-coded to give a at-a-glance status
357357of packages, they become outdated over time and now could even be misleading
358358(i.e., they really are showing the status at the time of acceptance, not the current status).
@@ -409,8 +409,8 @@ If we decide to move forward with this partnership, these are the proposed steps
409409 and publish the updated guidelines and process, including new
410410 COI policy, packaging guidelines, and so forth.
411411 These new guidelines need to be compatible with
412- `pre-APE 24 Affiliated Package review guidelines `_ and
413- `pre-APE 24 Affiliated Package review process, with templates `_.
412+ `pre-APE 22 Affiliated Package review guidelines `_ and
413+ `pre-APE 22 Affiliated Package review process, with templates `_.
414414 At the same time, we should link to the actively developed
415415 `community-driven packaging guide `_ over at pyOpenSci and `Scientific Python `_,
416416 in addition to the `OpenAstronomy packaging guide `_ already implemented in Astropy.
@@ -427,7 +427,7 @@ If we decide to move forward with this partnership, these are the proposed steps
4274274. For the new packages, have our project website ingest a RSS/XML feed
428428 from pyOpenSci for cross-listing (also see **Listing on websites **).
429429 We would also link back to pyOpenSci on our page.
430- Meanwhile, we would keep the pre-APE 24 listing on a "legacy affiliation" page
430+ Meanwhile, we would keep the pre-APE 22 listing on a "legacy affiliation" page
431431 that will be kept alive during the lifetime of the Astropy project.
4324325. Work with pyOpenSci to cross-list Affiliated editors, between their
433433 editors listing and our roles page. For example, pyOpenSci could
0 commit comments