> we should create a documentation committee with a dedicated forum of > discussion space
Maybe instead start with figuring out what is wrong _exactly_? You say "documentation is hard". This is a general, non-actionable statement. If you said "module X has no examples for action Y" this would've been an actionable statement that can be turned into an issue for anyone to fix. It does not require a committee to figure out what is wrong, it requires an environment that makes it 1. easy to contribute an issue for the documentation -- if this part is missing ensure that at least (1) GitHub issue template is present, (2) there is a reminder at the documentation page that if _" you think that anything is missing, please create an issue here [link]. Please make sure that the described problem is as precise as possible (here is our guide on how to write docs [link], and some other helpful resources [link1], [link2]). Or, even better, consider making a pull request yourself [some link to relevant piece as well])"_ 2. There is a clear workflow for addressing documentation issues that is documented somewhere -- this does not require a dedicated design group, just start with _something_ and iteratively enhance the guide, organic growth is much better 3. Consider the most impactful action first, then go to the least important things. How much impact french documentation will have on the user base? Are there many French users that don't know English and can't use automatic translation tools? Are there any people who are interested in maintaining the translation?
