Index: /trunk/doc/misc/modelSoftwareUsers.txt
===================================================================
--- /trunk/doc/misc/modelSoftwareUsers.txt	(revision 5065)
+++ /trunk/doc/misc/modelSoftwareUsers.txt	(revision 5065)
@@ -0,0 +1,58 @@
+o Public Software Distribution
+    - package source tarballs
+    - aggregate source tarball
+    - utility to install ps sources tarballs + external dependencies
+
+o Developer Software Distribution
+    - utility to install ps sources from CVS + external dependencies
+
+o Production Environment Control
+    - operating system specific software packages
+
+--
+
+Scenario #1) typical organizational end-user
+
+The user wants to use application x.y.z. that has a dependency on pslib.  Odds
+are that the end-user has no idea the application even has a dependency pslib,
+or any other library, as all they care about is the functionality of the
+application.  A support request is filed with the in house support agency.  A
+short period of time later (1+ months), a systems administrator will download
+x.y.z and discover the dependency on pslib look for the website.  The software
+(pslib) will be downloaded in tarball form, compiled, and installed on the
+system under /usr or /usr/local.
+
+Mode of distribution: www/tarball or www/rpm
+
+Scenario #2) unsupported organizational end-user w/o root access
+
+Same as Scenario #1 except that they will have to do the install themselves
+and into their home directory.  If they have had to do this sort of install
+before they are likely to be comfortable building from tarballs.  The faint
+can do the install with jhbuild. 
+
+Mode of distribution: www/mega-tarball, jhbuild/tarball
+
+Scenario #3) Gentoo end-user
+
+User types something along the lines of "sudo emerge -va pslib".  psmodule and
+other PS specific software is not likely to live in the portage tree but
+ebuilds will be provided on the PS website.
+
+Mode of distribution: portage or www/ebuild
+
+Scenario #5) Production server environment
+
+Gentoo admins would follow Scenario #3.  RedHat admins would download RPMs
+from the PS website.  Others would likely download the tarballs and possible
+build RPMs (from the include spec file) if their distribution is RPM based.
+
+Mode of distribution: www/tarball, www/rpm, portage, or www/ebuild
+
+Scenario #6) External application developer
+
+Mode of distribution: www/tarball or www/rpm
+
+Scenario #7) Internal/pslib developer
+
+Mode of distribution: cvs or jhbuild/cvs