Analytics Meeting Minutes

This page was built to accumulate the minutes from the Analytics Working Group meetings and make them available to the public. The contents are organized chronologically, with the most recent meeting first

April 2022

29 Apr 2022 MTG

- attendence: @mZ#3472 @B.#2574 @Saturn#1052 @woptop#0493

Discussions:

    --  identifying and incentivizing contributors

     -- chicken and egg: need to define tasks to get contributors, need to get a sense of the contributors interests and skills to define tasks

     -- there are existing tasks that need to be broken down further

     -- how do we think about tasking the task of breaking down tasks (requirements gathering / defining acceptance criteria)

     -- because breaking down work is work we need to break down the work when someone is ready to actual take that work on then we break it down

     -- a next step: Saturn is going to work on recruiting, announcements; we'll use lettuce-meet to find a time that works for more people

     -- another next step: establish a pattern, set expectations about compensation. B and mZ can work on an Improvement Proposal for payment reporting, and then reverse engineer that to define working procedures for this working group

    -- will hold off on breaking down other proposed projects until after there are resources interested in collaborating on those projects.

    -- recurring biweekly friday meeting will drop to 30 min and focus on "sprint review" and "admin" but work-sessions will be scheduled separately to make progress on specific projects

March 2022

18 Mar 2022 Mtg[edit | edit source]

Present: @B., @mZ, @ricoflan, some others...

1. administrative + Elections: motions @b coordinator, @mZ archivist, @Saturn broker; all passed with no objections + payments : clear to make payments based on wallets status but small blocker on process; @B. to work with @mZ on process -- cross over from @ricoflan -- partnership between analytics and hustle karma on tracking work and logging payments--> new "epic" support karma hustle on reporting/payments etc
2. review of Submitted work + autopay Make Whole Computation -- split work across created point of confusion @Wade  |  TPT @gnudrew25 @B.; lack of clarity of task definition: @ricoflan do we know the addresses and do we know the amounts. @B. we know the addresses, we "can know the amounts"; @ricoflan we need the amounts and they need to get them to @Wade  |  TPT; we weren't aware this had not happened yet. @B. will assess out of band, now that he knows @Wade  |  TPT is the person he needs to coordinate with. @mZ meta comment: future work should have clearer acceptance criteria eg 'deliver dataset {"address": amount} to specific person Y such they can do X next step` -- we will improve work tracking processes.
3. Discuss and Define New Work + Complete autopay task now that it is clearly specified (and more clearly assigned); needed data: {addresses: proofs per address per epoch} --> final value of make whole {addresses: amount to transfer} + Scorecode -- can we adopt it; @mZ thinks we should but its a big chunk of work. @B. we should be doing architecture, analytics design but outputs may actually need to be accomplished in collaboration with engineering. @B. motion to take on Analytics Product Management; seconded by @Saturn @ricoflan -- need to begin capturing requirements. + tabling wallet by type distribution analysis til future call + @B.  Analytics wg official meeting is every other week but we have a motion to do work sessions in alternating weeks | motion passed
4. Next session -- new topic for admin next week: tooling, eg where is out backlog? is it karma hustle? do we need jira/trello/github or the like? -- improved definition of tasks discussed // try to make these meetings more like sprint planning/review meetings. (edited)