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.

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

Organize and Simplify the 'Node.js feature requests' Project #52485

Closed
RedYetiDev opened this issue Apr 11, 2024 · 1 comment
Closed

Organize and Simplify the 'Node.js feature requests' Project #52485

RedYetiDev opened this issue Apr 11, 2024 · 1 comment
Assignees
Labels
feature request Issues that request new features to be added to Node.js. meta Issues and PRs related to the general management of the project.

Comments

@RedYetiDev
Copy link
Member

RedYetiDev commented Apr 11, 2024

What is the problem this feature will solve?

Currently, https://github.com/orgs/nodejs/projects/4/ is a bit, well, cluttered. I propose a couple of 'rules' that will keep this uncluttered and organized.

What is the feature you are proposing to solve the problem?

Everything here is subject to change, and those changes aren't my call, but here are my ideas:

Automatic Movement

For tasks that can be performed automatically:

  • Issue is opened: Move to Needs Triage
  • If issue has a linked PR that is merged, move to Done
  • If issue has a linked PR that is open (and the issue is not done), move to In Progress
    • If PR gets closed, move back to Needs Triage, or Todo, based on it's previous state
  • If issue is closed as not-planned, move from Needs Triage to Not Planned
  • If issue gets closed as completed by a member of the NodeJS team, move to Done

Manual Movement

For tasks that can't be performed automatically

  • Issue is a duplicate of another, remove from feature request (or move to a new column, duplicate)
  • Issue is triaged, move to Triaged
  • Issue will be added, move to Todo
  • Issue will not be implemented, move to Not Planned
  • Issue is being worked on, move to In Progress
  • Issue has been implemented, move to Done
  • If special attention is needed, move issue to Needs Review / Other

Columns

  • Needs Triage

  • Triaged

    The issue is a valid feature request, but the team needs to decide whether or not to implement it

  • Todo

  • In Progress

  • Done

  • Not Planned

  • Stale

  • Needs Review / Other

    For issues that just need a NodeJS team member to look at (whether it needs a new home in the project, or some kind of situation)

Examples of issues in the wrong place

In order to prevent the redundant referencing of random issues, I'm only listing 3

#52485 - Wrong Repo / Not Planned is currently sitting in Pending Triage
#50697 - Wrong Repo / Not Planned is currently sitting in Pending Triage
#50480 - Not Planned is currently sitting in Pending Triage

@RedYetiDev RedYetiDev added the feature request Issues that request new features to be added to Node.js. label Apr 11, 2024
@RedYetiDev
Copy link
Member Author

@github-project-automation github-project-automation bot moved this to Pending Triage in Node.js feature requests 1 minute ago

Oh the irony

@RedYetiDev RedYetiDev changed the title Update Feature Request Management Organize and Simplify the 'Node.js feature requests' Project Apr 12, 2024
@RedYetiDev RedYetiDev added the meta Issues and PRs related to the general management of the project. label Apr 21, 2024
@RedYetiDev RedYetiDev moved this from Awaiting Triage to In Progress in Node.js feature requests Jun 26, 2024
@RedYetiDev RedYetiDev self-assigned this Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issues that request new features to be added to Node.js. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

No branches or pull requests

1 participant