On Tuesday 24 February 2015 22:49:30 Uze Choi wrote: > I have a negative opinion for sharing the responsibility across different > technical domain. We can check the something wrong and comment > about something wrong but approval is different issue. Maintainer of his > technical area only can judge the code is aligned to the philosiphy and the > concept of that tech domain.
It's clear that there's a single Maintainer for each file[*]. We should also try and organise ourselves so that there's a single Maintainer per directory too. But how does that affect the discussion? I'm missing something, I think. [*] exception is security, since the security maintainer has project-wide responsibilities. Whenever a change affects the security solution, the security maintainer should have a say, regardless of which files were modified. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
