---
# System prepended metadata

title: Developer Relations Roadmap

---



## The **big goals** for 2023

- Goal 0: Support engineering teams with Devrel needs (docs + user feedback)
- Goal 1: Build awareness and a developer community around Polymer +  OpenIBC with Polymer as one of the thought leaders
- Goal 2: Develop a Developer Relations/Adoption framework and start executing
    - Developer Hub (docs, community & support)
    - Content-marketing strategy (collab w Marketing)
    - Education & grants (OpenIBC)
    - Metrics
        - Developer Hub: site traffic
        - non-developer content: views and engagement
        - Twitter: engagement linked to specific actions/campaigns
        - Support: 24h follow up rate

Numerical:
- Testnet users
- Mainnet users (2024)
- no. of Projects integrating BD? conversions?
- $ raised by those projects
- no. of followers twitter
- no. of users on discord
- no. of packets sent on polymer
- no. of chains integrated with polymer

Future big goals, 2024: Developer adoption after mainnet launch

**Format**: Per milestone (aligned with engineering milestones) we'll have deliverables used for evaluation and underlying tasks for project managment.

- EA: Deliverable 1
    - Task 1
    - Task 2
- DR: Deliverable 2
    - Task 1
    - Task 2
    - Task 3
- ...

Where:
- EA == engineering alignment deliverables, potential blocker
- DR == devrel exclusive deliverables, not an (immediate) blocker

## Milestone 1: June 8th / ibc-sdk private testnet

Short turnaround, so focus on priorities. Priority here is to ensure xDapp developers have the docs & support they need to use the ibc-sdk in local development.

- EA: Docs IBC SDK:
    - [X] repurpose blog post & whitepaper for dev-focused Polymer protocol section
    - dev environment docs for:
        - [X] ETH
        - [X] WASM
        - [ ] ~~BSC~~ (no eng support)
    - [X] Quickstart tutorial (simple)
    - [X] IBCTL commands overview
    - [X] configuration file
    - [X] Readme polish
    - Stretch, moved to next milestone :
        - [ ] Quickstart Advanced (IBC SDK OSS milestone)
        - [ ] Advanced packet tracing and metrics (IBC SDK OSS milestone)

- EA: Set up comms channels
    - [X] Support channel (Discord)
    - [X] Feedback & feature requests (Discord)
- DR: Set up developer segmentation framework 
    - [X] [identify crude categories](https://www.notion.so/polymer-labs/e89989fcf4f5405eb591e4c32a08b796?v=152e8c1bbaf24c8396636e83698587f8)(xDapp dev, relayer op, validators)
    - [ ] more developed personas (stretch)
- DR: Develop [content marketing schedule](https://docs.google.com/spreadsheets/d/1M54oBfYnrRrQy_20Ccue3vqmI6sZOv5W_M5rOhir4kM/edit#gid=0) --> incentivized testnet
    - [X] Identify all components of Polymer architecture (cfr. whitepaper)
    - [X] Cross-reference with engineering roadmap
    - [X] Set up schedule to release content to keep engagement high
- DR: Get comfortable with IBC-SDK to demo at conferences
    - [X] Study protocol and IBC SDK CLI
    - [X] Make [diagrams](https://www.canva.com/design/DAFjQHtmZQY/SsIbiCy2hKsdNVF3h5BIUQ/edit?analyticsCorrelationId=e0bd3403-0073-41b5-b162-a8d27104f84d) to be used at conferences
- DR: Research into frameworks/best practices for DevRels (stretch)
    - [X] Research frameworks, industry leaders
    - [X] Distill and summarize to set up internal Framework
    - [ ] Kodemo etc.
    - [ ] Polish

## Milestone 2a: IBC SDK OSS

The IBC SDK OSS marks the genesis of the community building effort around Polymer/OpenIBC as it's the first publicly shared code developers can interact with. Feedback and support channels should be up and running.

- EA: Support & Feedback private testnet
    - Monitor comms channels, <24h response time
    - Answer or delegate support or feedback

- EA: Docs. Polish and extend
    - [X] Migrate docs to Docusaurus
    - [ ] Structure Docusaurus
    - [ ] Advanced quickstart (realistic DeFi)
    - [ ] contributor guidelines (IBC SDK)
    - ~~IBC SDK as a library~~
    - ~~document how to interact with UI dashboard/explorer~~

- DR: Execute content-marketing
    - Work with external creators and Gabe to have content aiming less at devs, more at decision makers, researcher
    - Set up pipeline for vIBC, zkMint, (multi-hop) content

- DR: Attend conferences
    - AwesomeWasm: workshop
    - Nebular Summit: product demo talk + workshop repo
    - Find ambassadors (3-7)


## Milestone 2b: Alpha testnet 
- EA: Docs
    - [ ] Find vIBC core smart contracts on supported testnets
    - [ ] vIBC deep dive
    - [ ] (Virtual) Light client development => OpenIBC (?)

- EA: Support & Feedback private testnet
    - Monitor comms channels, <24h response time
    - Answer or delegate support or feedback

- DR: Have developer hub strategy ready
    - Work with marketing on strategy
    - Research community platform (eg forem)

## Milestone 3: Beta testnet

- EA: Docs
    - [ ] Chain integration docs (?)
    - [ ] Validator docs

- DR: Developer Hub is ready with Docs, support forum
    - Research frameworks, industry leaders
    - Distill and summarize to set up internal Framework

- DR: Explore partnerships for education & grants program prior to mainnet:
    - Encode
    - B9lab
    - ~~WBA~~(talked to Jeff and they moved away from CW content)
- Incorporate testnet feedback

## Milestone 4: Mainnet / DevCon + EthDenver 2024

Show off our product: 
- chain launched (?)
- active developer community
- awesome developer hub
- IBC educational programs/grant programs in place

