Start to rework exec summary

dosp-survey.ltx

@@ -36,13 +36,17 @@ license.\footnote{Note that this definition deliberately does not
   Netscape Navigator source code, which through further development
   eventually became Mozilla Firefox, is \emph{not} an example of DOSP.
   This report is examines the history and effects of DOSP practiced as
-  a conscious strategy; the effect of unplanned and unpredicted open
+  a conscious strategy; the effect of unplanned or unpredicted open
   source publication is also an interesting topic, but a separate
   one.}
 
-Software producers have practiced DOSP throughout the history of free
-and open source software.\footnote{We use the terms ``free software''
-  and ``open source software'' synonymously throughout this report.}
+Software producers have practiced DOSP throughout the history of free and open
+source software.\footnote{We use the terms ``free software'' and ``open source
+software'' synonymously throughout this report.} This document is a selective
+survey of that history.  It collects and categorizes sample products and tries
+to identify some trends.
+
+
 However, surveying this phenomenon at a high level, from its
 beginnings through today, shows some clear trends:
 
@@ -76,6 +80,7 @@ beginnings through today, shows some clear trends:
     "as soon as we find the right non-profit home for it", etc.
     Probably includes bounty mechanisms, but only if these were
     intended --- that is, not ``buy-outs".
+
 \emph{James thinks this is also not really DOSP in the same sense,
 although it's a category that quite a few people wrote in about.}
 
@@ -87,6 +92,42 @@ eventually decide to do so.  These aren't technically in scope, but we
 should give some examples somewhere --- maybe in a footnote or
 appendix --- just to make it clear that it's something that happens.
 
+DOSP approaches belong to a class of approaches and licenses that sit somewhere
+between traditional proprietary approaches and full-fledged FOSS licenses that
+meet the OSI Definition.  These models of software release, which we might call
+"public collaboration" models, are often quite similar (or even based on)
+traditionally recognized FOSS practices.  They are designed to foster public
+collaboration and distributed development, just like FOSS.  But unlike
+traditional FOSS, they tend to apply some additional restrictions that restrict
+collaboration.
+
+These restrictions vary based on the business or social goals of the software
+effort.  In some cases, as here, we see time delays (mostly used to provide a
+period of exclusive commercial exploitation) and in others, we see field-of-use
+restrictions.  FOU restrictions may also be used to protect commercial
+interests, but are also commonly designed for social goals.\footnote{See the
+Organization For Ethical Source at \otsurl{https://ethicalsource.dev/licenses/} and the
+Anti-996 License at \otsurl{https://github.com/996icu/996.ICU/blob/master/LICENSE} for
+two contemporary efforts that use public collaboration licenses to exclude what
+they see as socially harmful usage of collective labor.}  In either case,
+though, the intended effect is market segmentation.  DOSP segments the market
+into a group of public, FOSS particpants and a set of companies willing to pay
+for the latest features and proprietary use.  Ethics-focused FOU licenses
+segment the software's audience into a group of FOSS-like, public collaborators
+and a set of actors who do not meet the social standards of the software
+creators.  In both cases, the aim of the public collaboration license is
+exclusive exploitation to advantage one group and not the other. 
+
+Just as FOSS shook out into a handful of licenses that are used by the vast
+majority of projects, we might be seeing a convergence toward a recognizable set
+of DOSP licenses. It is too soon to know for sure if the current options will
+settle in as the standard.  The list of most-used FOSS licenses has been quite
+stable for over a decade now, and there is little reason to think it will
+change any time soon.  With DOSP licenses, though, it is possible we are still
+in a period of experimenation. Today's handful of commonly-used licenses may
+just be a precursor to tomorrow's recognized standard.
+
+
 \numberedsection{Early History}
 
 For many years, Aladdin GhostScript implemented a DOSP policy whereby