This is the internal wiki describing any information useful for the *development* of DIVE. Any information useful to the users to run DIVE should not be included here, but in the documentation within the code.
# Process description
We will be using a [Kanban-like agile process](Agile process) to run our hackathon. The process will be mainly managed from the issue board (click on Issues > Boards on the left menu to see this board). Issues will start on the left and generally move to the right of the board as we go through the design, development, and review phases.
## Project idea
The idea is to develop a graphical user interface to visualize the predictions of different diffusion models.
Find more info in the [project description](Project-idea.md)
## Process description
We will be using a [Kanban-like agile process](Agile-process.md) to run our hackathon. The process will be mainly managed from the issue board (click on Issues > Boards on the left menu to see this board). Issues will start on the left and generally move to the right of the board as we go through the design, development, and review phases.
The lifecycle of an issue will look something like the following. Each of these steps will be described in more detail below:
1. An issue is proposed
2. The issue enters the design phase during which the issue description is expanded
3. The issue enters the development phase during which somebody writes the code for this feature. Don't forget to add tests at this stage. This ends with a merge request.
4. The merge request is reviewed. Once accepted, the corresponding issues is marked as done.
5.*Optionally* a screenshot of the new feature is posted on slack
\ No newline at end of file
5.*Optionally* a screenshot of the new feature is posted on slack
## Reading resources
Along the way we collected a couple of usefulul links, the list which you can find [HERE](reading_resources.md).
