BR: yBudget Cat Herder #3

[0xPickles]

Scope

Refer to previous request & end of period report: #227

About

The Cat Herder is responsible for overseeing operational processes and ensuring the yBudget team makes timely and informed decisions. This role serves as a process owner, acting impartially without voting rights. Responsibilities include making corrections and clarifications, proposing consensus-driven solutions, and ensuring adherence to proper procedures. The role does not directly influence decision-making outcomes.

This request period

This request period is the first where this role transitions into maintenance mode. There will still be minor dev work ongoing, bug fixing, minor improvements, and greater focus on documentation for the process and the automation system, but major development work is considered complete for the time being.

It's possible that maintenance mode is further reduced in the future as the process matures.

Plan

Ongoing Tasks

• Manage the funding request repository on GitHub.
• Oversee the handling of incoming requests from receipt to decision.
• Administer internal yBudget processes, including team coordination, voting procedures, status updates, timely communications, and team incentives.

Request Period Specific Deliverables

• Robokitty improvements
  • Improve documentation
  • UX and automation improvements
    • Automated polls
    • Automated voting reminders
    • Button telegram bot commands
  • Improve test coverage
  • Bug fixes
• Refine the yBudget process as necessary.

Deadline

From Nov 1 to Jan 31, 2024.

Team

• @0xPickles

Funding

Primary funding will support compensation for contributors and hardware operations.

Financials

Maintenance mode (this request)

• Monthly Allocation: 5,000 USD equivalent
• Total Request: 15,000 USD equivalent

Future requests

• If automation increases and the work effort in terms of hours spent is reduced, it's possible future maintenance mode requests are reduced further.
• If new major functional requirements are added, it's possible the request goes back into Development Mode.

Blue Dots

N/A

Wallet

• Wallet details will be provided separately to yBudget.

Reporting

A comprehensive report will be delivered at the end of the request period.

[0xPickles]

Epoch 3 Report

This epoch, I intended to focus on UX and automation improvements, but my priorities shifted to the following tasks:

Robokitty Development

High-priority items addressed:

• Unpaid Requests Report: Produced payment instructions for yRoboTreasury scripts.
• Default Payment Address: Added a default payments address to the teams struct for cases where no address is provided in the BR, updated methods accordingly.
• Log Payment Functionality: Implemented a feature to track payments made against approved BRs.
• Backfill Payments Data: Populated historical payment data for past BRs.
• Data bugs: Identified and squashed a couple of data bugs that had proposals associated to the wrong epochs.
• CLI Refactor: Simplified the Robokitty CLI by fully transitioning to the clap crate.
• Epoch Payments Report: Generated team payment instructions for yRoboTreasury based on epoch closures and point allocations.
• Proposal and End-of-Epoch Reports: Updated reports to include new payment data and fixed display bugs.
• WIP: Epoch Stats Report: Developing a report to compare KPIs across epochs.

For details, see commits in the public repo.

Yearn Governance

Contributed to governance processes, including YIPs and related implementations that required oversight.

Looking Ahead

The UX and automation improvements remain valuable and will be included in the next request. Additionally, I plan to refactor the Robokitty codebase to improve modularity and maintainability.

Feedback or suggestions are welcome!