Archived
15
23
Fork
You've already forked meta
6

[AGREEMENT] Ryuno-Ki application to accessibility team #181

Closed
opened 2023年02月28日 10:44:59 +01:00 by Ryuno-Ki · 0 comments
Contributor
Copy link

Application

I propose to be accountable for the Forgejo release and become part of the the accessibility team.

  1. If you agree, please simply add a 👍 to this issue.
  2. If you disagree or have reservations, please write them down here, in a comment.

This application follows the Forgejo decision making process.

Pledge

I pledge to review changes on accessibility aspects.
I pledge to be available on a best-effort basis to answer questions about accessibility.
I pledge to educate about accessibility if someone has interest.

Background

Accessibility is in itself a broad area. My focus is with hard-of-hearing / deaf people (for private reasons). I learned German Sign Language and have contact with deaf people. I also know accessibility experts to expand my knowledge on special subjects.

In my past career as employee I spearheaded accessibility teams among Frontend developers. Those learning material is still in use by today.

Accessibility is a team-wide effort. Therefore I'm learning more about earlier phases in a FSDL to help raising awareness there as well.

The current workflow in Forgejo is a bit more complicated than Gitea's (caused by all those rebases) but I'm willing to learn more about it in 2023 so I can contribute more often. In the meantime I contributed to the website and commented on issues and PRs.

## Application I propose to be accountable for the Forgejo release and become part of the the [accessibility team](https://codeberg.org/forgejo/meta/src/branch/readme/TEAMS.md#accessibility). 1. If you agree, please simply add a 👍 to this issue. 2. If you disagree or have reservations, please write them down here, in a comment. This application follows the [Forgejo decision making process](https://codeberg.org/forgejo/meta/src/branch/readme/DECISION-MAKING.md). ## Pledge I pledge to review changes on accessibility aspects. I pledge to be available on a best-effort basis to answer questions about accessibility. I pledge to educate about accessibility if someone has interest. ## Background Accessibility is in itself a broad area. My focus is with hard-of-hearing / deaf people (for private reasons). I learned German Sign Language and have contact with deaf people. I also know accessibility experts to expand my knowledge on special subjects. In my past career as employee I spearheaded accessibility teams among Frontend developers. Those learning material is still in use by today. Accessibility is a team-wide effort. Therefore I'm learning more about earlier phases in a FSDL to help raising awareness there as well. The current workflow in Forgejo is a bit more complicated than Gitea's (caused by all those rebases) but I'm willing to learn more about it in 2023 so I can contribute more often. In the meantime I contributed to the website and commented on issues and PRs.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta#181
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?