[reproducible-website] 01/01: Reorder.
Chris Lamb
chris at chris-lamb.co.uk
Fri Mar 9 03:59:02 UTC 2018
This is an automated email from the git hooks/post-receive script.
lamby pushed a commit to branch master
in repository reproducible-website.
commit 06e6a7e8e5f423920c877b726bdda0836d1c23a8
Author: Chris Lamb <lamby at debian.org>
Date: Thu Mar 8 19:58:58 2018 -0800
Reorder.
---
funding.html | 88 +++++++++++++++++++++++++++++++-----------------------------
1 file changed, 45 insertions(+), 43 deletions(-)
diff --git a/funding.html b/funding.html
index 4b97ef2..3af0ac4 100644
--- a/funding.html
+++ b/funding.html
@@ -48,6 +48,51 @@ permalink: /funding/
<div class="row">
<div class="four columns title">
+ <h2>Future work</h2>
+ </div>
+ <div class="eight columns">
+ <p>
+ The Reproducible Builds team has demonstrated that it is, in principle,
+ possible to build a Linux distribution in a reproducible manner and have
+ solved many of the issues in doing so.
+ </p>
+
+ <p>
+ However, the next release of Debian ("buster") is currently not yet
+ 100% reproducible and funding to support on-going maintenance of
+ critical infrastructure will be absolutely essential to reach this goal.
+ </p>
+
+ <p>
+ This not only includes the administration of over 50 build nodes across
+ multiple architectures, it requires continuous and patient work with
+ package maintainers and upstreams to merge reproducibility-related
+ patches. It also includes extending the scope of
+ <a href="https://tests.reproducible-builds.org/">our testing
+ framework</a> to even more projects, as well as improving the existing
+ tests and reports.
+ </p>
+
+ <p>
+ In addition, there are currently no tools that let a user know whether
+ packages that they are installing are reproducible or not, required to
+ "close the loop" and allow end-users to finally truly validate the
+ software they are running on their machines.
+ </p>
+
+ <p>
+ Furthermore, maintaining momentum — both in terms of public
+ perception and in private — around the various related projects
+ such as <em>diffoscope</em>, etc. will be key in ensuring a reproducible
+ "buster" becomes a reality.
+ </p>
+ </div>
+</div>
+
+<br>
+
+<div class="row">
+ <div class="four columns title">
<h2>Past work</h2>
</div>
<div class="eight columns">
@@ -110,49 +155,6 @@ permalink: /funding/
<div class="row">
<div class="four columns title">
- <h2>Future work</h2>
- </div>
- <div class="eight columns">
- <p>
- The Reproducible Builds team has demonstrated that it is, in principle,
- possible to build a Linux distribution in a reproducible manner and have
- solved many of the issues in doing so.
- </p>
-
- <p>
- However, the next release of Debian ("buster") is currently not yet
- 100% reproducible and funding to support on-going maintenance of
- critical infrastructure will be absolutely essential to reach this goal.
- </p>
-
- <p>
- This not only includes the administration of over 50 build nodes across
- multiple architectures, it requires continuous and patient work with
- package maintainers and upstreams to merge reproducibility-related
- patches. It also includes extending the scope of
- <a href="https://tests.reproducible-builds.org/">our testing
- framework</a> to even more projects, as well as improving the existing
- tests and reports.
- </p>
-
- <p>
- In addition, there are currently no tools that let a user know whether
- packages that they are installing are reproducible or not, required to
- "close the loop" and allow end-users to finally truly validate the
- software they are running on their machines.
- </p>
-
- <p>
- Furthermore, maintaining momentum — both in terms of public
- perception and in private — around the various related projects
- such as <em>diffoscope</em>, etc. will be key in ensuring a reproducible
- "buster" becomes a reality.
- </p>
- </div>
-</div>
-
-<div class="row">
- <div class="four columns title">
<h2>Contact</h2>
</div>
<div class="eight columns">
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git
More information about the Reproducible-commits
mailing list