All of lore.kernel.org
 help / color / mirror / Atom feed
From: "richard offer" <offer@sgi.com>
To: selinux@tycho.nsa.gov
Subject: Re: Mirror Site
Date: Tue, 26 Dec 2000 14:18:44 -0800	[thread overview]
Message-ID: <1001226141844.ZM40057@sgi.com> (raw)
In-Reply-To: "Dabney, NathanX" <nathanx.dabney@intel.com> "RE: Mirror Site" (Dec 26,  1:18pm)


* $ from nathanx.dabney@intel.com at "26-Dec: 1:18pm" | sed "1,$s/^/* /"
*
*
* Last I checked, White River Junction, VT was still under jurisdiction of the
* US gov.  I don't think setting yourself up as a potential haven for runaway
* NSA code is a good place to start on this list.  Be glad you have the code
* and a chance to improve security with it and leave it at that.
*
* As far as the functionality you want to provide, I suggest having a look at
* the way sourceforge.org does it.  Hosting projects with them is free, simple
* and incredibly useful.  That and their code is GPL as well which would save
* you what looks like 2-3 years of development to catch up.
*
* Speaking of which, any reason selinux is not hosted on Sourceforge?  Anyone?

Lets give the project owners (NSA) the benefit of the doubt. The codes been
released what two (working) days and we want to move it to sourceforge already
?


It is vitally important (for internal potilical reasons) that any organisations
first open source project be seen to be a success.

Moving a project from the host site to a third party site after two days would
be seen as the project having failed in part of its goals (building involvement
between an organisation and the OS community).

[I'm speaking as a a long time open source developer, internal politics are the
same everywhere ]

There are reasons for moving the code to sourceforge.

  1) if the NSA do not want to be the gatekeeper.
  2) if the community wants features that the gatekeeper cannot/willnot provide
  3) if the gatekeeper has limited bandwidth/administrative personel.
  4) if the number of developers outside an organisation is such that the
internal developers are swamped just integrating patches.
  5) if the goals of the gatekeeper diverge from that of the community.

I don't see any of that happening for the time being.

*
* Enjoy,
* Nathan Dabney


Thanks to Peter and the rest of the team for releasing this...

richard.


-----------------------------------------------------------------------
Richard Offer          Widget FAQ --> http://reality.sgi.com/widgetFAQ/
{X,Motif,Trust} on {Irix,Linux}
__________________________________________http://reality.sgi.com/offer/

You have received this message because you are subscribed to the selinux 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.

  parent reply	other threads:[~2000-12-26 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-26 21:18 Mirror Site Dabney, NathanX
     [not found] ` <nathanx.dabney@intel.com>
2000-12-26 22:18   ` richard offer [this message]
2000-12-26 23:02 ` Douglas
  -- strict thread matches above, loose matches on Subject: below --
2000-12-26 21:48 Howard D. Holm
2000-12-26 22:56 ` Ben Johnson
2000-12-26 23:35 ` Grant Bayley
2000-12-30 19:34 ` RJ Atkinson
2000-12-26 20:33 Ben Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1001226141844.ZM40057@sgi.com \
    --to=offer@sgi.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.