Mad Hatter MGMT Season 4 Proposal

[nonsensetwice]

Author: nonsensetwice#3475
Date Created: June 24, 2021

1. Summary

2. Mad Hatter Features and Services

3. Season 4 Plans and Goals

   1. Proposed Feature Development
   2. Support and Education Through wenHELP

4. Financial Implications

   1. Project Manager Responsibilities
   2. Core Developer Responsibilities
   3. Compensation Breakdown

5. Success Metrics or KPIs

   1. Feature Utilization
   2. Feature Development
   3. Developer Onboarding

Multisig Address:

TBD

SUMMARY

Once upon a time, the original intent of the DEGEN Workgroup was to develop “one bot to rule them all” to assist in all matters pertaining to the administration of the BanklessDAO (hereafter, bDAO) Discord Server. However, upon development of the POAP distribution feature, DEGEN became specifically about POAP, and the bDAO server-specific features were split off into the Mad Hatter Discord bot, with development waning. Due to recent organizational changes, the DEGEN Workgroup has since relinquished custody of Mad Hatter to pursue further development of the POAP features. As such, Mad Hatter now requires a team to assist in its maintenance, feature support and education, and continued development.

MAD HATTER FEATURES AND SERVICES

Mad Hatter serves specifically to be a public good for bDAO. The features that exist in Mad Hatter have been designed and developed out of either a need for administrative automation, or requests from the community to improve operations. The existence of the bot itself provides a number of opportunities to help onboard new members for various groups in the DAO, while continued development allows for incoming developers to showcase their talent. This bot is not currently, nor will it ever be, designed for the purpose of generating revenue.

In an effort to best support bDAO, a number of features were developed and built, including, but not limited to:

• /squad up for quickly bootstrapping projects with the right roles and personnel
• /notion homepage for Notion Guild Pages delivery
• /notion meeting-notes for quickly bootstrapping an agenda in Notion for Guild meetings
• /afk or “Away from Keyboard,” to capture user notifications and inform the notifier when someone is away
• /coordinape for Coordinape participation form delivery
• /guest pass for Guest Pass assignment and automated removal upon expiration
• /timecard for time keeping, to manage time coverage and review
• Username Spam Filter to prevent spoofing of high-level contributor accounts and minimize social engineering attempts
• Various features and updates to support Ops in administering the Discord server

SEASON 4 PLANS AND GOALS

PROPOSED FEATURE DEVELOPMENT

Prior to releasing custody of Mad Hatter, the DEGEN Workgroup had a roadmap of features to build out for the bot, none of which came to fruition, yet remain anticipated. In bringing a team together to support the continued development of Mad Hatter, many of these features will become production priorities. These features include, but are not limited to:

• Augmenting Mad Hatter with a front end for ease of configuration
• Opening up Squad Up to allow Level 1 members to quickly bootstrap projects
• Enabling tipping with BANK on Polygon
• Adapting Coordinape automation via the upcoming Coordinape bot for bDAO-specific functionality
• And many more!

While it is unlikely that these will all be completed during the remainder of Season 4, these features can begin development, the delivery of which will allow bDAO to become better organized and more efficient. Furthermore, Mad Hatter will provide ample opportunity for devs new to bDAO to pick up bounty work and quickly integrate into the DAO’s work-intensive ecosystem. Currently, the Developers Guild provides its own form of First Quest, providing incoming developers with quick and easy bounties to produce features across a number of projects, allowing said developers a fast path to onboarding. Mad Hatter will provide more of these opportunies, with the team vetting incoming feature requests and making bounties available to incoming developers for those features that are most likely to succeed.

SUPPORT AND EDUCATION THROUGH wenHELP

In addition to the above, there are matters of education and support to consider. With the success of DEGEN largely due, at least initially, to the work provided by the Product Support Center—soon to be rebranded as wenHELP, and will be referred to as such for the remainder of this document— Mad Hatter MGMT will outsource education and support there. Despite Mad Hatter being the de facto bDAO bot, few are aware of all of its capabilities, and fewer still are competent in all of its use cases. Α partnership with wenHELP will not only provide the necessary support for issues and inquiries, but also provide opportunities for general education of Mad Hatter features across the DAO by way of content generation and presentation.

wenHELP’s responsibilities will include:

• Content generation, including, but not limited to:
  • feature documentation
  • tutorial videos
  • Scheduling Knowledge Sessions
• Troubleshooting and issues resolution, including:
  • logs review
  • troubleshooting ticket management
  • communicating technical issues to the core dev team for bug fixes and patches
  • answering support-related questions from bDAO members
• Running polls and surveys to understand use cases for Mad Hatter in bDAO and how it can be improved season over season

Mad Hatter MGMT will work closely with wenHELP to provide the assistance they require to generate all necessary materials and properly support bDAO members coming to wenHELP for assistance with Mad Hatter.

FINANCIAL IMPLICATIONS

To accomplish all the terms of this proposal, Mad Hatter MGMT will consist of four salaried positions:

