-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Remove Scarf tracking #45865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Scarf tracking #45865
Conversation
jscheffl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK to merge from my side
After discussions, we have decided to remove Scarf usage tracking for now. We might replace it with Matomo at a later stage. https://matomo.org/guide/tracking-data/apps-sdks/
Backport failed to create: v2-10-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 70a8a8a v2-10-testThis should apply the commit to the v2-10-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
After discussions, we have decided to remove Scarf usage tracking for now. We might replace it with Matomo at a later stage. https://matomo.org/guide/tracking-data/apps-sdks/ Discussion: https://lists.apache.org/thread/bkpn6rc8w1wsd3c29zlolfb8s8r4ldtq
After discussions, we have decided to remove Scarf usage tracking for now. We might replace it with Matomo at a later stage. https://matomo.org/guide/tracking-data/apps-sdks/ Discussion: https://lists.apache.org/thread/bkpn6rc8w1wsd3c29zlolfb8s8r4ldtq
After discussions, we have decided to remove Scarf usage tracking for now. We might replace it with Matomo at a later stage.
https://matomo.org/guide/tracking-data/apps-sdks/
Discussion: https://lists.apache.org/thread/bkpn6rc8w1wsd3c29zlolfb8s8r4ldtq
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.