Meta issue: a living map of the project's areas, who leads each, and the hot topics each area is driving. It is a coordination and transparency anchor. Each area leader owns their section.
For concrete PRs to review, test, or improve, check the Notable PRs by Area board. It is the canonical, always-current grouping of notable PRs by Main Area for org members. Set a PR's Main Area to surface it there.
Areas at a glance
| Area |
Label |
Scope |
Leader |
| VM |
a/vm |
GnoVM, security, runtime |
@thehowl |
| UX |
a/ux |
Product, marketing, community, UI, DevX |
@alexiscolin |
| Gnops |
a/gnops |
DevOps, valopers, netops, infra, monitoring, coordination |
@aeddi |
| Blockchain |
a/blockchain |
BFT, consensus, IBC, TM2 |
@tbruyelle |
| Gno.land |
a/gnoland |
Governance, strategy, facilitation |
@jaekwon · @moul |
Areas
Scope: GnoVM, security, runtime.
Hot topics
- Correctness and security.
- Gas and performance improvement.
Contributors: @ltzmaxwell, @omarsy, @Villaquiranm
Scope: Product, marketing, community, UI, DevX.
Hot topics
- User and namespace system.
- Product and famous dapps, including boards v2 and gnoswap.
- Content moderation.
- Marketing, frontend, docs, tutorials, onboarding.
- Improve individual and team contributor experience.
Contributors: @Kouteki, @gfanton, @zxxma, @jeronimoalbi, @notJoon, @jefft0, @davd-gzl
Gnops · @aeddi · a/gnops
Scope: DevOps, valopers, netops, infra, monitoring, coordination.
Hot topics
- Make hard upgrades testable, repeatable, and safe: halt-height, dry-runs, runbooks.
- Network integration tests, monitoring, and long-term tooling: tx replayer, gnoviser, explorer.
Contributors: @ajnavarro, @sw360cab, @D4ryl00, @louis14448
Blockchain · @tbruyelle · a/blockchain
Scope: BFT, consensus, IBC, TM2.
Hot topics
- IBC readiness.
- Consensus stability, security, and performance improvements.
Contributors: @julienrbrt
Scope: Governance, strategy, facilitation.
Hot topics
- Make the token transferable.
- Make the chain strong, secure, maintainable, and ready for production.
- Ship with IBC and a DEX.
- Make GovDAO decentralized enough.
- Make the chain used and valuable.
How we work
Each area has a leader who is responsible for understanding the full scope, making judgment calls, delegating work, following up, and facilitating reviews and merges.
Goals and tasks are defined collaboratively, discussed as a team, and then ratified. Each area is then responsible for making them happen. Task allocation is based on availability and coordinated with Nemanja, who maintains the shared assignment view so everyone can plan day to day.
Maintaining this issue
- Areas, labels, and leaders mirror the
a/* labels and a-* GitHub teams.
- The Notable PRs by Area board is the source of truth for concrete PRs to review, test, or improve.
- Area leaders: please update this issue when your area changes.
- Area leaders: feel free to create your own meta issue for your area and link it from this issue.
Meta issue: a living map of the project's areas, who leads each, and the hot topics each area is driving. It is a coordination and transparency anchor. Each area leader owns their section.
For concrete PRs to review, test, or improve, check the Notable PRs by Area board. It is the canonical, always-current grouping of notable PRs by
Main Areafor org members. Set a PR's Main Area to surface it there.Areas at a glance
a/vma/uxa/gnopsa/blockchaina/gnolandAreas
VM · @thehowl ·
a/vmScope: GnoVM, security, runtime.
Hot topics
Contributors: @ltzmaxwell, @omarsy, @Villaquiranm
UX · @alexiscolin ·
a/uxScope: Product, marketing, community, UI, DevX.
Hot topics
Contributors: @Kouteki, @gfanton, @zxxma, @jeronimoalbi, @notJoon, @jefft0, @davd-gzl
Gnops · @aeddi ·
a/gnopsScope: DevOps, valopers, netops, infra, monitoring, coordination.
Hot topics
Contributors: @ajnavarro, @sw360cab, @D4ryl00, @louis14448
Blockchain · @tbruyelle ·
a/blockchainScope: BFT, consensus, IBC, TM2.
Hot topics
Contributors: @julienrbrt
Gno.land · @jaekwon · @moul ·
a/gnolandScope: Governance, strategy, facilitation.
Hot topics
How we work
Each area has a leader who is responsible for understanding the full scope, making judgment calls, delegating work, following up, and facilitating reviews and merges.
Goals and tasks are defined collaboratively, discussed as a team, and then ratified. Each area is then responsible for making them happen. Task allocation is based on availability and coordinated with Nemanja, who maintains the shared assignment view so everyone can plan day to day.
Maintaining this issue
a/*labels anda-*GitHub teams.