Community sentiment survey

[jducoeur]

Possible idea: should we do a survey of the TL community as a whole? It's easy for the Steering Committee to become an echo chamber, and it's worthwhile to make sure that we are in touch with the feelings and priorities of the whole organization.

This one is more an idea to ponder and maybe gradually evolve, not a call for action NowNowNow. Writing surveys is easy; writing good, actionable surveys that accurately represent sentiment and result in enough information to make better decisions is not. This one is unlikely to happen in the next month or two, but we can use this thread for brainstorming about it.

[jducoeur]

We should keep in mind that the "community" is far from homogeneous. We have lots of sub-communities, and should think about whether we want to ask questions aimed at any or all of:

• Maintainers of core libraries
• Maintainers of affiliate libraries
• Users of the various TL components (which ones do they use? how do they combine them? what use cases?)
• FP geeks coming into Scala
• FP newbies trying to get their hands around this stuff

[zmccoy]

For tackling the variations of where folk are coming from I think having a lot of optional portions and then "If you are a maintainer of a core library" ... "Which one?" ... "More question..." etc and we can attempt to partition the data that way. If those bullet points are essentially headers people can just fill out what they identify under.