On Thu, Jun 16, 2016 at 03:32:03PM +0200, Michał Górny wrote:
> On Thu, 16 Jun 2016 16:18:20 +0300
> Andrew Savchenko <birc...@gentoo.org> wrote:
>
> > On Thu, 16 Jun 2016 14:04:19 +0200 Michał Górny wrote:
> > > On Wed, 15 Jun 2016 21:11:30 +0200
> > > Michał Górny <mgo...@gentoo.org> wrote:
> > >
> > > > Right now we have the following components:
> > > >
> > > > - Applications,
> > > > - baselayout,
> > > > - Core system,
> > > > - Development,
> > > > - Eclasses and Profiles,
> > > > - Games,
> > > > - GCC Porting,
> > > > - GNOME,
> > > > - Hardened,
> > > > - Java,
> > > > - KDE,
> > > > - Keywording & Stabilization,
> > > > - Library,
> > > > - New packages ('New ebuilds' previously),
> > > > - Printing,
> > > > - SELinux,
> > > > - Server,
> > > > - Unspecified.
> > >
> > > Revision two:
> > >
> > > - Current packages [bug-wranglers@],
> > > - Eclasses [bug-wranglers@],
> > > - Hardened [hardened@],
> > > - New packages [bug-wranglers@],
> > > - Overlays [overlays@],
> > > - Profiles [bug-wranglers@],
> > > - SELinux [selinux@].
> >
> > Why hardened and selinux are separate?
>
> It's in the rationale, below. It may make sense to stage bugs through
> Hardened/SELinux teams since not all developers have access to
> Hardened/SELinux systems. If that's not needed, I'm happy to drop them.
Yes, on behalf of both Hardened and SELinux, please keep those
components.
The bugs can be a problem with the hardening or SELinux policy in which
case we just fix it without bothering the maintainer who probably doesnt
even have an selinux system to test the changes. Sometimes there is an
actual bug in the package in which case we can easily involve the
maintainer or assign to them completely.
-- Jason
