I am against this kind of enforcement. In the past, we told everybody: “Hey come over to slack, we will help you on short notice.” And now we want to make it a bit more difficult by adding the my.typo3.org layer?
Why do we need to get “a better data quality” about those 2140 Slack Members that posted 2 or less messages?
I see no use in creating “terms and conditions” for the usage of Slack. The only applicable “terms and conditions” are those from Slack.
How should that be happen? How would do you define “active user base”? How would you messure that? What do you want to do with this knowledge?
Could you explain more detailed, which kind of data you want to publish here? Or how do you what to “move traffic” to talk? I guess that would be a good example for this DSGVO stuff.
I guess, that would be the best way to filter out all those users, that stayed quite for a while / never intended to talk / where to shy to talk and scare them out of the community. Great success - not.
So in my opinion, that is the perfect way to sabotage this kind of working community perfectly. If you want the active Slack users creating an account on my.typo3.org - ask them and let them do so voluntarily. But I am pretty sure that those, who consider themselves as active already have an account. So offer them the possibility to link there two accounts in the profile. Might be nice.
Don’t enforce anything. You will scare people away and will create a very bad reputation about TYPO3. As in “Those TYPO3 guys just want to talk to me, if register myself as a TYPO3 user.”