Skip to content

Department documentation tracking #35

@poroburu

Description

@poroburu

This issue tracks the progress of council departments onboarding their documents to the Juno Council repository.

What document parity is planned by each department, or required by the Charter?
If any of those documents are not to be uploaded to this repository. Please include a markdown file with either a policy or link to those documents.

For reference, the current department directory tree:

\COUNCIL\DEPARTMENTS
├───communications
│   └───rfp
├───development
│   ├───budgets
│   ├───events
│   │   └───Meeting
│   ├───policies
│   ├───procedures
│   ├───rfp
│   │   ├───001-Blockchain_Maintenance_Provider
│   │   ├───002-Chain_Upgrade_Support
│   │   ├───003-dApp_Development_Support
│   │   ├───004-Relayers_Activity_Support
│   │   └───005-Validator_Set_Support
│   └───templates
└───operations

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions