https://bugzilla.redhat.com/show_bug.cgi?id=2190479 Link Dupont <link@xxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |link@xxxxxxxxxxx --- Comment #1 from Link Dupont <link@xxxxxxxxxxx> --- > Note: This repository is probably useless outside of internal HashiCorp use. It is open source for disclosure and because our open source projects must be able to link to it. Should we consider a downstream patch that permanently disables these checkins, but maintains the API so that calling code can continue to function? Leaving the telemetry calls enabled by default puts the responsibility to enable/disable the telemetry to the downstream packagers, or possibly to the users. This would allow Fedora's RPMs to run within HashiCorp, but does that bring any more value than having to remember to always disable the checkin downstream? I'm leaning towards carrying a patch in this RPM that disables the checkin and telemetry. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2190479 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202190479%23c1 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
