From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mummy.ncsc.mil (mummy.ncsc.mil [144.51.88.129]) by tarius.tycho.ncsc.mil (8.13.1/8.13.1) with ESMTP id m77GsDUd010299 for ; Thu, 7 Aug 2008 12:54:15 -0400 Received: from mail.wrs.com (jazzhorn.ncsc.mil [144.51.5.9]) by mummy.ncsc.mil (8.12.10/8.12.10) with ESMTP id m77GsCbV017046 for ; Thu, 7 Aug 2008 16:54:12 GMT Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m77Gs1kh027378 for ; Thu, 7 Aug 2008 09:54:02 -0700 (PDT) Message-ID: <489B25B6.4080309@windriver.com> Date: Thu, 07 Aug 2008 12:41:26 -0400 From: Vikram Ambrose MIME-Version: 1.0 To: SE Linux Subject: Request for multiple mailing lists Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov The SE Linux mailing list is being cluttered with non selinux related material. Especially concerning refpolicy. And there is no set fast term used for filtering such content, and needless to say a waste of bandwidth. 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. In the last 4 months, there have only been a handful of unique threads concerning SELinux. A few by Stepehen, Eric, and myself. Everything else is policy related. With a total of 800 odd messages in this time frame, its quite clear the policy discussion is cluttering the list. As more and more people begin to adopt SELinux and face the battles of SELinux integration, the userspace topic will become increasingly popular. As I see it, the current list should be split into 3. 1. selinux-kernel This would be a very low volume list. .Perhaps even with special clearance to address security holes and concerns. 2. selinux-userspace This list would deal with userspace tools, wrappers and other non kernel related material. Whether it be NSA's userspace tools or support for 3rd party applications being compiled to be selinux-aware using libselinux. This list is very important, if not the most important of the three. 3. selinux-policy This list will deal with policies. A good place for Administrators and policy developers to discuss the creation, debugging and use of various policies. This as it stands would have the highest volume. Nevertheless as suggested by Grift Dominick on #selinux, a forum would be an even better place to discuss policies. Repository of ideas, designs and development dedicated to policies. A forum for the Administrator and Policy Developer. Without this breakdown, the selinux list would be analogous to people talking about GNU and C programming on lkml. Vikram. -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.