Re: Request for multiple mailing lists

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 7, 2008 at 12:41 PM, Vikram Ambrose
<Vikram.Ambrose@xxxxxxxxxxxxx> wrote:

> The SELinux list is not a place for non-SELinux maintainers, like Tresys to
> discuss their policies within themselves. Would it be alright for me and the
> other developers in my company to use the SELinux list to discuss our
> policies? Or the next company that decides to adopt SELinux? RedHat goes as
> far as to using the SELinux list as a communication channel with Tresys.
> Unless there has been some agreement made between the SELinux gatekeepers
> (NSA?) , Tresys and Redhat, I find this a misuse of the mailing list.

Some misunderstanding.  Tresys is the refpolicy maintainer.  The
intention of refpolicy is to be a single upstream policy on which
others can build, extend, and make their own changes.  Hopefully all
generically useful changes that people make to policy get sent back to
refpolicy.  We don't hear tresys discuss their custom policies, they
only talk about the general refpolicy, of which one of their employees
spends a great deal of maintaining for the benefit of us all.

> As I see it, the current list should be split into 3.

I'm willing to accept and think 2 lists is a good idea.  selinux-list
and selinux-policy-list.  Where selinux-list deals with anything that
comes along, be it userspace, kernel, my BLAH is broken, this tool
sucks, etc etc.  selinux-policy-list is for policy PATCHES ONLY.
There are some people who really follow both closely, but we do have
enough specialists who care 99% about policy those of us who care only
1% about policy.  Sure I'll subscribe to both, but I'm going to ignore
policy list.  I figure if any discussion comes up on policy-list that
needs userspace changes someone will poke me or they will mention it
on the general list.  I think moving policy patches and only patches
that need review to go into refpolicy onto its own list can help a
number of people better focus on things.  Chris can find those patches
without wading through crap and accept/reject them.  I can ignore
them.

My suggestion would be

selinux-list @ nsa - general selinux discussion including userspace
and kernel patches
selinux-policy-list @ whoever - PATCHES intended for refpolicy

-Eric

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux