Hey, thanks for your feedback!
I appreciate the opportunity to answer these questions. Below each one is my response.
(1) Regarding the allocation of reserve funds, which are subject to council members’ voting on future proposals, an additional $5,000 is proposed. However, it appears that the Build DAO previously allocated $3,500 in January, yet the funds have not been distributed or reported by the DAO treasurer. Could you please clarify the necessity for an additional $5,000?
In January, that $3500 went toward implementing Keypom trial accounts in our forkable / reusable gateway example, launching the Build North America DevRel program, and introducing a modular component library for builders.
The $5000 in reserves this month used to fund this Forefront analytics dashboard.
Looking ahead to March, we have additional projects in the works:
(2) It is noted that $5,000 is requested for the development of low-code builder tools by open-source contributors (efiz.near & collaborators) and $7,000 for the team of developers (archetype-org.near) working on package management solutions. Could you elaborate on the significance of these initiatives for Near users like myself?
These products improve quality of experience for NEAR builders and increase utility of the blockchain operating system. Ultimately, such initiatives contribute to widening ecosystem adoption and sustaining development of community resources.
CLI tool + environment for local BOS development
- helps Node.js developers overcome the learning curve of BOS
- offers an expanding list of evolving tools for building open web apps
- integrates familiar solutions like VS Code, GitHub, NPM, and Typescript
- enables usage of custom SDKs, packages, and libraries, resulting in better user experiences
Users: Build DAO, PotLock, Proof of Vibes, DiscoverBOS, and QuestVerse
common structure for open web apps ~ unified frontend paradigm
Everything provides a way to put it all together, so anyone can build on the open web using NEAR, and everyone can help each other. This allows Build DAO to expand its communities to include more diverse groups. On-chain type systems make it easier for non-developers to create widgets and other things, leveraging available templates, libraries, modules, and frameworks.
global type registry, curation system, and metadata layer
This project aims to secure cross-chain composability, which would protect safety and give users peace of mind when interacting with open web solutions. Also, their team is connecting NEAR builders with communities in relevant ecosystems like Urbit and Ethereum. This may help to strengthen our position as leaders in the space.
(3) The proposal for openwebacademy.near to develop examples, tutorials, and workshops for builders lacks specific Key Performance Indicators (KPIs). Could you please include measurable KPIs such as the number of examples, tutorials, workshops, and expected outcomes?
The main goal of this collaboration is to empower Build DAO contributors with training and educational content focused on the open web stack, fostering a robust community of NEAR builders.
You can review this new post by izcc.near (on-chain), outlining their KPIs:
- Participation Rate: number of qualified builders taking part in educational programs
- Completion Rate: percentage of participants who successfully complete the bootcamp
- Repository Engagement: usage of resources and contributions by influential NEAR builders
- Community Growth: growth of the NEAR Buidlers community within Build DAO over time
- Project Contributions: number of projects initiated or enhanced by program participants
Deliverables
- 5x tutorials: guides covering various aspects of open web development
- 3x written tutorials: step-by-step walkthroughs of complex technical processes
- 8x technical infographics
- “Zero to Builder” bootcamp playbook, syllabus, and evaluation rubrics
- Slides and material used in workshops and bootcamps
- Bootcamp session recordings
- Workshop session recordings
Here is a sneak peek of a resource they are putting together now… 
(4) Similarly, the proposal to hire imagin.near to develop a support system for builders and their projects also lacks clarity regarding outcomes and KPIs. Could you please provide more detailed information?
The current plan is to measure success by tracking the number of active builders contributing to relevant projects. As the Build Support Lead, Thom will design and implement a recruitment and onboarding system involving dev agencies and talent houses.
Overall, this program would improve operations and bolster usability of resources. Below are some objectives and metrics we discussed with imagin.near and the support squad:
Accountability → Coordination + Productivity
Build Stewards cultivate successful projects and communities.
- Metric – How many builders post ideas, updates, or questions via the #build feed?
Talent Recruitment → Onboarding + Capacity
Build Tasks bring skilled contributors to NEAR and the open web.
- Metric – How many developers are hired by NEAR Builders Cooperative?
Quality of Experience → Learning + Retention
Build Resources facilitate development of apps, components, gateways, etc.
- Metric – How many people feel empowered to build something on their own?
(5) Could you please use this form for the Dragonverse proposal? It’s hard to understand OKRs.
I’ve shared that request with their team, led by Rhyme Taylor and Jeff Gold.
Since then, we have discussed these goals and metrics:
Objectives:
- users really having fun!
- generating awareness
- activating more game builders
Key Results:
- lots of people playing Dragonverse and enjoying the gameplay
- custom BOS gateway for gaming deployed on web4 (with docs)
- reusable incubator game components added to a library
Please let us know any other info that you need. Thanks!