Skip to content

docs: proposal for issue triage process #2052

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

Merged
merged 2 commits into from
Dec 15, 2022
Merged

docs: proposal for issue triage process #2052

merged 2 commits into from
Dec 15, 2022

Conversation

Golodhros
Copy link
Member

Summary of Changes

Proposes a new process for issue management
Cleans up docs

CheckList

Make sure you have checked all steps below to ensure a timely review.

  • PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • PR includes a summary of changes.
  • PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
  • In case of new functionality, my PR adds documentation that describes how to use it.
    • All the public functions and the classes in the PR contain docstrings that explain what it does

@boring-cyborg boring-cyborg bot added area:all Related to all the project area:docs labels Dec 8, 2022
Signed-off-by: Marcos Iglesias <[email protected]>
Copy link
Contributor

@kristenarmes kristenarmes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'm looking forward to being able to more easily see which issues are more popular and should be prioritized!

@Golodhros Golodhros marked this pull request as ready for review December 9, 2022 18:56
@Golodhros Golodhros requested a review from a team as a code owner December 9, 2022 18:56

1. New issues will automatically added the "Status: Needs Triage".
2. Once maintainers review the issue, they will remove the "Status: Needs Triage" label, add new ones and close the issue.
3. The Amundsen community will upvote the issues they want to be addressed by viewing the [features](https://github.com/amundsen-io/amundsen/issues?q=is%3Aissue+is%3Aclosed+sort%3Areactions-%2B1-desc+label%3Atype%3Afeature+) and [bug](https://github.com/amundsen-io/amundsen/issues?q=is%3Aissue+is%3Aclosed+sort%3Areactions-%2B1-desc+label%3Atype%3Abug+) lists and reacting with a 👍.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 notes:

  • do we have a min number of upvote/downvotes to move or discard a feature request?
  • As maintainers, we can also vote on any issue, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the input Verdan!

  1. Not really. I was thinking on not discarding them at all, as they are already "closed" issues. The link we attach here would show the issues ordered by number or reaction, so it would act as an organically prioritized backlog. That said, maybe we could discard (adding the "Abandoned" tag) issues due to lack of technical feasibility.

  2. Oh yeah. I would say our vote should count more! :)

@Golodhros Golodhros merged commit 99227c1 into main Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:all Related to all the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants