Review issues, consolidate, suggest issue templates, sort projects (general read through)

[balacij]

I heard we like issues, so I thought I'd make another.

The real intention of this ticket is to review our issues, consolidate them where possible, suggest issue templates (as a trial run, if we're interested), sort projects, and generally "clean up" the issues. I will use this issue to track my progress. This issue should be closed by June 12th, 2024.

Work Tasks

• [ ] Suggest issue templates
• [ ] Wiki: add a section about writing good, actionable issues and link to further resources

Pages:

• [ ] 1
• [ ] 2
• [ ] 3
• [ ] 4
• [ ] 5
• [ ] 6
• [ ] 7
• [ ] 8
• [ ] 9
• [ ] 10
• [ ] 11
• [ ] 12
• [ ] 13
• [ ] 14
• [ ] 15

Projects (at least the ones I have access to):

• New:
  • [ ] Typing Expr
  • [ ] Vectors, Matrices, Arrays, etc.
• Classic:
  • [ ] Projectile
  • [ ] Documenting Drasil - Double Pendulum Project
  • [ ] Rationalizing the data-structures/classes in drasil-lang
  • [ ] Chunk Investigation
  • [ ] ChemCode
  • [ ] Merging in Extensible ChunkDB Prototype
  • [ ] Refactoring based on #2883's Analysis
  • [ ] Project Setup Clean-up
  • [ ] Removing Reliance on RelationConcepts
  • [ ] Improving Vector Support
  • [ ] Upgrading Expr
  • [ ] Explore Space, Symbol, and Unit

[smiths]

Thank you for taking this on @balacij! I like the idea of using issue templates. I wonder if our template should have a checklist with reminders for what makes a good issue? Part of our current problem is that our issue tracker includes great ideas, but they aren't great issues. The content would be better in a discussion or on a wiki page. The checklist could remind the author of the issue that it should be something that can be closed with less than a week's (a day's) work? Alternatively, we can add more information to our contributor's guide on what makes a good issue. We don't have to reinvent what makes a good issue; there are resources that can be found online.

[balacij]

That sounds like a great idea! It would be nice to see more actionable tickets, having a time estimate or work breakdown would be great where possible. I certainly think we should move questions to the discussions section almost entirely. I like that idea, and that looks like a great resource. I will add these tasks to the OP.