We’ve now had discuss.ocaml.org running happily for some months, and I’m going to do another round of adjusting the site structure, particularly around categories.
A few projects have asked whether they can use the site to discuss their pieces in particular, and some maintainers want to have semi-private areas so that they can shift their discussions onto discuss but still maintain a focussed small group dynamic for day-to-day discussions.
Therefore, a good structure for this category-wise would be:
Projectscategory, with sub-categories for individual major communities. This would mean renaming the
Ocsigencategories into subcategories of projects, and adding others such as
Miragein the future.
Maintainerscategory which is configured by default to be semi-private, and invitational to maintainers of the particular projects involved. These are not designed to grow into enormous discussions, but to cover the need for private discussions while still using an open-source platform.
- Review the use of tags in the main site, and update the pinned introduction post to link newcomers to useful indexes.
I hope that with this new structure, projects can have a good place to redirect longer-running GitHub issues into the more freeflowing discussion format encouraged here. It will also help us shift currently rather spread out maintainer discussions into here, to make it easier for new contributors to get up to speed on what their fellow maintainers have discussed in the past. This is currently rather difficult with email/Slack/IRC (although @whitequark’s IRC logs are extremely handy in this regard).
As a reminder, the difference between categories and tags on Discourse seems primarily around ease of subscription to new topics. Categories can be individually subscribed to, so a project maintainer could ignore the rest of the site while only receiving messages relevant to them.