Yeah, these are all important, but are they specific to ROS? And for that matter, how wil best practices and design patterns change with the adoption of ros2? I think the topics on the best practices wiki page illustrate the difference between common quality topics and ROS-specific best practices.
Either way, I think @130s is right about the need for some sort of process to come to consensus and categorization. Discourse leads to pretty visible discussion, but isn’t well suited for persistence or process control. The wiki doesn’t work very well, t you can see that he page @130s linked still uses pre-hydro terminology.
Maybe a best-practice tag in the quality channel for requesting/brainstorming, since quality-minded people are likely to go there, and a GitHub repo for drafting them via PRs.