ONE PROJECT MANAGER
The Project Manager works to maintain the operations of Mad Hatter MGMT, which includes managing team meetings and POAP distribution; proper execution of the team’s governance framework; instantiating multisig transactions and following up with approvals and/or rejections; resolving conflicts within the team; preparing proposals and other such operational documentation; and reviewing Pull Requests to the codebase maintained by the team.

THREE CORE DEVELOPERS
The Core Developers are primarily responsible for the overall structure and maintenance of the codebase, which includes writing tests and refactoring code; reviewing Pull Requests; designing data models and guiding the development of requisite APIs; guiding the development of and maintaining the front end/bot configuration site; onboarding new developers; working closely with other developers from other projects in collaboration, as either consultants or contractors; and assisting in the management of the bot’s deployment.

In addition to these positions, a bounty pool will be necessary to incentivize contributing developers to build new features. A funds disbursement to wenHELP for the creation of documentation and educational materials and presentations, in order to provide hands on support for bDAO members. Furthermore, the deployment costs, currently covered under a private debit card, will need to be reimbursed.

COMPENSATION BREAKDOWN

As the current workload is unknown, the following figures are being presented as an estimate of the time commitment of the core team, with regard to a small stipend for each position. Considering that the Core Team’s focus will be on maintaining and planning, approximately six hours of work per week is estimated for each position at a rate of 1000 BANK/hr.

A bounty pool of 40,000 BANK is being requested for the remainder of Season 4. This will potentially cover up to one new major feature development, and a handful of smaller features and feature augmentations.

An amount of 190,000 BANK is being requested for wenHELP to generate educational content around all of Mad Hatter’s current features, and provide support for bDAO members seeking to make the most use of these features. This amount also includes basic app monitoring to assist in the troubleshooting process when bDAO members run into issues using Mad Hatter’s features, and includes support through Season 5. The breakdown of this amount can be found in the Mad Hatter MGMT x wenHELP Partnership Proposal.

Finally, deployment costs are currently covered via the personal debit card of nonsensetwice#3475 and runs at a monthly cost of 10.00 USD + applicable taxes and fees. This includes:

• Mad Hatter’s deployment through Heroku: 7.00 USD/mo
• LogDNA/Mezmo account for log collection and 7-day retention, and team member access: 3.00 USD/mo

A reimbursement of 24.00 USD for the months of June and July are requested in the form of USDC/DAI or its equivalent in BANK to cover these costs, as well as the relevant transaction fees to offramp to fiat.

Role	Position	Rate	Time	Total per Line
Project Manager	nonsensetwice#3475	1000 BANK/hr x 6 hr/wk	4 weeks	24,000 BANK
CORE Dev 1	Tiki#0503	1000 BANK/hr x 6 hr/wk	4 weeks	24,000 BANK
CORE Dev 2		1000 BANK/hr x 6 hr/wk	4 weeks	24,000 BANK
CORE Dev 3		1000 BANK/hr x 6 hr/wk	4 weeks	24,000 BANK
Bounty Pool				40,000 BANK
Education & Support	wenHELP			190,000 BANK
Deployment Reimbursement		12 USD/Mo	2 months	24 USDC/DAI
Total Overall				326,000 BANK + 24 USDC/DAI

This brings the total amount being requested for the remainder of Season 4 to 326,000 BANK + 24 USDC or DAI.

SUCCESS METRICS OR KPIS

Mad Hatter success metrics will revolve around three main points:

• Feature utilization
• Feature development
• Developer onboarding

FEATURE UTILIZATION

Mad Hatter MGMT will measure the success of Mad Hatter by way of feature utilization and new feature development. We will work closely with wenHELP to monitor logs and measure the use of each command, taking a record of utilization prior to education of the available features, and then again after educational materials have been published and knowledge sessions have been introduced. The primary goal during this stage will be to establish a workflow that will allow Mad Hatter MGMT to quickly recognize and understand what features are underutilized and why, and poll the DAO on how these features can be improved, or if they should be removed. The remainder of Season 4 will be used to establish this workflow, minimizing the fiscal impact of Mad Hatter in future seasons.

FEATURE DEVELOPMENT

Mad Hatter provides a unique value proposition to the DAO in that features can be developed specifically to meet the DAO’s needs internally, by way of improving operations and efficiency. For the remainder of Season 4, the list of proposed features will be reviewed and bounties will be established for developers to begin work on those that take priority. As mentioned above under the same heading, it is unlikely that these features will be completed by the end of the season; however, progress can be made toward their completion, with expected feature delivery in early Season 5.

DEVELOPER ONBOARDING

As all new feature development will be executed via bounties, Mad Hatter MGMT will work closely with the Developers Guild to provide opportunities for developers new to bDAO to become quickly acclimated to the DAO’s work culture. Smaller bounties for feature augmentations will be recommended to new developers, while larger bounties for new features will be recommended to more consistent contributors, though any developer can take on any bounty they feel confident in completing. In terms of metrics, success in this area will be determined by how many bounties are picked up and completed. Ultimately, Mad Hatter MGMT will provide a welcoming atmosphere of work for new developers coming to bDAO through the Developers Guild.

Approve Mad Hatter MGMT for Funding?

• Yes, absolutely
• No, absolutely not (please comment below why not)