On 09/27/14 17:35, Tom Wijsman wrote:
On Sat, 27 Sep 2014 06:25:28 -0400
Rich Freeman <ri...@gentoo.org> wrote:
On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers <j...@gentoo.org>
wrote:
Right now, CC'ing a single alias is inconvenient, but under your
proposal, you might need to CC a dozen or more people instead of
that alias.
That is incorrect. Herds would be replaced with projects, not with
lists of individual (non-)maintainers.
I don't think that anybody thinks that having groups of devs isn't
useful. The problem is that we have two different mechanisms for
having groups of people, and one of them seems to make more sense than
the other.
Answer this: 5 developers want to maintain a group of packages
together. Should they form a herd, or a project? Under what
circumstances should they choose one vs the other?
I don't think the distinction is particularly useful, and projects at
least have a straightforward governance model.
--
Rich
Herds cannot be replaced by projects, because projects can contain
multiple herds; iotw, there's no one-to-one mapping between them.
The hardened project has two herds: hardened and hardened-kernel, the
former for toolchain related stuff and the latter for the kernel. We
really need to keep that distinction. So mapping herds to projects
doesn't work. But, mapping hardened/hardened-kernel to our
*subprojects* structure does. Perhaps that might be a more natural
solution in general, not just for hardened.
We might proceed by associating each herd to a project, and then letting
them decide whether to absorb the herd(s) into their project level, or
break it down to subprojects. So as another example, ppc and ppc64
teams are merging into one team (powerpc) with one lead (currently
jmorgan). There also we want to keep two herds for the two different
arches for keywording/stabilizing requests. If we just say "ppc and
ppc64 herds belong to powerpc team", then it will be easy to change
"herd" to "subproject" requiring nothing more than just a webpage put up
if it doesn't already exist.
I don't think having multiple mechanisms to form groups is a problem;
from my previous paragraph, it becomes clear that it is a solution.
Answer: The project model has some concepts that herds do not have.
I don't think discussing this is useful, projects are documented.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
