@devgovgigs.near [Posted on Developer DAO Board](https://near.social/#/devgovgigs.near/widget/Post?id=531) ## Idea: DevHub 2023 Q2-Q3 *2023-05-10: First revision.* OKRs?! Not in my decentralized community! DevHub is organized by a decentralized community, but we still need to coordinate with each other, agree on the priorities, and what is delivered by who and when. This document tries to follow best OKR practices, but it mixes key-results and initiatives for the sake of actionability. The names assigned to the Objectives are Accountable people per RACI. Responsible, Consulated, Informed roles are not mentioned, for example @frol.near is Responsible for many usages of Fellowship program and the creation of curriculums/modules, but this is not mentioned. This post also does not mention non-moderator community contributors as their responsibilities are more fine-grained than Objectives. # Community Quality *The NEAR developer community is pleasant and worthy to be in.* * **P1 Objective: Repositories are maintained.** @bo.near * KR: Community PRs are Issues are addressed * KR: Small backlog of Issues and PRs * KR: Repositories have the following files: `CODEOWNERS`, `CODE_OF_CONDUCT.md`, license files, `CHANGELOG.md`, `README.md`, see for the reference: https://github.com/near/near-sdk-rs * KR: Repositories have releases and CI where applicable * KR: Ownership of each of the repositories is assigned to the correct parties. IP ownership is taken care of * **P1 Objective: Documentation is maintained.** @bo.near * KR: All documentation has exhaustive and up-to-date information * KR: Examples and tutorials use recent versions of the libraries * KR: Each DevHub community links to the relevant documentation * **P0 Objective: Community channels are discoverable and navigate-able.** @bo.near * KR: All community channels are linked into DevHub Communities with Telegram and Zulip messages synced * **P1 Objective: Community is active and responsive.** @theori.near * KR: Each Community Group telegram channel has a “Notes” document pinned and populated with ideas/concerns brought up in the channel so far. This document is used to propose the agenda for the meetings * KR: Community feedback is recorded in the “Notes” document and propagated to Work Groups and DevHub moderators * KR: Semi-coverage by DevHub community managers in channels to make sure questions are answered or acknowledged within some time. Needs linking all channels into DevHub Communities to be executable * **P2 Objective: Community experience is cohesive and coordinated across the ecosystem** @maria * KR: Published interfaces with the regional hubs * KR: Hackbox is used to launch 4 events/month in Q2 and 8 events/month in Q3 * KR: All events are amplified through the marketing campaigns * KR: Each event participant is attempted to be retained using our Developer Engagement strategy # DevHub Product *DevHub is a central place for developer community interactions.* * **P0 Objective: Each DevHub Community page is a perfect place for all relevant developer needs.** @theori.near * KR: Each DevHub Community page is visually pleasing, including all its sub-pages * KR: Each DevHub Community Overview page is an equivalent of “Awesome <name of the community>”, see for reference https://github.com/mbasso/awesome-wasm * KR: Each DevHub Community page has linked Telegram and Zulip channels as separate tabs that are also synced real time * KR: Each DevHub Community Events page contains notes and recordings of the past meetings for this community, as well as the upcoming meetings and relevant events, including relevant third-party events * KR: Each DevHub Community Sponsorship page has an up-to-date list of projects that were sponsored or in the process of payment approval. The stages will correspond to the stages of KYC process, which will depend on KYC provider used at a time * KR: Each DevHub Community Proposals page has an up-to-date list of proposals that are currently in the review process with the last stage being approved/declined * **P1 Objective: DevHub is rebranded.** @theori.near * KR: DevHub has a new visual identity incorporated into its web-page, swag, video thumbnails, etc * KR: Community plays an active role in different stages of creating visual identity: sourcing for ideas, voting on the final design, selecting swag, and celebrating the results * KR: Creation and assignment of each individual developer badge is its own campaign which includes recognition of outstanding developers and its celebration * **P1 Objective: https://www.neardevgov.org/ is merged into http://neardevhub.org/ .** @theori.near * KR: DevHub Communities teams are Work Group members displayed from DevHub contract data * KR: Blog posts are moved into posts under DevHub Moderators Community * KR: Moderators can create, edit, remove DevHub Communities. Work Group members can edit them * KR: https://www.neardevgov.org/ now redirects to http://neardevhub.org/ * KR: We replaced mentions of DevGov and DevGigs with DevHub wherever possible # Developer Engagement *Onboard new developers and they stick around without financial incentives.* * **P1 Objective: Bootcamp participants continue their active journey with NEAR after the bootcamps.** @ajeon.near * KR: Established relationship with one or more carefully selected bootcamp with BOS added to their agenda * KR: Post-bootcamp, module system, similar to freecodecamp * KR: Devs create portfolios of real functioning projects * KR: Devs are introduced to more web3 concepts * KR: Fellowship program provides hands-on guidance for devs * **P1 Objective: Hackathons are a recurrent touch point with NEAR devs.** @maria * KR: Regular hackathons across the globe re-engage devs with NEAR in-person * KR: Bootcamp participants with love to build are actively invited to hackathons * KR: Real-work bounties from DevHub constitute majority of the prize pool * KR: Fellowship program provides hands-on guidance for hackathon participants, including hustling, pitching, team-building * **P2 Objective: University clubs are a major source for new NEAR devs.** @ajeon.near * KR: Established relationship with uni blockchain clubs in areas with high tech population (Seattle, Chicago, Atlanta, Boston, etc) * KR: Regular regional meetups pull club members into ideation and problem solving conversations with established professionals * KR: NF speaker program provides regular speakers for uni blockchain clubs and meetups * **P3 Objective: Experienced devs have their traits matched with opportunities.** @ajeon.near * KR: DevHub has clear contribution guidelines * KR: For each type of skill and passion we have a map of opportunities, including mentoring, strategizing, building, etc # Strategic Initiatives *DevHub owns several critical responsibilities in the ecosystem.* * **P1 Objective: NEAR is on the forefront of ZK innovation.** @nearmax.near * KR: DevHub provides exceptional e2e support for top-3 ZK projects * KR: NEAR has presence at top ZK events and communities * KR: ZK developers can freely migrate to NEAR ecosystem * **P1 Objective: DevHub organizes top NEAR dev events.** @maria * KR: Organization of NEARCon hackathon and other brand-focused events e2e * KR: NEAR is represented in large third-party events, physical and virtual # Operations *DevHub is a self-sufficient organization.* * **P2 Objective: DevDAO Trust is launched and processes all payments.** @nearmax.near * KR: DevDAO Trustee dashboard is launched * KR: DevDAO Trustees are onboarded, which includes training, written guidelines, and hardware/software setup; * **P2 Objective: DevHub Community for Moderators is launched.** @nearmax.near * KR: Explainer of DevDAO structure and interface with DevHub * KR: Explainer for escalation and feedback paths in DevHub ecosystem * KR: Explainer of roles and responsibilities * KR: Linked or created explainers of all processes, including proposal review process * **P2 Objective: DevHub payments operations are streamlined.** @nearmax.near * KR: Dashboard for DevDAO trustees provides a one-click solution for reviewing and approving payments for proposals that were approved by community and passed KYC/KYB * KR: Dashboard for DevDAO trustees provides reports for payouts grouped by quarters and categories * KR: Each Work Group and the corresponding Community has a well-maintained Kanban board with pending and past payouts where the last stage is the only action from DevDAO trustee * **P2 Objective: DevHub proposal operations are streamlined.** @frol.near * KR: Each Work Group and the corresponding DevHub community has an up-to-date Kanban board with stages that proposals go through * KR: Github NEP board and labels are synced into DevHub proposals and labels, resulting in identical boards for the Work Groups * KR: Each DevHub Community board has real-time metrics for how long each proposal has been stale and what is the average time for proposals in each stage in the past 3 months * **P2 Objective: DevHub users are never lost and know what to do.** @frol.near * KR: When user posts on DevHub we display them guidelines with what to expect and do next, to ensure they are not left hanging * KR: Notification system suggesting users next steps and guidelines for when their post discussion stale * **P3 Objective: DevHub Moderators delegate most of their work to partners.** @nearmax.near * KR: DevHub integrates with one or more NEAR Gigs platforms and favors them over direct paid community contributors * KR: Moderators delegate creation and supervision of all tasks to fellowship program and Work Groups * KR: DevHub automatically requests KYC/KYB from integrated BOS-native service when needed * KR: DevDAO Trustees don’t need help from DevDAO Moderators