In our team meeting yesterday we discussed this a little and noted that for some tools, or in some communities, QuickSurveys may be overkill. If a wiki only has a few administrators it would be frustrating for them to receive multiple surveys about different tools rather than just getting one which asks about all of them in one place. Additionally, even on a big wiki there might only be a handful of users who use, for example, AbuseFilter, so we could easily get the list of active users and message them directly.

After further discussions about this draft KR, we determined that this would be best achieved by creating a standardized methodology for collecting information about product satisfaction, and user-level/community-level product adoption. This would provide an advantage in reducing the amount of repeated preparatory work (e.g. reusable versus bespoke privacy statements, transferrable localization) and allow us to better cross-compare adoption and satisfaction across different products. The current intent is to collect fairly high-level satisfaction/adoption metrics, and fine-tune these on a per-project basis.

This does mean that QuickSurvey is unlikely to be the main tool for collecting survey responses, due to its current limitations.

After I meet with Claudia today, we'll wait until the request comes from the RDS process.
After that, Management will decide how to proceed.