[Reproducible-commits] [blog] 01/01: First post draft

[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 c7028323a8f31e43ec5510b630432876d9cdc18c
Author: Ceridwen <ceridwenv at gmail.com>
Date:   Thu May 19 12:10:00 2016 -0400

    First post draft
---
 drafts/people/ceridwen/first.mdwn | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/drafts/people/ceridwen/first.mdwn b/drafts/people/ceridwen/first.mdwn
new file mode 100644
index 0000000..3efefdf
--- /dev/null
+++ b/drafts/people/ceridwen/first.mdwn
@@ -0,0 +1,32 @@
+[[!meta title="Improving the process for testing build reproducibility"]]
+
+Hi!  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
+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
+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
+[Autopkgtest](https://people.debian.org/~mpitt/autopkgtest/README.running-tests.html).
+
+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
+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.
+

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