Until now, the task of uploading software to net-dist has been handled 
by a number of people across IS with no central coordination.  While the
problem with this approach was recently made glaring by the improper setup
of a specific package, that was only the most recent problem.  Other 
incidents have included uploads of packages to wrong directories, the 
use of archival software without proper licences, and distribution of
software without regard to export control laws.  Obviously this situation 
needs to be rectified.

A solution would be the creation of a small team, one or two people, who
would accept software packages for distribution from other IS teams, 
and make them available on net-dist in a manner consistant with
licence and other legal issues.  This team could also perform a final
check of configurations for appropriate information, and final virus scans 
before making the packages available.

This team would be the only ones with the actual access to upload packages.  
Requests would be made via email to netreq@mit.edu, which will insure 
tracing of requests via the discuss archive.  Requests will require the
following information: application information including name, function,
platform(s), necessary distribution restrictions (i.e. mit-only), group
responsible for maintainance, (--ANY OTHERS FOLKS?--).

As part of this effort, a decision as to the function of the Appleshare
net-dist server will also be required.  It would need to also come under
the control of the "net-dist team".  There has been some informal discussion 
of making the Appleshare server a bootstrap server, with a minimual set
of software, and keeping the bulk of software distribution on the ftp 
server.  This would address the version skew problems discussed in the 
net-dist reorganization team's report.

There have been concerns in the past about the need to have rapid access
to net-dist, so as to get applications rapidly to clients.  While this 
team would endevour to get software up as quickly as possible, it also
needs to address the issues outlined above, which the current "system" 
fails to do.