Hi,
We are a small team (<10) but we have to manage very different projects/products that are not related.
So we could have repositories with identical names in different projects, but again they are specific to each project. And support of legacy products avoid to make too many change.
Developers could switch from one project to another.
I tried to manage using group but it's became quickly an horrible nightmare.
So I imagine managing a team by product or product range.
I see the main benefits;
- the problem of redundancy of repository names disappears
- management of users and groups should be easier in each team
I see also some drawbacks;
- a user could be in different team, so I'll have to pay for him in each team.
- no way to share a group between different teams; that means in each team I''l have to create a group - often with the same name and add users and often the same ones.
Please let me know your experiences about teams management and the solutions you define.
Any helpful comment will be very welcome!
Thanks,
Philippe
