Archived
15
23
Fork
You've already forked meta
6

Decision diagram for contributions to Forgejo #165

Open
opened 2023年02月22日 20:03:36 +01:00 by Ryuno-Ki · 0 comments
Contributor
Copy link

This is a follow-up to forgejo/forgejo#409

Given the nature as soft-fork of Gitea there are a handful of branches we have to juggle for our releases. This can feel intimidating (happened to at least two members of the organisation).

forgejo/forgejo@613c87ed70/CONTRIBUTING/WORKFLOW.md

Since we have support for Mermaid, I propose to add a flowchart (see https://mermaid.js.org/syntax/examples.html#basic-flowchart ) to aid in the decision making.

What I need is an answer to questions like:

I want to contribute an accessibility fix. Which branch do I have to branch of of? What should be the target branch when I open a Pull Request?

And

In which relationship are the branches to each other?

(Like, branch X is branched of of Y and will be merged back after rebase of Y on top of Z).

Having it visualised could help. Mermaid is text-based so updating should also be low-effort.

Note, that this must not replace a text representation. See https://adrianroselli.com/2022/03/maybe-dont-use-flow-charts-on-github.html and https://mermaid.js.org/config/accessibility.html

CC @fsologureng

This is a follow-up to https://codeberg.org/forgejo/forgejo/pulls/409 Given the nature as soft-fork of Gitea there are a handful of branches we have to juggle for our releases. This can feel intimidating (happened to at least two members of the organisation). https://codeberg.org/forgejo/forgejo/src/commit/613c87ed7082e65f3b68a01def46268dd671d539/CONTRIBUTING/WORKFLOW.md Since we have support for Mermaid, I propose to add a flowchart (see https://mermaid.js.org/syntax/examples.html#basic-flowchart ) to aid in the decision making. What I need is an answer to questions like: > I want to contribute an accessibility fix. Which branch do I have to branch of of? What should be the target branch when I open a Pull Request? And > In which relationship are the branches to each other? (Like, branch X is branched of of Y and will be merged back after rebase of Y on top of Z). Having it visualised could help. Mermaid is text-based so updating should also be low-effort. Note, that this must not replace a text representation. See https://adrianroselli.com/2022/03/maybe-dont-use-flow-charts-on-github.html and https://mermaid.js.org/config/accessibility.html CC @fsologureng
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#165
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?