fUnit 0.0.2 → 0.0.3

data/COPYING

@@ -1,79 +1,81 @@
-NASA OPEN SOURCE AGREEMENT VERSION 1.3
+= Copying
 
-THIS OPEN SOURCE AGREEMENT ("AGREEMENT") DEFINES THE RIGHTS OF USE,
-REPRODUCTION, DISTRIBUTION, MODIFICATION AND REDISTRIBUTION OF CERTAIN
-COMPUTER SOFTWARE ORIGINALLY RELEASED BY THE UNITED STATES GOVERNMENT
-AS REPRESENTED BY THE GOVERNMENT AGENCY LISTED BELOW ("GOVERNMENT
-AGENCY").  THE UNITED STATES GOVERNMENT, AS REPRESENTED BY GOVERNMENT
-AGENCY, IS AN INTENDED THIRD-PARTY BENEFICIARY OF ALL SUBSEQUENT
-DISTRIBUTIONS OR REDISTRIBUTIONS OF THE SUBJECT SOFTWARE.  ANYONE WHO
-USES, REPRODUCES, DISTRIBUTES, MODIFIES OR REDISTRIBUTES THE SUBJECT
-SOFTWARE, AS DEFINED HEREIN, OR ANY PART THEREOF, IS, BY THAT ACTION,
-ACCEPTING IN FULL THE RESPONSIBILITIES AND OBLIGATIONS CONTAINED IN
-THIS AGREEMENT.
+ NASA OPEN SOURCE AGREEMENT VERSION 1.3
 
-Government Agency: NASA Langley Research Center
-Government Agency Original Software Designation: LAR-17081-1
-Government Agency Original Software Title: fUnit
-User Registration Requested: please see clause 3.F.
-Government Agency Point of Contact: funit-support@rubyforge.org
+ THIS OPEN SOURCE AGREEMENT ("AGREEMENT") DEFINES THE RIGHTS OF USE,
+ REPRODUCTION, DISTRIBUTION, MODIFICATION AND REDISTRIBUTION OF CERTAIN
+ COMPUTER SOFTWARE ORIGINALLY RELEASED BY THE UNITED STATES GOVERNMENT
+ AS REPRESENTED BY THE GOVERNMENT AGENCY LISTED BELOW ("GOVERNMENT
+ AGENCY").  THE UNITED STATES GOVERNMENT, AS REPRESENTED BY GOVERNMENT
+ AGENCY, IS AN INTENDED THIRD-PARTY BENEFICIARY OF ALL SUBSEQUENT
+ DISTRIBUTIONS OR REDISTRIBUTIONS OF THE SUBJECT SOFTWARE.  ANYONE WHO
+ USES, REPRODUCES, DISTRIBUTES, MODIFIES OR REDISTRIBUTES THE SUBJECT
+ SOFTWARE, AS DEFINED HEREIN, OR ANY PART THEREOF, IS, BY THAT ACTION,
+ ACCEPTING IN FULL THE RESPONSIBILITIES AND OBLIGATIONS CONTAINED IN
+ THIS AGREEMENT.
 
-1. DEFINITIONS
+ Government Agency: NASA Langley Research Center
+ Government Agency Original Software Designation: LAR-17081-1
+ Government Agency Original Software Title: fUnit
+ User Registration Requested: please see clause 3.F.
+ Government Agency Point of Contact: funit-support@rubyforge.org
 
-A. "Contributor" means Government Agency, as the developer of the
-Original Software, and any entity that makes a Modification.
+ 1. DEFINITIONS
 
-B. "Covered Patents" mean patent claims licensable by a Contributor
-that are necessarily infringed by the use or sale of its Modification
-alone or when combined with the Subject Software.
+ A. "Contributor" means Government Agency, as the developer of the
+ Original Software, and any entity that makes a Modification.
 
-C. "Display" means the showing of a copy of the Subject Software,
-either directly or by means of an image, or any other device.
+ B. "Covered Patents" mean patent claims licensable by a Contributor
+ that are necessarily infringed by the use or sale of its Modification
+ alone or when combined with the Subject Software.
 
-D. "Distribution" means conveyance or transfer of the Subject
-Software, regardless of means, to another.
+ C. "Display" means the showing of a copy of the Subject Software,
+ either directly or by means of an image, or any other device.
 
-E. "Larger Work" means computer software that combines Subject
-Software, or portions thereof, with software separate from the Subject
-Software that is not governed by the terms of this Agreement.
+ D. "Distribution" means conveyance or transfer of the Subject
+ Software, regardless of means, to another.
 
-F. "Modification" means any alteration of, including addition to or
-deletion from, the substance or structure of either the Original
-Software or Subject Software, and includes derivative works, as that
-term is defined in the Copyright Statute, 17 USC 101.  However, the
-act of including Subject Software as part of a Larger Work does not in
-and of itself constitute a Modification.
+ E. "Larger Work" means computer software that combines Subject
+ Software, or portions thereof, with software separate from the Subject
+ Software that is not governed by the terms of this Agreement.
 
-G. "Original Software" means the computer software first released
-under this Agreement by Government Agency with Government Agency
-designation NASA and entitled fUnit, including source code,
-object code and accompanying documentation, if any.
+ F. "Modification" means any alteration of, including addition to or
+ deletion from, the substance or structure of either the Original
+ Software or Subject Software, and includes derivative works, as that
+ term is defined in the Copyright Statute, 17 USC 101.  However, the
+ act of including Subject Software as part of a Larger Work does not in
+ and of itself constitute a Modification.
 
-H. "Recipient" means anyone who acquires the Subject Software under
-this Agreement, including all Contributors.
+ G. "Original Software" means the computer software first released
+ under this Agreement by Government Agency with Government Agency
+ designation NASA and entitled fUnit, including source code,
+ object code and accompanying documentation, if any.
 
-I. "Redistribution" means Distribution of the Subject Software after a
-Modification has been made.
+ H. "Recipient" means anyone who acquires the Subject Software under
+ this Agreement, including all Contributors.
 
-J. "Reproduction" means the making of a counterpart, image or copy of
-the Subject Software.
+ I. "Redistribution" means Distribution of the Subject Software after a
+ Modification has been made.
 
-K. "Sale" means the exchange of the Subject Software for money or
-equivalent value.
+ J. "Reproduction" means the making of a counterpart, image or copy of
+ the Subject Software.
 
-L. "Subject Software" means the Original Software, Modifications, or
-any respective parts thereof.
+ K. "Sale" means the exchange of the Subject Software for money or
+ equivalent value.
 
-M. "Use" means the application or employment of the Subject Software
-for any purpose.
+ L. "Subject Software" means the Original Software, Modifications, or
+ any respective parts thereof.
 
-2. GRANT OF RIGHTS
+ M. "Use" means the application or employment of the Subject Software
+ for any purpose.
 
-A. Under Non-Patent Rights: Subject to the terms and conditions of
-this Agreement, each Contributor, with respect to its own contribution
-to the Subject Software, hereby grants to each Recipient a
-non-exclusive, world-wide, royalty-free license to engage in the
-following activities pertaining to the Subject Software:
+ 2. GRANT OF RIGHTS
+
+ A. Under Non-Patent Rights: Subject to the terms and conditions of
+ this Agreement, each Contributor, with respect to its own contribution
+ to the Subject Software, hereby grants to each Recipient a
+ non-exclusive, world-wide, royalty-free license to engage in the
+ following activities pertaining to the Subject Software:
 
   1. Use
   2. Distribution
@@ -82,11 +84,11 @@ following activities pertaining to the Subject Software:
   5. Redistribution
   6. Display
 
-B. Under Patent Rights: Subject to the terms and conditions of this
-Agreement, each Contributor, with respect to its own contribution to
-the Subject Software, hereby grants to each Recipient under Covered
-Patents a non-exclusive, world-wide, royalty-free license to engage in
-the following activities pertaining to the Subject Software:
+ B. Under Patent Rights: Subject to the terms and conditions of this
+ Agreement, each Contributor, with respect to its own contribution to
+ the Subject Software, hereby grants to each Recipient under Covered
+ Patents a non-exclusive, world-wide, royalty-free license to engage in
+ the following activities pertaining to the Subject Software:
 
   1. Use
   2. Distribution
@@ -94,169 +96,169 @@ the following activities pertaining to the Subject Software:
   4. Sale
   5. Offer for Sale
 
-C. The rights granted under Paragraph B. also apply to the combination
-of a Contributor's Modification and the Subject Software if, at the
-time the Modification is added by the Contributor, the addition of
-such Modification causes the combination to be covered by the Covered
-Patents.  It does not apply to any other combinations that include a
-Modification.
+ C. The rights granted under Paragraph B. also apply to the combination
+ of a Contributor's Modification and the Subject Software if, at the
+ time the Modification is added by the Contributor, the addition of
+ such Modification causes the combination to be covered by the Covered
+ Patents.  It does not apply to any other combinations that include a
+ Modification.
 
-D. The rights granted in Paragraphs A. and B. allow the Recipient to
-sublicense those same rights.  Such sublicense must be under the same
-terms and conditions of this Agreement.
+ D. The rights granted in Paragraphs A. and B. allow the Recipient to
+ sublicense those same rights.  Such sublicense must be under the same
+ terms and conditions of this Agreement.
 
-3. OBLIGATIONS OF RECIPIENT
+ 3. OBLIGATIONS OF RECIPIENT
 
-A. Distribution or Redistribution of the Subject Software must be made
-under this Agreement except for additions covered under paragraph 3H.
+ A. Distribution or Redistribution of the Subject Software must be made
+ under this Agreement except for additions covered under paragraph 3H.
 
-1. Whenever a Recipient distributes or redistributes the Subject
-    Software, a copy of this Agreement must be included with each copy
-    of the Subject Software; and
+ 1. Whenever a Recipient distributes or redistributes the Subject
+     Software, a copy of this Agreement must be included with each copy
+     of the Subject Software; and
 
-2. If Recipient distributes or redistributes the Subject Software in
-    any form other than source code, Recipient must also make the
-    source code freely available, and must provide with each copy of
-    the Subject Software information on how to obtain the source code
-    in a reasonable manner on or through a medium customarily used for
-    software exchange.
+ 2. If Recipient distributes or redistributes the Subject Software in
+     any form other than source code, Recipient must also make the
+     source code freely available, and must provide with each copy of
+     the Subject Software information on how to obtain the source code
+     in a reasonable manner on or through a medium customarily used for
+     software exchange.
 
-B. Each Recipient must ensure that the following copyright notice
-appears prominently in the Subject Software:
+ B. Each Recipient must ensure that the following copyright notice
+ appears prominently in the Subject Software:
 
   Copyright 2006 United States Government as represented by
   NASA Langley Research Center. No copyright is claimed in
   the United States under Title 17, U.S. Code. All Other Rights
   Reserved.
 
-C. Each Contributor must characterize its alteration of the Subject
-Software as a Modification and must identify itself as the originator
-of its Modification in a manner that reasonably allows subsequent
-Recipients to identify the originator of the Modification.  In
-fulfillment of these requirements, Contributor must include a file
-(e.g., a change log file) that describes the alterations made and the
-date of the alterations, identifies Contributor as originator of the
-alterations, and consents to characterization of the alterations as a
-Modification, for example, by including a statement that the
-Modification is derived, directly or indirectly, from Original
-Software provided by Government Agency. Once consent is granted, it
-may not thereafter be revoked.
-
-D. A Contributor may add its own copyright notice to the Subject
-Software.  Once a copyright notice has been added to the Subject
-Software, a Recipient may not remove it without the express permission
-of the Contributor who added the notice.
-
-E. A Recipient may not make any representation in the Subject Software
-or in any promotional, advertising or other material that may be
-construed as an endorsement by Government Agency or by any prior
-Recipient of any product or service provided by Recipient, or that may
-seek to obtain commercial advantage by the fact of Government Agency's
-or a prior Recipient's participation in this Agreement.
-
-F. In an effort to track usage and maintain accurate records of the
-Subject Software, each Recipient, upon receipt of the Subject Software,
-is requested to provide Government Agency, by e-mail to the Government
-Agency Point of Contact listed in clause 5.F., the following information:
-name, institution (if applicable), postal code, and country.
-Recipient's name and personal information shall be used for statistical
-purposes only. Once a Recipient makes a Modification available, it is
-requested that the Recipient inform Government Agency, by e-mail to the
-Government Agency Point of Contact listed in clause 5.F., how to
-access the Modification.
-
-G. Each Contributor represents that that its Modification is believed
-to be Contributor's original creation and does not violate any
-existing agreements, regulations, statutes or rules, and further that
-Contributor has sufficient rights to grant the rights conveyed by this
-Agreement.
-
-H. A Recipient may choose to offer, and to charge a fee for, warranty,
-support, indemnity and/or liability obligations to one or more other
-Recipients of the Subject Software.  A Recipient may do so, however,
-only on its own behalf and not on behalf of Government Agency or any
-other Recipient.  Such a Recipient must make it absolutely clear that
-any such warranty, support, indemnity and/or liability obligation is
-offered by that Recipient alone.  Further, such Recipient agrees to
-indemnify Government Agency and every other Recipient for any
-liability incurred by them as a result of warranty, support, indemnity
-and/or liability offered by such Recipient.
-
-I. A Recipient may create a Larger Work by combining Subject Software
-with separate software not governed by the terms of this agreement and
-distribute the Larger Work as a single product. In such case, the
-Recipient must make sure Subject Software, or portions thereof,
-included in the Larger Work is subject to this Agreement.
-
-J. Notwithstanding any provisions contained herein, Recipient is
-hereby put on notice that export of any goods or technical data from
-the United States may require some form of export license from the
-U.S. Government.  Failure to obtain necessary export licenses may
-result in criminal liability under U.S. laws.  Government Agency
-neither represents that a license shall not be required nor that, if
-required, it shall be issued.  Nothing granted herein provides any
-such export license.
-
-4. DISCLAIMER OF WARRANTIES AND LIABILITIES; WAIVER AND INDEMNIFICATION
-
-A. No Warranty: THE SUBJECT SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY
-WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY,
-INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE
-WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM
-INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR
-FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO
-THE SUBJECT SOFTWARE. THIS AGREEMENT DOES NOT, IN ANY MANNER,
-CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY PRIOR RECIPIENT
-OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY
-OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE.
-FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES
-REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE,
-AND DISTRIBUTES IT "AS IS."
-
-B. Waiver and Indemnity: RECIPIENT AGREES TO WAIVE ANY AND ALL CLAIMS
-AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND
-SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT.  IF RECIPIENT'S USE OF
-THE SUBJECT SOFTWARE RESULTS IN ANY LIABILITIES, DEMANDS, DAMAGES,
-EXPENSES OR LOSSES ARISING FROM SUCH USE, INCLUDING ANY DAMAGES FROM
-PRODUCTS BASED ON, OR RESULTING FROM, RECIPIENT'S USE OF THE SUBJECT
-SOFTWARE, RECIPIENT SHALL INDEMNIFY AND HOLD HARMLESS THE UNITED
-STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY
-PRIOR RECIPIENT, TO THE EXTENT PERMITTED BY LAW.  RECIPIENT'S SOLE
-REMEDY FOR ANY SUCH MATTER SHALL BE THE IMMEDIATE, UNILATERAL
-TERMINATION OF THIS AGREEMENT.
-
-
-5. GENERAL TERMS
-
-A. Termination: This Agreement and the rights granted hereunder will
-terminate automatically if a Recipient fails to comply with these
-terms and conditions, and fails to cure such noncompliance within
-thirty (30) days of becoming aware of such noncompliance.  Upon
-termination, a Recipient agrees to immediately cease use and
-distribution of the Subject Software.  All sublicenses to the Subject
-Software properly granted by the breaching Recipient shall survive any
-such termination of this Agreement.
-
-B. Severability: If any provision of this Agreement is invalid or
-unenforceable under applicable law, it shall not affect the validity
-or enforceability of the remainder of the terms of this Agreement.
-
-C. Applicable Law: This Agreement shall be subject to United States
-federal law only for all purposes, including, but not limited to,
-determining the validity of this Agreement, the meaning of its
-provisions and the rights, obligations and remedies of the parties.
-
-D. Entire Understanding: This Agreement constitutes the entire
-understanding and agreement of the parties relating to release of the
-Subject Software and may not be superseded, modified or amended except
-by further written agreement duly executed by the parties.
-
-E. Binding Authority: By accepting and using the Subject Software
-under this Agreement, a Recipient affirms its authority to bind the
-Recipient to all terms and conditions of this Agreement and that that
-Recipient hereby agrees to all terms and conditions herein.
-
-F. Point of Contact: Any Recipient contact with Government Agency is
-to be directed to the designated representative as follows:
-funit-support@rubyforge.org.
+ C. Each Contributor must characterize its alteration of the Subject
+ Software as a Modification and must identify itself as the originator
+ of its Modification in a manner that reasonably allows subsequent
+ Recipients to identify the originator of the Modification.  In
+ fulfillment of these requirements, Contributor must include a file
+ (e.g., a change log file) that describes the alterations made and the
+ date of the alterations, identifies Contributor as originator of the
+ alterations, and consents to characterization of the alterations as a
+ Modification, for example, by including a statement that the
+ Modification is derived, directly or indirectly, from Original
+ Software provided by Government Agency. Once consent is granted, it
+ may not thereafter be revoked.
+
+ D. A Contributor may add its own copyright notice to the Subject
+ Software.  Once a copyright notice has been added to the Subject
+ Software, a Recipient may not remove it without the express permission
+ of the Contributor who added the notice.
+
+ E. A Recipient may not make any representation in the Subject Software
+ or in any promotional, advertising or other material that may be
+ construed as an endorsement by Government Agency or by any prior
+ Recipient of any product or service provided by Recipient, or that may
+ seek to obtain commercial advantage by the fact of Government Agency's
+ or a prior Recipient's participation in this Agreement.
+
+ F. In an effort to track usage and maintain accurate records of the
+ Subject Software, each Recipient, upon receipt of the Subject Software,
+ is requested to provide Government Agency, by e-mail to the Government
+ Agency Point of Contact listed in clause 5.F., the following information:
+ name, institution (if applicable), postal code, and country.
+ Recipient's name and personal information shall be used for statistical
+ purposes only. Once a Recipient makes a Modification available, it is
+ requested that the Recipient inform Government Agency, by e-mail to the
+ Government Agency Point of Contact listed in clause 5.F., how to
+ access the Modification.
+
+ G. Each Contributor represents that that its Modification is believed
+ to be Contributor's original creation and does not violate any
+ existing agreements, regulations, statutes or rules, and further that
+ Contributor has sufficient rights to grant the rights conveyed by this
+ Agreement.
+
+ H. A Recipient may choose to offer, and to charge a fee for, warranty,
+ support, indemnity and/or liability obligations to one or more other
+ Recipients of the Subject Software.  A Recipient may do so, however,
+ only on its own behalf and not on behalf of Government Agency or any
+ other Recipient.  Such a Recipient must make it absolutely clear that
+ any such warranty, support, indemnity and/or liability obligation is
+ offered by that Recipient alone.  Further, such Recipient agrees to
+ indemnify Government Agency and every other Recipient for any
+ liability incurred by them as a result of warranty, support, indemnity
+ and/or liability offered by such Recipient.
+
+ I. A Recipient may create a Larger Work by combining Subject Software
+ with separate software not governed by the terms of this agreement and
+ distribute the Larger Work as a single product. In such case, the
+ Recipient must make sure Subject Software, or portions thereof,
+ included in the Larger Work is subject to this Agreement.
+
+ J. Notwithstanding any provisions contained herein, Recipient is
+ hereby put on notice that export of any goods or technical data from
+ the United States may require some form of export license from the
+ U.S. Government.  Failure to obtain necessary export licenses may
+ result in criminal liability under U.S. laws.  Government Agency
+ neither represents that a license shall not be required nor that, if
+ required, it shall be issued.  Nothing granted herein provides any
+ such export license.
+
+ 4. DISCLAIMER OF WARRANTIES AND LIABILITIES; WAIVER AND INDEMNIFICATION
+
+ A. No Warranty: THE SUBJECT SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY
+ WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY,
+ INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE
+ WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM
+ INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR
+ FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO
+ THE SUBJECT SOFTWARE. THIS AGREEMENT DOES NOT, IN ANY MANNER,
+ CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY PRIOR RECIPIENT
+ OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY
+ OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE.
+ FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES
+ REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE,
+ AND DISTRIBUTES IT "AS IS."
+
+ B. Waiver and Indemnity: RECIPIENT AGREES TO WAIVE ANY AND ALL CLAIMS
+ AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND
+ SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT.  IF RECIPIENT'S USE OF
+ THE SUBJECT SOFTWARE RESULTS IN ANY LIABILITIES, DEMANDS, DAMAGES,
+ EXPENSES OR LOSSES ARISING FROM SUCH USE, INCLUDING ANY DAMAGES FROM
+ PRODUCTS BASED ON, OR RESULTING FROM, RECIPIENT'S USE OF THE SUBJECT
+ SOFTWARE, RECIPIENT SHALL INDEMNIFY AND HOLD HARMLESS THE UNITED
+ STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY
+ PRIOR RECIPIENT, TO THE EXTENT PERMITTED BY LAW.  RECIPIENT'S SOLE
+ REMEDY FOR ANY SUCH MATTER SHALL BE THE IMMEDIATE, UNILATERAL
+ TERMINATION OF THIS AGREEMENT.
+
+
+ 5. GENERAL TERMS
+
+ A. Termination: This Agreement and the rights granted hereunder will
+ terminate automatically if a Recipient fails to comply with these
+ terms and conditions, and fails to cure such noncompliance within
+ thirty (30) days of becoming aware of such noncompliance.  Upon
+ termination, a Recipient agrees to immediately cease use and
+ distribution of the Subject Software.  All sublicenses to the Subject
+ Software properly granted by the breaching Recipient shall survive any
+ such termination of this Agreement.
+
+ B. Severability: If any provision of this Agreement is invalid or
+ unenforceable under applicable law, it shall not affect the validity
+ or enforceability of the remainder of the terms of this Agreement.
+
+ C. Applicable Law: This Agreement shall be subject to United States
+ federal law only for all purposes, including, but not limited to,
+ determining the validity of this Agreement, the meaning of its
+ provisions and the rights, obligations and remedies of the parties.
+
+ D. Entire Understanding: This Agreement constitutes the entire
+ understanding and agreement of the parties relating to release of the
+ Subject Software and may not be superseded, modified or amended except
+ by further written agreement duly executed by the parties.
+
+ E. Binding Authority: By accepting and using the Subject Software
+ under this Agreement, a Recipient affirms its authority to bind the
+ Recipient to all terms and conditions of this Agreement and that that
+ Recipient hereby agrees to all terms and conditions herein.
+
+ F. Point of Contact: Any Recipient contact with Government Agency is
+ to be directed to the designated representative as follows:
+ funit-support@rubyforge.org.

data/README

@@ -1,27 +1,132 @@
 = FUnit: a Fortran Unit Testing Framework
 
-FUnit is a unit testing framework for Fortran modules.
+FUnit is a {unit testing}[http://en.wikipedia.org/wiki/Unit_testing]
+framework for Fortran modules.
+
 Unit tests are written in Fortran fragments that use a small
-set of testing-specific extensions.  FUnit transforms these
-fragments into valid Fortran code and compiles,
-links, and runs them against the module under test.
- 
-== Prerequisites
+set of testing-specific keywords and functions.  FUnit transforms
+these fragments into valid Fortran code and compiles, links, and
+runs them against the module under test.
+
+FUnit is
+{opinionated software}[http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html]
+which values convention over configuration.
+Specifically, fUnit requires a Fortran 95 compiler,
+it only supports testing routines contained in modules,
+it requires tests to be stored along side the code under test,
+and it requires that you follow a specific naming rule
+for test files.
+
+* Documentation: http://funit.rubyforge.org
+* Project Page: http://rubyforge.org/projects/funit
+
+== Requirements
 
 1. A Fortran 90/95/2003 compiler (set via F9X environment variable)
-2. {The Ruby language}[http://www.ruby-lang.org/]
-3. {RubyGems package manager}[http://rubyforge.org/projects/rubygems/]
+2. {The Ruby language}[http://www.ruby-lang.org/] with the
+   {RubyGems package manager}[http://rubyforge.org/projects/rubygems/]
 
 == Installation
 
  gem install funit
 
+== Example
+
+Suppose you have a module in <tt>gas_physics.f90</tt> that
+contains a routine that returns viscosity as a function of
+temperature,
+
+ module gas_physics
+ ..
+ contains
+   ..
+   function viscosity(temperature)
+     real :: viscosity, temperature
+     viscosity = 2.0e-3 * temperature**1.5
+   end function
+   ..
+ end module
+
+The tests of this module would be contained in <tt>gas_physicsMT.ftk</tt>,
+and might contain a test like,
+
+ ..
+ beginTest viscosity_varies_as_temperature
+  IsRealEqual( 0.0, viscosity(0.0) )
+  IsEqualWithin( 0.7071, viscosity(50.0), 1e-3 )
+ endTest
+ ..
+
+This brief fragment is all you need, the framework provides
+the rest of the trappings to turn this into valid Fortran code.
+
+You would run the tests for the <tt>gas_physics</tt> module
+with the command,
+
+ funit gas_physics
+
+which would transform your fragments contained in <tt>gas_physicsMT.ftk</tt>
+into valid Fortran code, create a test runner program, compile everything,
+and run the tests.  A sample output would look like,
+
+ parsing gas_physicsMT.ftk
+ computing dependencies
+ locating associated source files and sorting for compilation
+ g95 -o TestRunner 
+   gas_physics.f90 \
+   gas_physicsMT.f90 \
+   TestRunner.f90
+ 
+ gas_physics test suite:
+ Passed 2 of 2 possible asserts comprising 1 of 1 tests.
+
+== Support
+
+Send email to funit-support@rubyforge.org or submit a request
+through http://rubyforge.org/tracker/?group_id=1416.
+
+== License
+
+FUnit is released under the NASA Open Source Agreement, which
+requests registration.  If you would like to register, send
+an email to funit-support@rubyforge.org with your name, institution
+(if applicable), city, postal code, and country.
+See COPYING[http://funit.rubyforge.org/files/COPYING.html] for details.
+
+== A Brief History
+
+On October 4, 2001, Mike Hill (then of
+{Object Mentor}[http://www.objectmentor.com/], now of
+{Industrial Logic}[http://www.industriallogic.com])
+visited NASA Langley Research Center in Hampton, Virginia
+and gave a test-first design talk at Institute for Computer
+and Applied Sciences and Engineering (ICASE).  Copies of his
+slides are available at
+{icase.edu/series/MPP}[http://www.icase.edu/series/MPP/].
+
+Mike spent the afternoon with Bil Kleb, Bill Wood, Karen Bibb,
+and Mike Park reasoning out how we might create a testing framework
+for Fortran 90 to use during FUN3D[http://fun3d.larc.nasa.gov]
+code development.  By the end of the afternoon we had a working
+protoype based on the macro expansion techniques employed in
+Mike Hill's cpptestkit[http://sourceforge.net/projects/cpptestkit].
+We quickly found C-preprocessor macros to be to restrictive and
+rewrote the framework in Ruby[http:www.ruby-lang.org].
+
 == To Do
 
-* Make tests so that they fail gracefully if Fortran compiler not found.
-* Work out RubyGEM packaging kinks.
-* Change from CamelCase to snake_case.
+* Make tests fail gracefully if Fortran compiler is not found.
+* Complete migration rom CamelCase to snake_case for methods and variables.
 * Use 'test' keyword instead of 'beginTest' business.
+* Don't add to test name during translation to avoid 32 character limit trouble.
+* Rename assertions to more consistent with other xUnits.
+* Add assertions to capture stops and warning messages.
 * Clean up documentation.
 * To increase portability, create a single, stand-alone executable with
   Erik Veenstra's RubyScript2Exe[http://www.erikveen.dds.nl/rubyscript2exe/].
+* Use a makefile instead of a single, ordered command line for compilation.
+* Add a clean option to remove all generated artifacts.
+* Migrate to a new naming convention?
+  E.g., gas_physics.fun -> gas_physics_fun.f90
+* Change Fortran envinoment variable from <tt>F9X</tt> to GNU-standard
+  <tt>FC</tt>.