On 10/04/2017 09:33 AM, Emmanuel Lécharny wrote:
>> So separate git repos for
>> - project
>> - apacheds
>> - studio
>> - jdbm
>> - mavibot
>> makes sense.
> 
> +1. I would let aside jdbm, as we are very unlikely to modify it as soon
> as Mavibot will be ready.

Ok. I won't start a separate vote I think there is consensus :)

>> But does it make sense to create a separate repos for all the helper
>> projects (checkstyle-configuration, junit-additions, skins, docker)? Or
>> should we move them into a common repo. Currently they anyway live
>> within a common "buildtools" folder [1]
> 
> +1 for buildtools.

Ok.

>> We drop the apacheds-manuals and ldap-api-manuals because those manuals
>> are now maintained in the CMS, right?
> 
> correct.
>>
>> What about kerberos-client? There is no change since 2008 and Kerby took
>> over, right?. I'd rather move it to our "deceased" folder.
> 
> Leave it where it is (ie, svn).

> Side note : give me up to the end of this week so that I can commit some
> pending changes I have for various projects, before reqesting the migration

Sure take your time, I won't start before the weekend.

Reply via email to