Working Group notes & documents
Feel free to add any additional pages and whiteboards for internal use as sub-pages here.
Communication Channels
Slack
for ad-hoc, immediate communication
Confluence
to collect ideas, tasks and early drafts
GitBook
for official specs and formal revisions
Weekly Video Call
Structure of Confluence Workspace
Some confluence documents are linked to from the official GovStack specs as annexes (see
10 Other Resources | bb-digital-registries ). We keep these documents and the top level within the “Digital Registries” section of Confluence.
Internal drafts, notes and documents for the Working Group can be freely added within subpages of the https://govstack-global.atlassian.net/wiki/spaces/GH/pages/1413316637/Processes+Communication+in+Registries+Working+Group?atlOrigin=eyJpIjoiNDE2Yjk4MmU1MGU2NDI3NjhhZTQwMGYzNjI4ZWM5OTUiLCJwIjoiYyJ9 section.
Small corrections and final drafts of specifications will be done directly in GitBook
For initial work in progress and drafts in discussion, you can use the pages of the https://govstack-global.atlassian.net/wiki/spaces/GH/pages/1438253066 here on Confluence
Process to revise the current BB specifications:
We are using Jira tasks to organize our work: https://govstack-global.atlassian.net/jira/software/c/projects/DR/boards/30/backlog
The person in the primary/lead role for a section is assigned to the “Revise Section X …” (e.g. https://govstack-global.atlassian.net/browse/DR-133 is assigned to @Dr. Bimal kumar )
Any additional supporting people can list/mention themselves in the description of the Jira task:
All people revising a section of the specification read through the current version in GitBook (“Development” branch): GitBook: Digital Registries - Development
Comment any problems, questions or improvements directly in GitBook:
We will discuss the comments as a team and then create tasks to actually implement the changes, which will be assigned to one team member then.