[Reproducible-commits] [blog] 01/01: Improve wording, note Python is the language, mention myself

[Cara V]

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

ceridwen-guest pushed a commit to branch master
in repository blog.

commit 99f295712bbfbe63cfd23d4201d6a83a390f76cf
Author: Ceridwen <ceridwenv at gmail.com>
Date:   Thu May 19 14:44:49 2016 -0400

    Improve wording, note Python is the language, mention myself
---
 drafts/people/ceridwen/first.mdwn | 44 ++++++++++++++++++++++++---------------
 1 file changed, 27 insertions(+), 17 deletions(-)

diff --git a/drafts/people/ceridwen/first.mdwn b/drafts/people/ceridwen/first.mdwn
index 3efefdf..3da0188 100644
--- a/drafts/people/ceridwen/first.mdwn
+++ b/drafts/people/ceridwen/first.mdwn
@@ -1,32 +1,42 @@
 [[!meta title="Improving the process for testing build reproducibility"]]
 
-Hi!  I'm going to be one of the
+Hi!  I'm Ceridwen.  I'm going to be one of the
 [Outreachy](https://www.gnome.org/outreachy/) interns working on
 [Reproducible Builds](https://wiki.debian.org/ReproducibleBuilds) for
-the summer of 2016.  I'm going to be creating a script, tentatively
+the summer of 2016.  My project is to create a script, tentatively
 named reprotest, to make the process of verifying that a build is
 reproducible easier.
 
 The current
 [tool chain](https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain)
-has limits on what it can test, because of limitations on what build
-variations can be tested in pbuilder/cowbuilder, and is not very user
+and the
+[Reproducible Builds site](http://tests.reproducible-builds.org/) have
+limits on what they can test, and the tool chain is not very user
 friendly.  (For instance, I ended up needing to edit the rebuild.sh
-script.)  There's an outline of the goals for the command line API
-and the configuration file at
-(https://reproducible-builds.org/events/athens2015/reprotest/).  I
-also intend to use some ideas, and possibly some code, from
+script to run it on my system.)  Reprotest will automate some of the
+busywork involved and make it easier for maintainers to test
+reproducibility without detailed knowledge of the tool chain.
+[reproducible-builds.org/events/athens2015/reprotest/](https://reproducible-builds.org/events/athens2015/reprotest/)
+outlines the some of the functionality and command-line and
+configuration file API goals for reprotest.  I also intend to use
+some ideas, and command-line and config processing boilerplate, from
 [Autopkgtest](https://people.debian.org/~mpitt/autopkgtest/README.running-tests.html).
+One major feature is that reprotest, like autopkgtest, should be able
+to interface with more build environments, such as schroot and qemu.
+Both autopkgtest and [diffoscope](https://diffoscope.org/), the
+program that the Reproducible Builds project uses to check binaries
+for differences, are written in Python, and as Python is the scripting
+language I'm most familiar with, I will be writing reprotest in Python
+too.
 
-One of my major goals is to get a usable prototype released in the first
-three to four weeks.  At that point, I want to try to solicit as much
-feedback (and any contributions anyone wants to make!) as possible.
-One of my experiences in open source software is that connecting
-people with software they might want to use is often the hardest part
-of a project.  I've reimplemented existing functionality myself because I
+One of my major goals is to get a usable prototype released in the
+first three to four weeks.  At that point, I want to try to solicit
+feedback (and any contributions anyone wants to make!).  One of my
+experiences in open source software is that connecting people with
+software they might want to use is often the hardest part of a
+project.  I've reimplemented existing functionality myself because I
 simply didn't know that someone else had already written something
 equivalent, and seen many other people do the same.  Once I have the
 skeleton fleshed out, I'm going to be trying to find and reach out to
-other communities who might find reprotest useful, outside the
-Debian reproducible builds project itself.
-
+other communities who might find reprotest useful, outside the Debian
+Reproducible Builds project itself.

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