Hi everyone,
here's a little heads up.
For the next five weeks, students from Freie Universität Berlin will contribute
to the Saros project.
Last week was their introduction week (you might have noticed in Gerrit the many
small patches that deal with SonarQube issues).
This is how this whole project works:
- Eventually, the students will provide patches that should be integrated into
the normal Saros code base, i.e. the master branch of the saros repository.
Those are the patches I encourage everyone to review.
- For preparing those "final" patches, the student team has a repository of its
own called "saros-swtp2016".
It's up to them whether they create patches for the normal "saros" repository
directly (as they did for the micro-patches of the introduction week), or
whether they want to play around first without the need to comply with Saros'
high standards regarding internal code quality.
This works as follows:
- The students start creating patches towards a certain end, e.g. a small
feature.
- This is software development with very little knowledge about the code
base, so many things are likely to be tried out until a viable solution has
been found.
- They will review the changes among themselves until they reach a level of
common agreement.
- Eventually, after a feature took maybe 7 patches to be complete, the
students take a step back and create a streamlined version of their
changes, maybe split into 2 patches which only reflect the effective
changes, and not every detour along the way.
(This is more or less how you might work on your own, at least that's what
I do: I create commits with a very small granularity and afterwards
reorder, change, and squash them to a much shorter series of changes.)
- The team decided to make their sandbox visible or everyone, i.e. you can
read their patches and provide comments if you like and if you can spare
the time.
- The project participants are free to incorporate or to ignore your comments
in their sandbox.
That's why non-student-project developers don't have a "Code-Review" vote
on these patches.
- Eventually, the students will need to create patches for the normal saros
repository.
Again, *those* are the patches you should focus your attention on.
We will see how this works out in the first week.
Cheers,
Franz
------------------------------------------------------------------------------
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
