Review of Older Issues and PRs

[lock9]

Summary or problem description
We have issues and PRs that are old and inactive. This creates a feeling of abandonment and makes it more complex to manage the project.

Do you have any solution you want to propose?

• Create a backlog
• Go through over 300 open issues and PRs across different repositories.
  • For each issue decide:
    • Send it to the backlog?
    • Recreate it summarized? (when the problem continues to exist but the best solution may have changed)
      • Can be used to merge multiple issues into one.
      • Can be used to avoid losing important feedback and ideas in the middle of long discussions
    • Set a priority?
    • Or close it

We can always reopen the issues in the future. We don't have a backlog. Without one is hard to view what should be done now and what should be done later.

Related to #2949

Neo Version

• Neo 2
• Neo 3

Where in the software does this update applies to?

• Compiler
• Consensus
• CLI
• Plugins
• Ledger
• Network Policy
• P2P (TCP)
• RPC (HTTP)
• SDK
• VM
• Other:

[shargon]

For other repositories, we can move only the active ones, the previous repository will be archived, so these old issues don't hurt us