On Sat, 27 Sep 2014 06:25:28 -0400 Rich Freeman <[email protected]> wrote:
> On Sat, Sep 27, 2014 at 4:58 AM, Jeroen Roovers <[email protected]> > 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. 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.
