How the internship/thesis work is structured

You will work in a group: when you enter the project as a student you will work in a group with other students. At first you will begin to familiarize yourself with the working tools and the project, then later you will move on to small tasks (fixing small bugs, other changes) and finally, once you are “familiar” with the project and the working tools, you choose a specific topic that constitutes your internship/thesis work.

The work is organized as follows: each week we hold a “synchronization” meeting where we look at the work done and plan that for the following weeks. In the meeting, micro-tasks are then assigned, even more than one. From the moment you start working on a particular task, you must complete it within a week or two at the most, to avoid falling too far behind and having to start over again.

Each individual task, in order to be completed, goes under a “validation” phase called code review by those managing the project. This serves as a safety-net towards the students, to avoid inadvertently “damaging” an app that is already public. If there is any doubt about parts of the code, the reviewer will make comments and the student should check and possibly edit the code.

The internship (or thesis) is completed when the agreed-upon work is complete and sufficient, regardless of time and other factors (such as length), except for the minimums set by the secretary.

For work to be complete, it is necessary that, at the time of graduation application, all merge requests you are working on are joined to the main development branch (i.e., in Merged status) and you have no other issues assigned.

For information about the completion of the internship/thesis (procedures, etc.), see the Documents page.