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

Review tag changes #1176

Open
asweigart opened this issue Jul 30, 2024 · 2 comments
Open

Review tag changes #1176

asweigart opened this issue Jul 30, 2024 · 2 comments

Comments

@asweigart
Copy link
Contributor

asweigart commented Jul 30, 2024

I've made a list of tag changes I want to make using a script. They are here:

https://docs.google.com/spreadsheets/d/1JratsDIiKdmUNIs-RImMYLFpsgo2mPfwpzj2dhbY7r0/edit?usp=sharing

Column A contains the current tag, while column B is the tag I want to change it to. The tag policy is lowercase letters and separated by spaces. If column B is blank, then this is a tag I want to remove entirely. I've tried to be conservative with the tags I'm changing here, but it is a large change so I wanted the spreadsheet reviewed before I make a PR.

This issue is just for getting someone else to review the list of changes I'm going to make. It can be closed once someone gives their thumbs up.

@jonafato jonafato transferred this issue from pyvideo/pyvideo Jul 30, 2024
@jonafato
Copy link
Member

jonafato commented Jul 30, 2024

Thanks, Al! At a quick glance, this seems like a big improvement. I see a few places where I may have notes (e.g. shortening "python-software-foundation" to "psf" removes clarify, especially for folks that are not already familiar enough with the foundation to use the initialism as conversational shorthand).

I'd also like to loop in @kojoidrissa, who authored the tag guidelines at https://github.com/pyvideo/data/blob/7280e6fcfb2813fff7e9ba70f73672394d97c126/CONTRIBUTING.rst#tags, as a possible extra reviewer. I've mentioned having some concerns regarding our current rule about lower-casing everything and how that relates to screen readers and other accessibility tools (edit: and just general clarity, since cases like "FLOSS" and "floss" concern two very different things). I don't think that's a blocker on fixing up many of the current tags, but it may lead to another revision like this in the near future.

Note: I've moved this issue to the data repository where the metadata (including tags) is maintained.

@jonafato
Copy link
Member

@asweigart I've recently added a way to specify html-based redirects via a redirects.txt file that I think would be useful here. For event names, speaker names, tag changes, and tag consolidations, this will allow us to make large batches of changes without breaking existing links. Can we start with the consolidation (sans case changes), event name, and speaker name items here as a first pass? Happy to make notes in your linked spreadsheet to keep things scriptable (e.g. redirect from / redirect to) if you share edit access.

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

No branches or pull requests

2 participants