Arrange a time when you can meet everyone in your group. (Some people may participate remotely.)
Introduce yourselves, and discuss how you are going to carry out the group (lab) exercises:
What are your skills and strengths? The mini-projects will require a combination of skills: knowledge of open source software projects, usage of many tools (for revision control, building software, testing, quality assurance), understanding requirements, documentation, mining bug/issue trackers, knowledge of theory, etc.
How do you want to communicate? In person, by e-mail, chat, slack?
How will you keep track of open tasks?
How do you plan to work? You can use two lab computers with pair (or triple) programming, your own environment, etc. Note that two thirds (2/3) of the work will be carried out outside supervised and planned lab sessions!
How will you write the documentation? (Any tool that produces a PDF in the end is fine with us.)
Is there anyone who cannot be present in lab sessions? How do you compensate for this? (This is particularly important for the final session in each mini-project).
Agree on a code of conduct relating to the items stated above, in particular to possible absences in the lab session.
Upload a short text document listing all team members and their skills, and the decisions you have made regarding the criteria above. This assignment is mandatory but will not count towards higher grades (pass or fail only).
Can't change a rubric once you've started using it.