roles
roles copied to clipboard
bisq-network
Matomo Operator
Main duties:
- Ensure the Matomo server is functioning properly, secured, and updated
- Install plugins and provision accounts as required by the Analytics Administrator and others
- Write a monthly report on the appropriate issue.
Team: @bisq-network/matomo-operators
Cycle 6 report
- Created a self-hosted Matomo instance at https://matomo.bisq.network/
- Migrated the production https://bisq.network/ website from Google Analytics on August 23, 2019 in https://github.com/bisq-network/bisq-website/pull/208
- Migrated the production https://docs.bisq.network/ website from Google Analytics on September 10, 2019 in https://github.com/bisq-network/bisq-docs/pull/159
- Granted access to Website maintainer @m52go
- Granted access to Analytics maintainer @ripcurlx
- Granted access to Analytics admin @FKrauss
Matomo has been collecting data for almost a month now, so Analytics Admin should be able to start generating some reports soon.
/cc https://github.com/bisq-network/compensation/issues/380
Cycle 7 report
- Upgraded matomo to v3.12.0
- Instance is running great
/cc bisq-network/compensation#398
Cycle 8 report
- Promoted @FKrauss to superuser account
- Matomo upgraded to latest version
- No issues running instance
/cc https://github.com/bisq-network/compensation/issues/448
Cycle 9 report
- Added @RiccardoMasutti as analytics co-admin with @FKrauss
- Matomo upgraded to latest version by @FKrauss
- No issues running instance
/cc https://github.com/bisq-network/compensation/issues/470
Cycle 11 report
- Removed @RiccardoMasutti
- Matomo upgraded to latest version
- Instance running stable
/cc bisq-network/compensation#515
Cycle 12 report
- Matomo is runnning stable and nothing to report
https://github.com/bisq-network/compensation/issues/547
Cycle 13 report
- Matomo is running stable and nothing to report.
https://github.com/bisq-network/compensation/issues/569
Cycle 14 report
Matomo is running stable, and will be migrated to new server soon
/cc https://github.com/bisq-network/compensation/issues/602
Cycle 15 report
- Matomo has been installed on a new server, and the migration will happen this week (requires DNS change)
/cc https://github.com/bisq-network/compensation/issues/632
I've changed the name of this role from "Analytics Operator" to "Matomo Operator" to better reflect the specific nature of the role and to follow convention with other role names, which are named specifically vs. generally, e.g. "YouTube Administrator" vs. "Video Administrator", etc. This change also aligns with the existing @bisq-network/matomo-operators team name.
@wiz, I notice that there haven't been explicit cycle update comments on this role since Cycle 15 at https://github.com/bisq-network/roles/issues/88#issuecomment-663868332. Was there a decision made to drop comments if there is "nothing to report"? In any case, I think dropping them in such cases is worth doing so long as the compensation request still references the role issue, leaving an activity trail in the timeline that lets us know the role is being actively owned. I mean, this is actually pretty informative:
Well yeah, when it comes to hosting roles most reports were a boring "nothing to report" since everything is operating normally... if there was a problem the person would get removed from the role by the ops team members. So for those I personally think it's fine to waive the monthly report and compensation approval process, since we constantly monitor those services already. But we should formalize it in the Bisq docs somehow.
Since @m52go resigned as growth lead, and @ripcurlx resigned as analytics maintainer, and @FKrauss resigned as analytics admin, I believe there is nobody using the matomo analytics anymore.
Therefore, if there is no objection I would like to terminate this role and cease operating matomo services for the bisq.network website.
cc @cbeams @chimp1984 @ripcurlx @emzy
Worth considering, thanks. In any case I'd suggest leaving this open through the completion of the current cycle (Cycle 37), with some kind of mention of it in your compensation request, to increase the chances other see it and speak up about it if they have thoughts to the contrary or reasons not to do this.
One reason I can personally think of to continue operating the service is so that there is continuity of data whenever (if ever) someone picks back up on using it. If we simply shut Matomo down, there will be a "dark period" where it will be impossible to make any analyses about what happened during that period after the fact. We may only realize that we wanted and needed Matomo data in the future—and for reasons we may not be able to predict today.
According to prior compensation requests, maintaining this service only costs the DAO the equivalent of 100 USD/cycle. I would think that having that continuity of data, even if we're not using it right now, is at least arguably worth continuing that spend. Assuming it is not an undue burden for you @wiz, to continue administering the infrastructure, is there any reason not to just leave well enough alone?
Agreed, No objections
On June 10, 2022 5:27:47 PM UTC, wiz @.***> wrote:
Since @m52go resigned as growth lead, and @ripcurlx resigned as analytics maintainer, and @FKrauss resigned as analytics admin, I believe there is nobody using the matomo analytics anymore.
Therefore, if there is no objection I would like to terminate this role and cease operating matomo services for the bisq.network website.
cc @cbeams @chimp1984 @ripcurlx @emzy
-- Reply to this email directly or view it on GitHub: https://github.com/bisq-network/roles/issues/88#issuecomment-1152582896 You are receiving this because you were mentioned.
Message ID: @.***>
@cbeams it's been another year and I need to migrate the matomo to a new server - just shut the old one down. do we still want to keep this running? if so I'm happy to set it up but otherwise now is a good time to terminate this role.
Thanks for the heads up, @wiz. I think the previous logic still applies, ie that it’s better to have continuous data even if we’re not using it right now, so if it’s no big burden for you, my vote would be to stand the instance back up and let it keep collecting.On Jul 24, 2023, at 9:06 AM, wiz @.***> wrote: @cbeams it's been another year and I need to migrate the matomo to a new server - just shut the old one down. do we still want to keep this running? if so I'm happy to set it up but otherwise now is a good time to terminate this role.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>