[Olsr-dev] [Olsr-commit] OLSR.org main repository branch, GSOC, updated. OLSRD_0_6_1_fixed-33-gd7b6715

[Ferry Huberts]

On 07/28/2011 07:33 PM, L. Aaron Kaplan wrote:
> 
> On Jul 28, 2011, at 11:31 PM, Ferry Huberts wrote:
> 
>>
>>
>> On 07/28/2011 07:28 PM, L. Aaron Kaplan wrote:
>>> (...)
>>>>>
>>>>> What could be the worst thing happening ? Someone manages to remove all 
>>>>> branches from our git repository. I get the mail, have some work and just put 
>>>>> up a fresh repository from my mirror at git.hrogge.de.
>>>>>
>>>>> After this I would have some more work to implement a write commit ACL system 
>>>>> on our webpage (Most likely one that look at the bugtracker to see if the 
>>>>> commiter has write access).
>>>>>
>>>>> But I really see no purpose to do it now.
>>>>>
>>>>
>>>> ok fair enough.
>>>>
>>>> I'll adjust ;-)
>>>>
>>> Ferry how would you adjust?
>>
>> adjust == accept :-)
> 
> Hehe, ok. But do you have any better idea how to prevent backdoors?
> It is actually IMHO a quite interesting discussion...
> 
> The only way I could think of is to have really thorough independent code reviews.
> 


I think it's much easier: limit commit access to trusted people. much like
the kernel and many other projects do.

more review is just extra and is probably too much for olsrd, at least for
the moment.


The main developers do not want to limit commit access so maybe not keep
this discussing alive, unless they pipe in themselves :-)



grtz

-- 
Ferry Huberts