Edit history

What needs fixing?

After the refactor, I would suggest enabling the Projects/Roadmaps capabilities in the github repo. This will allow better organization/grouping of issues, as well as tying issues to a specific Roadmap. So if someone is looking to contribute, instead of trying to look through all of the issues, they could search for the issues that are blocking the next release, and work on those. It also makes it easier to group multiple issues under one task. So Let's say Federation or EE2E, which will require multiple components to be accomplished before the main feature is implemented, could be grouped together. Overall, this would make tracking the progress of Fluxer a lot easier, and make it more apparent what issues need to be prioritized next to accomplish X feature.

Where is it? (optional)

Here's the github documentation about it, as well as some sample layouts: https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view

What needs fixing?

After the refactor, I would suggest enabling the Projects/Roadmaps capabilities in the github repo. This will allow better organization/grouping of issues, as well as tying issues to a specific Roadmap. So if someone is looking to contribute, instead of trying to look through all of the issues, they could search for the issues that are blocking the next release, and work on those. It also makes it easier to group multiple issues under one task. So Let's say Federation or EE2E, which will require multiple components to be accomplished before the main feature is implemented, could be grouped together. Overall, this would make tracking the progress of Fluxer a lot easier, and make it more apparent what issues need to be prioritized next to accomplish X feature.

Where is it? (optional)

Here's the github documentation about it, as well as some sample layouts: https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view

Checks

• ☑ I searched for existing issues and didn't find a duplicate.

What needs fixing?

After the refactor, I would suggest enabling the Projects/Roadmaps capabilities in the github repo. This will allow better organization/grouping of issues, as well as tying issues to a specific Roadmap. So if someone is looking to contribute, instead of trying to look through all of the issues, they could search for the issues that are blocking the next release, and work on those. It also makes it easier to group multiple issues under one task. So Let's say Federation or EE2E, which will require multiple components to be accomplished before the main feature is implemented, could be grouped together. Overall, this would make tracking the progress of Fluxer a lot easier, and make it more apparent what issues need to be prioritized next to accomplish X feature.

Where is it? (optional)

Here's the github documentation about it, as well as some sample layouts: https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view

Suggested wording (optional)

No response

Checks

• ☑ I searched for existing issues and didn't find a duplicate.