Jeff Spaleta (jspaleta@xxxxxxxxx) said: > We make it the responsibility of each SIG to take ownership of at > least one comps group definition and to keep it pruned, with feedback > from release-eng. Well, I'm not sure the Security SIG needs to own a group, nor are there enough SIGS for all the groups. But it's a good idea for things like KDE, GNOME, Games, etc. > The real question is how do we do that functionally. There is one > comps file right now. Do we > give a lot of people the authority to poke around inside that file. > I'm not sure I like that approach, I'd be afraid of inexperienced > people accidentally breaking the comps syntax, unless we can find a > way to toolize a syntax verifier as part of the check in process, like > what Jesse has suggested to me in irc. I'd just edit the file. Bill -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
