Skip to content
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.

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

FEATURE: Hide or customize search categories on Astropy page #518

Closed
pllim opened this issue Nov 18, 2024 · 8 comments · Fixed by #521
Closed

FEATURE: Hide or customize search categories on Astropy page #518

pllim opened this issue Nov 18, 2024 · 8 comments · Fixed by #521
Labels
enhancement New feature or request

Comments

@pllim
Copy link
Contributor

pllim commented Nov 18, 2024

This is a follow-up of #207 . On https://www.pyopensci.org/communities/astropy.html , I see the following:

Screenshot 2024-11-18 135031

In the context of Astropy, I don't find them very useful, particularly "geospatial". I am also not very sure what "data munging" means though it does have hits when I click on it on that page. "reproducibility" seems redundant as that is one of the goals of Astropy project (and possibly OSS) in general.

Would be nice if Astropy is allowed to hide or customize these categories. Thanks for your consideration!

@lwasser
Copy link
Member

lwasser commented Nov 19, 2024

@pllim i hear you. those categories are a part of our submission template, and we use them to broadly categorize the types of packages in our ecosystem. Maybe a good first move is for us to simply remove the categories and filtering from the partner page.

then, in another issue we can talk about what type of filtering astropy might prefer?
I had thought about filtering by health metrics previously - last commit date, downloads, stars. But we could have a discussion that is separate from - let's remove the filtering from the page for now.

there are only 3 packages so filtering isn't super powerful right now anyway!

let me know what you think!

@pllim
Copy link
Contributor Author

pllim commented Nov 19, 2024

I think hiding for now is fine but let's see what @dhomeier and @hamogu says. Thanks!

@pllim
Copy link
Contributor Author

pllim commented Nov 19, 2024

What about something like #521 ?

@hamogu
Copy link

hamogu commented Nov 19, 2024

Hiding is fine. We can think about filtering in any form once the number of packages goes > 20 or so.
I could image a filter by wavelength (radio, IR, optical, UV, High-energy). Of course many packages are broadly applicable, but we also have many that are somewhat instrument or wavelength specific.
However, the question then becomes how to tag that? Additional field in the YAML? Som other mechanism?

Either way, we can worry about that when we have enough packages to make up a representative sample to look at to decide what would be reasonable categories to use; for now, let's just hide it.

@pllim
Copy link
Contributor Author

pllim commented Nov 19, 2024

We do have like 50 packages that are already Affiliated in our pre-pyOpenSci days if those help us form categories, but I agree it is not urgent. Thanks!

@hamogu
Copy link

hamogu commented Nov 19, 2024

And I looked at those when I made my suggestion to mostly sort by waveband. Still, as the landscape of software changes, I don't know if we'll end up with a similar distribution in 2027 when we hit 50 astropy packages in PyopenSci.

@pllim
Copy link
Contributor Author

pllim commented Nov 19, 2024

landscape of software changes

Indeed it does. Maybe we will have to sort by "typed" and "not typed"... 🙈

@hamogu
Copy link

hamogu commented Nov 19, 2024

Indeed it does. Maybe we will have to sort by "typed" and "not typed"... 🙈

or "hyped" and "not hyped".

Or "AI with LLM" and "other software".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants