Working Groups & Architecture Review Process

[clevinson]

All feature development for the SDK is intended to happen in the context of Working Groups. These working groups spin up to own a pre-defined user need, or high-level feature request and follow a process of meeting regularly to move the feature along from design to implementation to QA. The working group is not the sole responsible entity for all components of a feature development & release cycle, but they are the group responsible for a features final delivery, and satisfying the original defined requirements.

Active Working Groups

Working Group	Discussion	Members	Status	Epics (if in implementation phase)
Gov & Group Module	#9066	@blushi (R) @aaronc (D) @cmwaters (I) @hxrts (U)	IMPLEMENTATION	Gov/Group Module Alignment (#9438), Add Group Module (#7633)
Module Wiring	#9182	@aaronc (I), @robert-zaremba (R), @blushi (R), @fdymylja, @fadeev (U), @jgimeno, @marbar3778, @alexanderbez	PAUSED	#9773
Protobuf golang v2 codegen	#7488	@technicallyty (I), @fdymylja (I), @AmauryM (R), @ruhatch, @aaronc (D), @marbar3778	IMPLEMENTATION	#7488
NFT Support for SDK	#9065	@okwme (D), @aaronc (R), @robert-zaremba (R), @haifengxi (I)	IMPLEMENTATION	#9826
Tx Improvements	#9406	@aaronc (R), @AmauryM (I), @cyberbono3 (I), @atheeshp (I)	IMPLEMENTATION	#9557
SMT MIgration		@robert-zaremba	IMPLEMENTATION	SMT Migration (#9816), Multistore Deprecation (#9818)
Postgres Indexing		@robert-zaremba @i-norden @aaronc	IMPLEMENTATION	#9817
ORM Framework		@aaronc @fdymylja	DESIGN, IMPLEMENTATION	#9815
Consensus Fees	#8224	@robert-zaremba (R), @hxrts (U)	PAUSED	#9962 #9963
x/upgrade, Cosmovisor Improvements	#9928	@robert-zaremba (I) @aaronc (R) @anilcse (R) @iramiller (D) @clevinson	IMPLEMENTATION	#9869
x/auth, x/bank, vesting re-design	#8528	@aaronc (D), @cyberbono3 (I), @AmauryM (R)	PAUSED	#9690 #7091 #9958 #9959 #7113
x/staking Improvements / Independence	#8328	@zmanian (D), @marbar3778 (I)	IMPLEMENTATION	#9935
Decimal Improvements	#7773	@aaronc	DESIGN
SIGN_MODE_TEXTUAL	#6513	@aaronc @AmauryM	DESIGN	#10251
ABCI++ Notes		@aaronc, @marbar3778, @aaronc (D)	DESIGN

Roles:

• Design Support (D): Consulted on design, and potentially actively contributing to design process. Not expected to do work outside of meetings.
• Implementors (I): Expected for writing code, ADRs, documentation
• Reviewer (R): Review design & implementation phase.
• User Stakeholder (U): Attend meetings, give feedback live in meetings. Not expected to do work outside of meetings.

Architecture Review Calls

The Cosmos SDK Core Team hosts bi-weekly Architecture Review calls on alternating Fridays at 4pm CET / 10am ET / 7am PT. These calls are an opportunity to discuss pending ADR's and host architectural conversations that warrant a longer discussion. These meetings start with status updates from any Working Groups that have epics in the DESIGN stage. The rest of the agenda is set aside to discuss any issues tagged with the Status: Needs Architecture Review label.

Notes are take on HackMD, and are archived on our Wiki Page for wider visibility.

[clevinson]

Closing this issue as we've migrated archiving of Architecture Review notes to a wiki page.

[aaronc]

Locking this as it's not intended as a discussion thread, but rather as a pinned tracking issue.

[robert-zaremba]

Would be good to link meeting notes. For example, in SMT we have a rolling meeting notes hackmd - but we would need to work on edit permissions.

[hxrts]

Would be good to link meeting notes.

Yes please!!

[tac0turtle]

Could we add a section for expected delivery version. Its hard to gauge off the list when things will be delivered.

[hxrts]

Still a little unclear if the working groups page on the wiki is being updated. If not, can we remove that section or have it link back here? https://github.com/cosmos/cosmos-sdk/wiki/Architecture-Design-Process#working-groups

[clevinson]

Just updated - thx @hxrts !

[julienrbrt]

Closing this issue as we migrated to GitHub Projects.