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.

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

Jump to bottom

[Feature] Aspect labels for i18n and a11y #59

Closed
zackkrida opened this issue Sep 8, 2021 · 2 comments · Fixed by #63
Closed

[Feature] Aspect labels for i18n and a11y #59

zackkrida opened this issue Sep 8, 2021 · 2 comments · Fixed by #63
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟩 priority: low Low priority and doesn't need to be rushed

Comments

@zackkrida
Copy link
Member

Not required, but it might be nice to have dedicated aspect labels for internationalization and accessibility, to make it easy for contributors who value that type of work to find relevant issues.
@zackkrida zackkrida added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository labels Sep 8, 2021
@dhruvkb
Copy link
Member

dhruvkb commented Sep 14, 2021

Since the i18n work happens in GlotPress, I don't think there will be PRs for that anymore. Also the [aspect: a11y] label would overlap heavily with the [aspect: interface] label.

@dhruvkb dhruvkb mentioned this issue Sep 14, 2021
Merged
7 tasks
@zackkrida
Copy link
Member Author

Sure, I think it's fine to use the a11y label in the future for issues like "Switch to i18n method for hardcoded strings".

@zackkrida zackkrida added 🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature labels Sep 14, 2021
dhruvkb added a commit that referenced this issue Feb 20, 2023
@dhruvkb
Merge pull request #59 from Automattic/line_endings
64bf132 
Fix line endings
dhruvkb pushed a commit that referenced this issue Feb 20, 2023
@zackkrida
Merge pull request #59 from WordPress/vulnerabilities
2031bc4 
Update packages with vulnerabilities
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟩 priority: low Low priority and doesn't need to be rushed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a label for a11y WordPress/openverse
2 participants
@zackkrida @dhruvkb