# Gno DevRel - 6 month OKRs - January - June

###### The following details OKRs proposed by the Gno DevRel team (Jon Roethke & Leon Hudak) with feedback incorporated from others via the [Gno DevRel OKR Miro board](https://miro.com/app/board/uXjVMj6DvrM=/).

## What is the purpose of the Gno DevRel team?
The purpose of the DevRel team is to:
- Document Gno.land, speak about Gno.land, write about Gno.land
- Develop Gno.land tools & libraries to make the experience of developers butter-smooth
- Develop apps to showcase the power of Gno.land
- Help the Core team test Gno.land & its features
- Raise awareness about Gno & Gno.land in order to bootstrap both the developer and end-user communities, ultimately bootstrapping Proof of Contribution

## How does Gno DevRel success look like?
In the eyes of the Gno DevRel team, success looks like this:
- Gno Developer experience is smooth:
- Stable & clear documentation
- Stable & plentiful dev tooling
- Easy setup, development, & deployment of Gno apps
- Easy debugging of Gno Code with understandable errors
- Gno.land is well known in Web3, Golang, & open-source communities
- Gno.land has a large dev & end-user community, most of which are (active) contributors and members of WorxDao, participating in Proof of Contribution
- Gno.land shows continuous growth as an ecosystem, attracting new development partners, contributors & validators

---
## **O1**: Establish baseline level of knowledge about what Gno.land is in the community
- ### KR1: Reference documentation (docs.gno.land) - how to use Gno.land
- Document `std` libraries (req. for mainnet)
- Document & refactor packages (`{p,r}/userland`)
- Document tools, CLIs, binaries (req. for mainnet)
- Document GnoVM
- Document TM2
- ### KR2: Context (ecosystem) documentation - how to understand the idea behind Gno.land
- Map of Gno.land (req. for mainnet)
- Reorganizing the monorepo, awesome-gno (req. for mainnet)
- Organizing the FAQ (req. for mainnet)
- Incorporating documentation feedback from community ([\#1505](https://github.com/gnolang/gno/issues/1505))
- ### KR3: Silver-platter content & tools - a compliation of reference & context documentation
- How-to guides, tutorials, video walkthroughs
- Expand on current offerings with emphasis on greater coverage + community-requested/demand-based content
##### **How-to Guides**:
- **Frequency:** 1/month
##### **Tutorials**
- **Frequency:** 1/month
##### **Video Tutorials**
- **Frequency:** 1 series/quarter

- Socials (eg, Blog posts, campaigns)
- Technical aspects of the project AND/OR demand-based/event-based content
- VM, TM2, tools, CLIs, packages, etc.
- **Frequency:** as-needed basis
##### Technical blog post:
- **Frequency:** 1/month; paired with engineer and/or appointment of technical writer

## **O2**: Increase overall engagement in Gno.land
- ### KR1: Prototyping
- [Dogfooding](https://github.com/gnolang/devrel/issues/24) to be the first users of Gno.land & its new features, providing feedback to the core, and showing the world what Gno is capable of
- Bettering dev experience (including partners/grantees) through changes in the monorepo & core
- ### KR2: Events, Talks, Meetups
- Attend events, hold talks, network, and make workshops in that are lead by the Marketing department
- **Frequency:** depends on marketing - needs discussion
- Organize mini engineering-focused meetups for the community around the world in sync with the Marketing department
- **Frequency:** 2-3 until end of Q2
- Dep: budget
- Infiltrating new developer communities (ie. open-source)
- Attending non-gopher & non-web3 conferences?

- ### KR3: Active engagement
- Engage with Partners/Grantees/Tinkerers
- Weekly syncs, on-demand syncs
- Incentivized builder retention (GoR, Bounties, etc.)
- Host Community Calls (owner: Michelle)
- Providing Core devleopment updates
- Host Office Hours
- **Frequency:** 1/month
- Host online workshops and hackathons/appathons
- **Frequency:** in-alignment with Marketing (eg, 1/quarter)
- Answering questions on various platforms (GitHub, Discord, Reddit, etc.)
- **Frequency:** depends on marketing - needs discussion
- <24hr response time

## **O3**: Easing developer experience through DevTooling
- ### KR1: Creating tools to track on-chain activity
- On-chain activity visualizers & trackers, like Mintscan's [Visualizations](https://www.mintscan.io/visualization)
- ### KR2: Developing a fast setup environment through DevPod
- Develop a simple-to-use setup system for the whole Gno.land development process
- ### KR3: Develop a faucet hub
- Milos's [proposal](https://github.com/gnolang/hackerspace/issues/53)

## O4: Develop DevRel Team Processes
- ### KR1: Establish + document processes
- Establish milestones/meta issues for all KRs for tracking purposes and visibility
- Implement weekly rituals for devrels (i.e. combing issues & PRs)
- Generate onboarding process for new DevRel team members & other tech hires

- ### KR2: Establish consistent reporting
- Generation & automation of reports
- Relaying the activity of the core team -> everyone (internal/external) + vice-versa

---
> Consider that additional OKRs will exist at both the team (regions: US, EU), AiB DevRel, and individual levels, and could be drafted in such a way to complement the OKRs of the greater DevRel team. Prioritization will be important; providing the basis of subsequent OKRs, serving as a type of roadmap of improvements to be addressed by the DevRel team as it continues to grow and improve its processes in perpetuity.