That was also my comment on the charter. Projects should be able to setup multiple repos for their scope, e.g. code, documentation, ... and for multiple components separately managed in repos.
Thanks, Bryan Sullivan | AT&T -----Original Message----- From: SPATSCHECK, OLIVER Sent: Friday, April 21, 2017 8:47 AM To: Christopher Donley (Chris) <Christopher.Donley at huawei.com> Cc: Dhananjay Pavgi <DP00476350 at TechMahindra.com>; Stephen Terrill <stephen.terrill at ericsson.com>; SULLIVAN, BRYAN L <bs3131 at att.com>; onap-tsc at lists.onap.org; Ed Warnicke <eaw at cisco.com> Subject: Re: [onap-tsc] Updated TSC Charter I have another question on the charter. I just noticed that a project (or sub project) and a repo are the same thing. I find this to be sub optimal. In my mind a project is a well defined scope of work. A repo has to do with how to optimize my code management. Am I the only one with the concern that binding the two will force people into sub optimal repo structures? Thx Oliver
