Development/Dataworker-Development-Workflow.md

+---
+summary: Development workflow for dataworker tasks
+maintainer: Antoine
+status:
+note:
+---
+
+
+Dataworker development flow takes place in the wiki and the issue tracker. The
+roadmap section in the dataworker homepage of the wiki lists all subjects in the
+development pipeline, from first discussion to validation.
+
+- [Dataworker Home Page](Development/DataWorker-Home)
+- [Dataworker Issue Tracker](https://gitlab.com/prospect-energy/prospect-server/-/boards/5718325?label_name[]=dataworker)
+
+# Flow
+
+> We no longer use the `proposal` status. We use instead new tickets without
+> status.
+
+## Discussion
+
+If the subject is complex, we start with a discussion page that describe the
+context of the issue, the issue, and direction for a solution. We link the
+discussion in the [Dataworker Home Page](Development/DataWorker-Home).
+
+## Open issue ticket
+
+Once the discussion leads to a design decision, we can start creating issue in
+the issue tracker, using the `dataworker` tag. New dataworker issues are visible
+in the [Dataworker Issue
+Tracker](https://gitlab.com/prospect-energy/prospect-server/-/boards/5718325?label_name[]=dataworker)
+in the `Open` column.
+
+## Ready to start
+
+Once tickets are correctly specified and agreed upon, we can tag them with
+`status:ready-to-start`, or slide them in the dashboard column for the same
+effect.
+
+## Current sprint
+
+An extra step for ready tickets, that should be picked up in priority.
+
+
+## In progress
+
+Someone is already working on it.
+
+## Validation
+
+The ticket is being reviewed, or deployed in staging and manually tested, or
+actively monitored.
+
+## Closed
+
+Once an issue fix is validated, we can close it, and it will no longer be
+visible in the issue dashboard. Before closing we change manually the status
+from `validation` to either `done` or `canceled`, to avoid the unclarity of a
+ticket both closed and with a `validation` label.
\ No newline at end of file