Annual survey

Some language communities do an annual survey.

Two examples:

• Rust
• Clojure

Of course all information sources need to be taken with a grain of salt. Surveys tell you about people who are willing and able to set aside (say) 15 minutes to take a survey.

Regardless, this would complement information from another self-selecting population -- folks who are willing and able to create/debate/advocate/shepherd github issues and RFC documents over hours/days/weeks/months.

(The latter group is important because there is a lot of volunteer work to be done; the people who do it should be recognized/appreciated. However it probably tends not to include as many people with full-time jobs and/or family-care obligations through the summer; people busy working on a startup company that uses Racket; and so on. Even if you didn't want to weight their input as highly (?), it's probably better to know about it than not know at all.)

Start by reading the issue and its linked Rust and Clojure survey examples. Define the survey scope and process with the community; done would mean an agreed survey plan or a published annual survey.