You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @jjasghar noted in Slack, it would be a very good idea to have a page with a single list of useful project links, e.g. Linktree.
Linktree is available at no cost and one can get stats about usage of a Linktree page with subscription fee.
While I am not a huge fan of collecting all the data all the time, it seems to me that being able to track hits to a Linktree page is a nice metric to tell us if we had more fans at say a meetup in Paris rather than one in New York City. It would also allows the Community Maintainers to collect that data point without having to bother meetup organizers to collect stats and send them to us (though of course we'd want to talk to the nice meetup organizers, anyway).
We should investigate if there are other services that are better from a pricing and privacy perspective, make a decision about it, then document said decision clearly in the community repo documents and add this detail to our Collaboration page.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.
As @jjasghar noted in Slack, it would be a very good idea to have a page with a single list of useful project links, e.g. Linktree.
Linktree is available at no cost and one can get stats about usage of a Linktree page with subscription fee.
While I am not a huge fan of collecting all the data all the time, it seems to me that being able to track hits to a Linktree page is a nice metric to tell us if we had more fans at say a meetup in Paris rather than one in New York City. It would also allows the Community Maintainers to collect that data point without having to bother meetup organizers to collect stats and send them to us (though of course we'd want to talk to the nice meetup organizers, anyway).
We should investigate if there are other services that are better from a pricing and privacy perspective, make a decision about it, then document said decision clearly in the community repo documents and add this detail to our Collaboration page.
The text was updated successfully, but these errors were encountered: