Looking at it again the discussions are what determine what a person would like to read and contribute to it. Hence rather than have different discussion environments implement a filter based on interest and level of understanding that a person would like to track.
Got this two scenarios to explain what am thinking to in terms of content for dev and content for user as well as where the two merge.
Scenario 1: Rust Coding e.g Cargo test --release won’t work. This is purely dev side similar to an issue against the repo on github. This would be filtered out for dev and only developers would like to be notified of such a disucssions.
Scenario 2: Client software on my machine has crushed or not working. The discussion here would be to provide support to such a person(user). Clearly this discussion is both for dev and users who can both contribute to best find a solution of why client fails/not working. However, there is not for all developers considering their different levels. An app developer may choose to opt out of such discussion since he/she is more concerned with whether network works as a whole and not for one person.
Scenario 3: Feature Request/ App Request Another example where both dev and user can contribute together.
Pretty much dev is involved in all available scenarios that may exist but its there preference as to whether to participate in the discussion. As for users it wouldn’t make sense to have them participate in scenario 1 since its very technical for them.