[Reproducible-commits] [source-date-epoch-spec] 01/01: add myself as author, add introduction, add more reasoning

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository source-date-epoch-spec.

commit 3ae29e163d4f5f578d4f5dddc4d2cf30471e9756
Author: Ximin Luo <infinity0 at debian.org>
Date:   Thu Aug 27 17:49:39 2015 +0200

    add myself as author, add introduction, add more reasoning
---
 source-date-epoch-spec.xml | 43 ++++++++++++++++++++++++++++++++++---------
 1 file changed, 34 insertions(+), 9 deletions(-)

diff --git a/source-date-epoch-spec.xml b/source-date-epoch-spec.xml
index 2f7503e..b80f3de 100644
--- a/source-date-epoch-spec.xml
+++ b/source-date-epoch-spec.xml
@@ -13,6 +13,15 @@
 				</address>
 			</affiliation>
 		</author>
+		<author>
+			<firstname>Ximin</firstname>
+			<surname>Luo</surname>
+			<affiliation>
+				<address>
+					<email>infinity0 at debian.org</email>
+				</address>
+			</affiliation>
+		</author>
 	</authorgroup>
 
 	<title><envar>SOURCE_DATE_EPOCH</envar> specification (DRAFT)</title>
@@ -20,6 +29,21 @@
 </articleinfo>
 
 <sect1>
+	<title>Introduction</title>
+	<para>
+		This specification defines a distribution-agnostic standard
+		for build systems to convey information about the date and
+		time in their build result in a reproducible manner.
+	</para>
+	<para>
+		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
+		"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
+		"MAY", and "OPTIONAL" in this document are to be
+		interpreted as described in RFC 2119.
+	</para>
+</sect1>
+
+<sect1>
 	<title>Background</title>
 	<sect2>
 		<title>Reproducible builds</title>
@@ -169,22 +193,23 @@
 		</para>
 		<para>
 			In the context of a distribution, the last modification
-			time is not a property of upstream source itself but
-			rather of a distributions' packaging that encapsulates
-			it. Ensuring this outer timestamp is used by the
-			underlying build system often requires cumbersome and
-			distribution-specific changes.
+			time is not a property of the upstream source itself but
+			rather of the distribution's packaging that encapsulates
+			it. Distributions typically have a standard repository
+			where this information may be accessed easily.
 		</para>
 		<para>
-			This specification therefore attempts to define a
-			distribution-agnostic standard for build systems to
-			exchange such a timestamp in a uniform manner.
+			Many upstream build processes embed the time of the build
+			since that is an easy option that approximates the more
+			informative source timestamp. Many also offer no way for
+			an external source to override this. This specification
+			offers a solution to both of these problems.
 		</para>
 	</sect2>
 </sect1>
 
 <sect1>
-	<title>Specification</title>
+	<title>Environment variables</title>
 	<para>
 		We propose the following environment variables to be consumed by
 		build systems, tools and wrappers.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/source-date-epoch-spec.git