Skip to content
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

Matomo Operator #88

Open
m52go opened this issue Sep 9, 2019 · 19 comments
Open

Matomo Operator #88

m52go opened this issue Sep 9, 2019 · 19 comments
Assignees
Labels
team:ops https://bisq.wiki/Ops_Team

Comments

@m52go
Copy link

m52go commented Sep 9, 2019

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

@wiz
Copy link

wiz commented Sep 27, 2019

Cycle 6 report

Matomo has been collecting data for almost a month now, so Analytics Admin should be able to start generating some reports soon.

/cc bisq-network/compensation#380

@wiz
Copy link

wiz commented Nov 11, 2019

Cycle 7 report

  • Upgraded matomo to v3.12.0
  • Instance is running great

/cc bisq-network/compensation#398

@wiz
Copy link

wiz commented Dec 14, 2019

Cycle 8 report

  • Promoted @FKrauss to superuser account
  • Matomo upgraded to latest version
  • No issues running instance

/cc bisq-network/compensation#448

@wiz
Copy link

wiz commented Jan 18, 2020

Cycle 9 report

/cc bisq-network/compensation#470

@wiz
Copy link

wiz commented Mar 16, 2020

Cycle 11 report

  • Removed @RiccardoMasutti
  • Matomo upgraded to latest version
  • Instance running stable

/cc bisq-network/compensation#515

@cbeams cbeams added the team:ops https://bisq.wiki/Ops_Team label Apr 15, 2020
@wiz
Copy link

wiz commented Apr 20, 2020

Cycle 12 report

  • Matomo is runnning stable and nothing to report

bisq-network/compensation#547

@wiz
Copy link

wiz commented May 18, 2020

Cycle 13 report

  • Matomo is running stable and nothing to report.

bisq-network/compensation#569

@wiz
Copy link

wiz commented Jun 21, 2020

Cycle 14 report

Matomo is running stable, and will be migrated to new server soon

/cc bisq-network/compensation#602

@wiz
Copy link

wiz commented Jul 25, 2020

Cycle 15 report

  • Matomo has been installed on a new server, and the migration will happen this week (requires DNS change)

/cc bisq-network/compensation#632

@cbeams
Copy link
Contributor

cbeams commented Jan 5, 2021

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.

@cbeams
Copy link
Contributor

cbeams commented Jan 5, 2021

@wiz, I notice that there haven't been explicit cycle update comments on this role since Cycle 15 at #88 (comment). 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:

image

@wiz
Copy link

wiz commented Jan 5, 2021

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.

@wiz
Copy link

wiz commented Jun 10, 2022

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

@cbeams
Copy link
Contributor

cbeams commented Jun 12, 2022

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?

@wiz
Copy link

wiz commented Jun 12, 2022

Sure, I'm fine to keep it running based on the reasons you gave.

@FKrauss
Copy link

FKrauss commented Oct 11, 2022 via email

@wiz
Copy link

wiz commented Jul 24, 2023

@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.

@cbeams
Copy link
Contributor

cbeams commented Jul 24, 2023 via email

@wiz
Copy link

wiz commented Feb 22, 2024

I've shut down matomo.bisq.network and I resign as Matomo Operator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team:ops https://bisq.wiki/Ops_Team
Projects
None yet
Development

No branches or pull requests

4 participants