[commits] r12797 - in /libdfp/trunk: CONTRIBUTING CONTRIBUTORS README.developer README.maintainer TODO

[ryanarn@xxxxxxxxxx]

Author: ryanarn
Date: Tue Feb  8 07:46:40 2011
New Revision: 12797

Log:
2011-02-08  Ryan S. Arnold  <rsa@xxxxxxxxxx>

	* README.maintainer: New file.
	* README.developer: Added several TODO items.
	* TODO: Added an item.
	* CONTRIBUTORS: Moved DCO from here to...
	* CONTRIBUTING: here.

Added:
    libdfp/trunk/CONTRIBUTING
    libdfp/trunk/README.maintainer
Modified:
    libdfp/trunk/CONTRIBUTORS
    libdfp/trunk/README.developer
    libdfp/trunk/TODO

Added: libdfp/trunk/CONTRIBUTING
==============================================================================
--- libdfp/trunk/CONTRIBUTING (added)
+++ libdfp/trunk/CONTRIBUTING Tue Feb  8 07:46:40 2011
@@ -1,0 +1,52 @@
+Contribution Statement:
+
+Since Libdfp is a Free Software Foundation project any 'legally
+significant' contribution requires that the contributor go through the FSF
+Copyright Assignment process.
+
+This webpage describes the copyright assignment requirements:
+
+	http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
+
+The maintainer of this library also requires that each individual change be
+accompanied by a DCO that is outlined as follows.
+
+Process For Accepting Third Party Code Contributions:
+
+To improve tracking of contributions to this project we will use a process
+modeled on the modified Developers Certificate of Origin (DCO 1.1) and use a
+"sign-off" procedure on patches that are being emailed around or contributed
+in any other way.
+
+The sign-off is a simple line at the end of the explanation for the patch,
+which certifies that you wrote it or otherwise have the right to pass it on as
+an open-source patch.  The rules are pretty simple: if you can certify the
+below:
+
+By making a contribution to this project, I certify that:
+
+(a)The contribution was created in whole or in part by me and I have the right
+to submit it under the open source license indicated in the file; or
+
+(b)The contribution is based upon previous work that, to the best of my
+knowledge, is covered under an appropriate open source License and I have the
+right under that license to submit that work with modifications, whether
+created in whole or in part by me, under the same open source license (unless
+I am permitted to submit under a different license), as indicated in the file;
+or
+
+(c)The contribution was provided directly to me by some other person who
+certified (a), (b) or (c) and I have not modified it.
+
+(d)The contribution is made free of any other party's intellectual property
+claims or rights.
+
+(e)I understand and agree that this project and the contribution are public
+and that a record of the contribution (including all personal information I
+submit with it, including my sign-off) is maintained indefinitely and may be
+redistributed consistent with this project or the open source license(s)
+involved.
+
+Then you just add a line saying:
+
+Signed-off-by: Random J Developer random@xxxxxxxxxxxxx>

Modified: libdfp/trunk/CONTRIBUTORS
==============================================================================
--- libdfp/trunk/CONTRIBUTORS (original)
+++ libdfp/trunk/CONTRIBUTORS Tue Feb  8 07:46:40 2011
@@ -1,9 +1,3 @@
-Contribution Statement:
-
-	Since this project is under the pervue of the FSF (Free Software
-	Foundation) contributors must obtain FSF copyright assignment prior
-	to contributing significant patches.
-
 Maintainers:
 
 	Base:    Ryan S. Arnold <rsa@xxxxxxxxxx>
@@ -19,43 +13,3 @@
 	Andreas Krebbel <krebbel@xxxxxxxxxxxxxxxxxx>
 	Carlos Eduardo Seo <cseo@xxxxxxxxxxxxxxxxxx>
 	Luis Machado <luisgpm@xxxxxxxxxx>
-
-Process For Accepting Third Party Code Contributions:
-
-To improve tracking of contributions to this project we will use a process
-modeled on the modified Developers Certificate of Origin (DCO 1.1) and use a
-"sign-off" procedure on patches that are being emailed around or contributed
-in any other way.
-
-The sign-off is a simple line at the end of the explanation for the patch,
-which certifies that you wrote it or otherwise have the right to pass it on as
-an open-source patch.  The rules are pretty simple: if you can certify the
-below:
-
-By making a contribution to this project, I certify that:
-
-(a)The contribution was created in whole or in part by me and I have the right
-to submit it under the open source license indicated in the file; or
-
-(b)The contribution is based upon previous work that, to the best of my
-knowledge, is covered under an appropriate open source License and I have the
-right under that license to submit that work with modifications, whether
-created in whole or in part by me, under the same open source license (unless
-I am permitted to submit under a different license), as indicated in the file;
-or
-
-(c)The contribution was provided directly to me by some other person who
-certified (a), (b) or (c) and I have not modified it.
-
-(d)The contribution is made free of any other party's intellectual property
-claims or rights.
-
-(e)I understand and agree that this project and the contribution are public
-and that a record of the contribution (including all personal information I
-submit with it, including my sign-off) is maintained indefinitely and may be
-redistributed consistent with this project or the open source license(s)
-involved.
-
-Then you just add a line saying:
-
-Signed-off-by: Random J Developer random@xxxxxxxxxxxxx>

Modified: libdfp/trunk/README.developer
==============================================================================
--- libdfp/trunk/README.developer (original)
+++ libdfp/trunk/README.developer Tue Feb  8 07:46:40 2011
@@ -39,6 +39,10 @@
 	7.  Make Rules
 	8.  Precision (TODO)
 	9.  Testing (make check) (TODO)
+	10. Contribution Checklist (TODO)
+	11. Coding Style (TODO)
+	12. DFP ABI (TODO)
+	13. Division of Responsibility With GCC (TODO)
 
 	A.  History
 	B.  Acknowledgements

Added: libdfp/trunk/README.maintainer
==============================================================================
--- libdfp/trunk/README.maintainer (added)
+++ libdfp/trunk/README.maintainer Tue Feb  8 07:46:40 2011
@@ -1,0 +1,30 @@
+===========================================================================
+
+				    Libdfp
+	  The "Decimal Floating Point C Library" Maintainer's Guide
+		     for the GNU/Linux OS and GLIBC 2.10+
+			Contributed by IBM Corporation
+		 Copyright (C) 2011 Free Software Foundation
+
+===========================================================================
+NOTE:Eight space tabs are the optimum editor setting for reading this file.
+===========================================================================
+
+		 Author(s) : Ryan S. Arnold <rsa@xxxxxxxxxx>
+			Date Created: February 9, 2011
+
+---------------------------------------------------------------------------
+Table of Contents:
+
+	1.  Introduction
+	2.  Specification
+	  2.1  DFP Spec
+	  2.2  Spec Changes
+	3.  DFP ABI Changes
+	4.  Versioning
+	5.  Mailing Lists
+	6.  ChangeLog
+	7.  Backends
+	8.  Bugs
+	9.  Contributions
+

Modified: libdfp/trunk/TODO
==============================================================================
--- libdfp/trunk/TODO (original)
+++ libdfp/trunk/TODO Tue Feb  8 07:46:40 2011
@@ -34,7 +34,7 @@
 
 Prototype versioned symbols support.
 
-Implement libbid backend.
+Implement libbid backend for x86_64.
 
 [DONE] Write User's guide