Agree upon a new workflow

[micnekr]

Create a workflow so that we can make meaningfully fast progress with the larger team.

Current issues:

The OxArm project isn't well-organised at the moment: we only have a rough outline of what the modules are supposed to do and how they will interact. Moreover, because people frequently leave and join the club, a lot of decisions on how the different parts of the project work were made by people no longer on the team, and newcomers (and the rest of us, frankly) would find it hard to deal with some of them.

This makes it difficult to track progress, see what the next important steps in the projects are and see at what stage we currently are. We also need to know what tasks have been accomplished and what issues are present (especially issues spanning multiple modules), so that we can fix them without making people working on one piece of code wait for others.

[micnekr]

Proposition:

We maintain a list of small tasks that we need to work on and assign them to people. Here is the rough structure I am proposing:

1. Someone encounters or bings up an issue. Please only bring up issues if

• This issue is complex enough that you need assistance from others
• Or you think others would benefit from knowing the solution (e.g. VMs don't detect the USB camera)
• Or it is a proposal for changing something about a project, a proposal for a piece of work to be done, or any other concern

2. They write a card in "proposed tasks" column with the title explaining what needs to be done. The description can be used to add extra details. They assign themselves and the people who would be affected by the outcome(or if the change affects a lot of people, just the subteam leaders).

3. These people then discuss the card. If the people decide to not implement the suggestion, move it to "Rejected". If the issue is quick to resolve, write down the solution in the description and move the card to "Done" column.

4. Otherwise, if the card is difficult to resolve, it can be moved to "in progress". Then, someone might start implementing it or a meeting can be held about it. Please record outcomes of the meeting in the description.
   For difficult cards, one can open an issue from a card to let multiple people add comments about it. When opening an issue related to code, please put it under RobotArmPackages repository, and if it is related to anything else (e.g. management or CAD), use RobotArm

The design goals for this system are:

1. To record all the decisions that happened so that even if members of the team leave, we know why certain decisions were made
2. Involves most of the people affected by a decision in the discussion
3. Avoid escalating most of the problems all the way to the team leader; for example, issues that relate just to the internals of a package are solved by the people working on the package.

Separately, to make sure that we are using peoples' time efficiently, I am suggesting that we focus on prototyping: It is better to make things work decently and then polish them once we have something to present.

[micnekr]

How to contribute to project:

Reference for the "feature branch" model

1. Convert a card into a github issue for the corresponding repository (usually RobotArmPackages2)
2. Create and switch to a branch based on the main branch in the repository named after the issue number (e.g. 4).
3. Create the changes; once you are ready, submit a pull request
4. We will then go over it and check the commits, potentially asking you to make minor changes
5. Other team members are free to add changes in the same branch - this will update the pull request. Don't forget to git pull and git push frequently!
6. We will then accept pull request and squash the commits