Skip to content

Return a link to the description of badges #677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −1
Open

Return a link to the description of badges #677

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion affiliated/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,16 @@ <h1 id="affiliated-package-list-pre-ape22">Affiliated Packages Registry (Pre-APE

<p>This section contains the listing of Astropy Affiliated Packages that pre-dated
<a href="https://github.com/astropy/astropy-APEs/blob/main/APE22.rst">APE 22</a>.
This section is frozen as of March 6, 2024.</p>
No new packages are be added to this list after March 6, 2024; but packages can be removed or their
status can change.</p>
<p>A detailed description of the meaning of the badges for each package can be found
<a href="https://github.com/astropy/astropy-project/blob/a9ea09ccd27703ea3ef2a80a811a5f70f91bc94b/affiliated/affiliated_package_review_guidelines.md#development-status-devstatus">here</a>.
Note in particular that a development status of
<img src="https://img.shields.io/badge/Functional%20but%20unmaintained-orange.svg" alt="Functional but unmaintained"> or
<img src="https://img.shields.io/badge/Functional%20but%20low%20activity-orange.svg" alt="Functional but low activity">
might be perfectly fine for e.g. teaching or with older Python verions, but packages with this status might not be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
might be perfectly fine for e.g. teaching or with older Python verions, but packages with this status might not be
might be perfectly fine for, e.g., teaching or with older Python versions, but packages with this status might not be

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dhomeier and I are still discussing other ideas. It's not ideal to mark "functional but low activity" packages orange, since they are, ham, "functional". Maybe a new category "none development" or a different badge color (e.g. blue) would help?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Technically, following the original review guidelines orange (or maybe yellow?🤪) would be appropriate, as such a package is in “non-excellent condition”, but the wording would probably be misleading in that case. Thus we could change that to make it clearer, or emphasise that it is not in an optimal state.

compatible with the latest versions of Astropy or might not reply to issues or bug reports.
</p

<p>Total number of pre-APE 22 affiliated packages: <strong id="total-affiliated-pkgs"></strong></p>

Expand Down