@ostephen I support the idea of a simplification of the category structure.
-
using this forumget a lot of post that may be more relevant insupport - I agree to merge
using this forumandcommunity feedback -
Day-to-day project operationandNews and Announcementsalso have a lot of overlap. I think aCommunitycategory will better represent them (with potential sub-category).
The cool things about tags is that they are not specific to a category; for example, the tag reconciliation is used in the Support and Using this forum category
For the internship, I agree to have one sub-category. We can create one tag per cohort. When we announce the internship program, we can reference the discourse tag for the cohort. This way, conversations can also happen across categories.
In summary, here is a tentative new structure (happy to move this to a separate thread if needed).
- Support (do we need a sub-categories?)
-
Development & Design - with a ‘design chat’ and ‘design proposal’ tag
- Contributor Meetup
- Internship (with a tag for each cohort).
- Documentation (move the category as sub-category since Documentation is part of the software)
-
Community
- News and Annoucement
- Day to Day
- Community Feedback (Do we need that subcategory or message can be posted in the top category?)
- Teaching OpenRefine