[reproducible-website] 01/01: resolve this confusion

[Holger Levsen]

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

holger pushed a commit to branch master
in repository reproducible-website.

commit b3882a68b51d5d3c2cc4b87a56cd5a0beb1092e4
Author: Holger Levsen <holger at layer-acht.org>
Date:   Tue Mar 14 16:40:13 2017 +0100

    resolve this confusion
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
 _events/berlin2016/agenda.md             | 1 +
 _events/berlin2016/binarytransparency.md | 4 +++-
 _events/berlin2016/whatelse.md           | 9 ++++-----
 3 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/_events/berlin2016/agenda.md b/_events/berlin2016/agenda.md
index 43ba260..f587fbe 100644
--- a/_events/berlin2016/agenda.md
+++ b/_events/berlin2016/agenda.md
@@ -91,6 +91,7 @@ Day 2
 *    14.20 Working Sessions III
 
      -   **What Else for the Auditable Ecosystem? https://pad.riseup.net/p/reproduciblebuildsII-whatelse (was https://pad.riseup.net/p/reproduciblebuildsII-binarytransparency )**
+     -   **[What else]({{ "/events/berlin2016/whatelse/" | prepend: site.baseurl }})** instead of **[Binary Transparency]({{ "/events/berlin2016/binarytransparency/" | prepend: site.baseurl }})**
      -   **SOURCE_PREFIX_MAP https://pad.riseup.net/p/reproduciblebuildsII-SOURCE_PREFIX_MAP**
      -   **Documentation II https://pad.riseup.net/p/reproduciblebuildsII-documentationII**
      -   **Defining reproducible builds II https://pad.riseup.net/p/reproduciblebuildsdefinitionII**
diff --git a/_events/berlin2016/binarytransparency.md b/_events/berlin2016/binarytransparency.md
index ff3df26..81b4e19 100644
--- a/_events/berlin2016/binarytransparency.md
+++ b/_events/berlin2016/binarytransparency.md
@@ -1,11 +1,13 @@
 ---
 layout: event_detail
-title: binarytransparency
+title: Binary Transparency I
 event: berlin2016
 order: 170
 permalink: /events/berlin2016/binarytransparency/
 ---
 
+somehow another pad was used in [this session]({{ "/events/berlin2016/whatelse/" | prepend: site.baseurl }}).
+
 <img style="margin-top: 10px; vertical-align: top;" src="{{ "/images/berlin2016/binarytransparency_01.jpg" | prepend: site.baseurl }}" alt="Binary Transparency Post-It notes" />
 
 
diff --git a/_events/berlin2016/whatelse.md b/_events/berlin2016/whatelse.md
index 8d5607b..1c5b7b9 100644
--- a/_events/berlin2016/whatelse.md
+++ b/_events/berlin2016/whatelse.md
@@ -1,12 +1,12 @@
 ---
 layout: event_detail
-title: whatelse
+title: What else…
 event: berlin2016
 order: 160
 permalink: /events/berlin2016/whatelse/
 ---
 
-what Else for the Auditable Ecosystem?
+### What Else for the Auditable Ecosystem?
 --------------------------------------
 
 What other gaps from Upstream code to User-facing binary artifacts?
@@ -21,9 +21,9 @@ benefits of trust in the code by running stuff that was made from it.
   * repo to tarball
   * server to user
 
-multiple builders is not the same as binary transparency.
+Multiple builders is not the same as binary transparency.
 
-does binary-transparency-style logging perform the same functionality as trusting n of k ?
+Does binary-transparency-style logging perform the same functionality as trusting n of k ?
 
 "append-only" is the feature we want from publication.
 
@@ -75,4 +75,3 @@ we might need an "ecosystem janitor" team:
 Eric Mehyre suggests considering IPFS or other content-addressable
 store.
 
--

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git