<div dir="ltr"><div><div><div>Hello Mattia,<br><br></div>Thanks for the reply.<br><br></div>I have subscribed to the mailing lists diffoscope and reproducible builds.<br><br></div>After going through the bug log again. I decided I want to work on this <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833697">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833697</a> issue but when I read the comments , I noticed Chris Lamb says <br><pre class="gmail-message">I will look into
this and come up with something cleaner.<br><br></pre><pre class="gmail-message">Does this mean he is working on it?<br><br></pre><pre class="gmail-message">If so then I can work on this <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833697">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833697</a><br><br></pre><pre class="gmail-message">regards,<br></pre><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 30, 2016 at 1:20 AM, Mattia Rizzolo <span dir="ltr"><<a href="mailto:mattia@debian.org" target="_blank">mattia@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Sep 27, 2016 at 10:15:54PM +0300, joannah nanjekye wrote:<br>
> Dear Mattia,<br>
<br>
Hi Joannah,<br>
<br>
sorry for the kinda late reply (I know people tends to like quick<br>
turnarounds for these subjects).<br>
<br>
Please take care of subscribing to this mailing list. I expect that<br>
once you officially apply you will be (but you can avoid it for now, if<br>
you want to).<br>
<span class=""><br>
> I like actively being part of ambitious missions and in my view Debian is<br>
> spot on through the projects currently being worked on and maintained. The<br>
> projects that Debian is undertaking during the internship I believe will<br>
> greatly shape my career and knowledge in software development.<br>
<br>
</span>Kind words, just I'm not so confident about the "greatly shape my<br>
career" bit, but for sure some employers appreciate applicants with a<br>
past of contributions to free software projects.<br>
<span class=""><br>
> After looking through the skill set needed , I also saw a good fit for me<br>
> here save for a few other skills I may need to learn through the<br>
> application process especially getting comfortable with packaging. I will<br>
> endeavor I polish up before the deadline on some of them.<br>
<br>
</span>I have some troubles understanding what you mean here, especially the<br>
first sentence.<br>
Anyway don't care too much about the effort of Debian packaging, we have<br>
a lot of experts around, and the work there is pretty much done.<br>
<span class=""><br>
> I was also drawn to Debian pretty much due to the community. It is an<br>
> engaging and easily accessible one and to me this is very important. I was<br>
> in touch with people in this community even people I decided to apply for<br>
> outreachy who freely shared what they knew with me. I almost got tempted to<br>
> mention names but I wont:). A big thanks even in their anonymity.<br>
<br>
</span>*These* are very kind words now! I know a lot of people have/had to<br>
fight a lot to enter enough within the Debian community to feel part of<br>
it. Some areas of Debian used to (still are?) hard to get it.<br>
<span class=""><br>
> I have an idea on concurrent programming much using .net where I used to<br>
> write banking programs that would run simultaneously in windows services.<br>
> Jobs like unattended running of end of day processes for applications that<br>
> ran on top of core banking, automated end of day and bank statement<br>
> transmission through sending transaction files to utility companies on a<br>
> daily basis. These programs ran at the same time and simultaneously and<br>
> were self starting.<br>
<br>
</span>This is nice, but I fear our case is quite different; we would like<br>
diffoscope to e.g. walk directories in parallel, and down that road.<br>
<span class=""><br>
> I would like to begin by working on this<br>
> <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814057" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-<wbr>bin/bugreport.cgi?bug=814057</a> bug.<br>
<br>
</span>That bug is part of a bigger picture where diffoscope would be able to<br>
hide difference (or even better: don't even compute them if not needed)<br>
as requested by the user. See this wiki page for more information:<br>
<a href="https://wiki.debian.org/ReproducibleBuilds/HideProfilesSpecification" rel="noreferrer" target="_blank">https://wiki.debian.org/<wbr>ReproducibleBuilds/<wbr>HideProfilesSpecification</a><br>
Hence I suggest against trying to start with such a thing, but rather<br>
try to fix a simpler thing, like a crash, or tests failures. Goal of<br>
the first phase should be to get accustomed to the codebase, tackling<br>
such bug would be way over that goal.<br>
<span class=""><br>
> You can walk<br>
> me through how I can own a bug so that I don't work on the same bug with<br>
> some one else unknowingly<br>
<br>
</span><a href="https://www.debian.org/Bugs/Developer#owner" rel="noreferrer" target="_blank">https://www.debian.org/Bugs/<wbr>Developer#owner</a><br>
<a href="https://www.debian.org/Bugs/server-control#owner" rel="noreferrer" target="_blank">https://www.debian.org/Bugs/<wbr>server-control#owner</a><br>
<span class=""><br>
> links to the general work flow guidelines of<br>
> submitting a patch the Debian way if there are any things I need to note.<br>
<br>
</span>The usual way is to send a patch as an attachment to a bug report.<br>
Though considering that you'd be contributing code to a "native"<br>
package, and that that package is maintained in git, the preferred form<br>
of sending patches would be to attach them as produced by<br>
git format-patch<br>
or by using<br>
git send-email<br>
(but this one requires a bit of set up), as they are easier to<br>
incorporate.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
regards,<br>
Mattia Rizzolo<br>
<br>
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.<br>
more about me: <a href="https://mapreri.org" rel="noreferrer" target="_blank">https://mapreri.org</a> : :' :<br>
Launchpad user: <a href="https://launchpad.net/~mapreri" rel="noreferrer" target="_blank">https://launchpad.net/~mapreri</a> `. `'`<br>
Debian QA page: <a href="https://qa.debian.org/developer.php?login=mattia" rel="noreferrer" target="_blank">https://qa.debian.org/<wbr>developer.php?login=mattia</a> `-<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><div><i><span style="font-family:Times New Roman"></span></i>Joannah Nanjekye<br>+256776468213<br></div>F : <span>Nanjekye Captain Joannah<br></span></div><span>S : joannah.nanjekye<br></span></div><span>T : @captainjoannah</span><br>SO : joannah<br><br><i><span style="font-family:Times New Roman"><span style="color:#ff6600">"You
think you know when you learn, are more sure when you can write, even
more when you can teach, but certain when you can program."</span> <br>
Alan J. Perlis</span></i></div></div>
</div>