Summary

In #274 by @michelengelen we stopped sending CSAT links for issues opened by open source users, under two main assumptions:

1. Looking at those would be a distraction; better focus on paid customers. This was raised by @oliviertassinari
2. Sending those surveys for open source issues is vastly different from how other open source projects behave. Usually, they do nothing. We don't want to create a vibe of a corporate product. This was raised by @colmtuite.

However, after discussing this with @DanailH, it created several issues:

1. On the first point, we don't get much feedback anymore. But fundamentally, whoever opens the issue is not the same as whoever will benefit from it. If you look at the total number of issue openers on a repository vs. users, you will find that about 0.1% of the users contribute by opening issues, and about x10 more contribute with upvotes or comments (1%). Put that in perspective with having about 10% of the user base paid. So we need to know how we do.
2. On the second point. We fundamentally need to leave a comment when an issue is closed to tell the next users to please, please open a new issue if it's unrelated (next.js locking old issues feels horrible DX). From there, is there a corporate negative vibe if we sneak in a way for people to give feedback? I think we can find a way to execute this in a way that feels light touch and about DX care.

So I would propose we start simple, we reenable CSAT collection on open core components (data grid, etc.).

Examples

No response

Motivation

A continuation of #156.

Search keywords: -