Giovanni Bricconi

Yep, you cannot easily keep all the sources in a single repository, and when you have many many of them it is easy to miss the one you need. Repos are usually organized in a pyramidal way, the main project and then inside many repos managed by the team. It is like they are tagged by team and not by purpose.

The pyramidal organization is easy to achieve, has the nice property that each element has just one parent, but you may have multiple concerns. You may want to group toghether project with labels. These repos are for deployment, these repos are for scheduling, these repos are for that project… the concerns may overlap one with another.

This make me think at the switch from tree organized mail into gmail organization where you have labels: at the beginning it is strange but in the end it simplifies the life.

This is definitively a whish I make to Atlassian guys, add labels to repositories, so that you can focus on related things, please do it.

Till then still relaying on the fact similar repo starts a bit with the same way, SPbla SPbli…