mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-05-12 22:10:25 +00:00
7894e1bb8f
* Separate documentation about the workflow for better attention. I could imagine that it was not read by everyone, since it was after the trivial 'Please write in English' instructions. * Improve explanations about the workflow, expectations and next steps. * Explicitly mark the Enhancement template to be mostly for contributors. * Disable blank issues. I could not really identify any recent usage of it that was legitimate. * Improve instructions about which details to share about the own Forgejo usage. * Explicitly state in the enhancement template that only issue references should go in there, not noise. * Create a placeholder in problem template to add references to potential solutions later. I hope this resolves some of the issues observed with the new workflow and improves the quality of submitted reports. Also addresses the feedback already received in https://codeberg.org/forgejo/user-research/issues/71 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10847 Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Otto Richter <otto@codeberg.org> Co-committed-by: Otto Richter <otto@codeberg.org>
39 lines
2.2 KiB
YAML
39 lines
2.2 KiB
YAML
name: "Step 2: Enhancement"
|
|
description: "[Advanced users only] Suggest a solution to one or multiple problems that have already been reported (see step 1)."
|
|
title: "enh: "
|
|
labels: ["enhancement/feature"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
- Please speak English, as this is the language all maintainers can speak and write.
|
|
- Be civil, and follow the [Forgejo Code of Conduct](https://codeberg.org/forgejo/code-of-conduct).
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
### New workflow
|
|
|
|
We are currently experimenting with a new workflow to manage issues and better understand your problems and needs. This is step 2 of the workflow, which is intended for Forgejo contributors: If you just want to raise a problem or need you have, please refer to step 1.
|
|
|
|
This step allows to document a solution to one or multiple problems. It allows developers to focus on actionable implementation tasks without the clutter of previous discussions or triaging work.
|
|
|
|
If you want to learn more about the background of our workflow, feel invited to read and participate in [the discussion that led to the current approach](https://codeberg.org/forgejo/discussions/issues/415). We are looking forward to your feedback.
|
|
- type: textarea
|
|
id: problems
|
|
attributes:
|
|
label: Existing problems this enhancement addresses
|
|
description: Only list the issue numbers of the **existing** problems that your proposal addresses. **Do not add new descriptions.** If you haven't previously described a problem, please [complete step one of the workflow](https://codeberg.org/forgejo/forgejo/issues/new?template=.forgejo%2fissue_template%2fproblem.yaml) and describe the problem you'd like to solve first.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: Enhancement description
|
|
description: Describe the changes you suggest for Forgejo and explain how they address the problems.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: details
|
|
attributes:
|
|
label: Details and notes
|
|
description: Feel free to supply additional information like technical considerations, link to alternative solutions, UI mockups etc.
|