Outreachy Summer 2021
vagrant at reproducible-builds.org
Mon Feb 1 01:48:06 UTC 2021
On 2021-01-21, Mattia Rizzolo wrote:
> We are pondering whether to do a round of Outreachy this year.
> Contrary to last years' we are going to throw the topic much earlier,
> and see if
> some good proposal for that round.
> Example for the past rounds would be:
> * https://wiki.debian.org/SummerOfCode2019/ApprovedProjects/ReproducibleBuilds
> * https://wiki.debian.org/Outreachy/Round15/Projects/ReproducibleBuildsOfDebian
> But really, we would love to see some more interesting ideas in there,
> including volunteers to take charge of such projects, if there are any.
> Examples for the kind of projects we are looking for include workflow
> changes, large refactoring work, new features of our tools, specific
> reproducibility fixes, etc. etc. But crucially they should fit in that
> sweet spot of (a) requiring more time and energy than a weekend project,
> but (b) are also not too complicated that they would take forever and
> that (c) they are actually possible to 'complete' in a satisfactory
I would be interested in fleshing out a proposal for an outreachy
internship to develop a tool to parse diffoscope output and make
best-effort suggestions about the possible types of discovered
reproducibility issues (e.g. build path, timestamp, kernel version,
username, hostname, etc.) ... kind of like a retroactive autoclassify
or "reprotest --auto-build" when you don't actually have the binaries
but you have diffoscope output, like the current Debian tests on
Does that sound like an appropriately ambitious (but not too ambitious)
goal for Outreachy?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 227 bytes
Desc: not available
More information about the rb-general