Week 12 Update:

Miles Fertel milesfertel at college.harvard.edu
Mon Aug 21 12:50:55 UTC 2017


I have not heard from @Brooks since the 4th of August, so I've been in
contact with Gavin in order to try to get the necessary questions answered
to be in a good place for this last week of GSoC.

It has been difficult making progress the last two weeks without Brooks
> available. I am confident that the Test Cases and Benchmarking code are
> very close to mergeable product, and I would like to see that completed
> this week. With regards to Wikisort, that is a bigger challenge, and I
> would like to get it to a workable place such that it could be improved
> upon in the days past the end of GSOC.
>

---------- Forwarded message ----------
From: Miles Fertel <milesfertel at college.harvard.edu>
Date: Mon, Aug 21, 2017 at 8:42 AM
Subject: Re: Summer of Code
To: gavin at freebsd.org


Hey Gavin,

Sorry for the late response. I've been in crisis mode in and out of
airports for the last 60 hours due to delays and cancellation of several
flights.

Unfortunately no, I haven't heard from brooks yet. I've been taking steps
to solve several of the problems on my own, but I'd be thrilled if you
could find someone to forward these questions to.

Test Cases: <https://reviews.freebsd.org/D11621>

   - Are the test cases prepared to merge? What must be done to merge them?
   - I asked these questions on phabricator and pointed to them to brooks
   by email but received no response:
      - Added the canary for the bigstruct test. Unsure if DEADBEEF is the
      right value to use but it's adjustable. The only problem I have left is
      that of printing out the entire array on failure. I'm unsure of
the proper
      way to do that. I could print both the input array and the improperly
      sorted array to stderr, but I worry about if that would be very
painful to
      look over and find the problem. Just the input array would probably be
      enough to reproduce the bug, but should it be printed directly
to STDOUT or
      STDERR or do I have to do it through some ATF_TC medium?

Benchmark <https://reviews.freebsd.org/D11646>:

   - I've received no commentary on the makefile or the python driver
   script i've uploaded to reviews.freebsd.org.
      - Is there a FreeBSD python style guide to which I should be adhering?
      - Am I utilizing ministat properly?
      - Is my Makefile correct?

WikiSort: <https://reviews.freebsd.org/D11598>

   - "I'd also appreciate if you could recommend what I might do about the
   style of WikiSort. I know it's a bit of an undertaking, as it seems to me
   the only way to make the code reasonably fit Style(9) would be to break it
   down into functions, as the logic results in some statements starting at
   the 70 column mark."
   - I've also received no comments either of the files on phabricator.

Documentation:

   - I've located my documentation temporarily at https://gist.github.com/
   milesfertel/3f1210be9774d33d2e250a447a716261
   <https://gist.github.com/milesfertel/3f1210be9774d33d2e250a447a716261>.
   - Is there a standard location I should be writing documentation?
   - Should I be updating any man pages or writing one for Wikisort?
   - Is there anything you'd have me do to make this project easy to work
   on going forward, as this is the last week of GSOC?

It has been difficult making progress the last two weeks without Brooks
available. I am confident that the Test Cases and Benchmarking code are
very close to mergeable product, and I would like to see that completed
this week. With regards to Wikisort, that is a bigger challenge, and I
would like to get it to a workable place such that it could be improved
upon in the days past the end of GSOC.

Thanks for the help,
- Miles

On Mon, Aug 21, 2017 at 7:45 AM, Gavin Atkinson <gavin at freebsd.org> wrote:

> Hey,
>
> Did you get a response in the end?
>
> Thanks,
>
> Gavin
>
> On 17 August 2017 at 20:38, Gavin Atkinson <gavin at freebsd.org> wrote:
>
>> Hey,
>>
>> I'm away today, let me try contacting him again later tonight of
>> tomorrow, and I'll get back to you tomorrow afternoon.
>>
>> Can you please forward me the question(s) you have? I can try to find
>> somebody else who can help if brooks doesn't get back yo you soon.
>>
>> Thanks,
>>
>> Gavin
>>
>> On 17 Aug 2017 13:56, "Miles Fertel" <milesfertel at college.harvard.edu>
>> wrote:
>>
>>> Any news on this front?
>>> Should I email soc-admins?
>>>
>>> Thanks for the help,
>>> Miles
>>> On Mon, Aug 14, 2017 at 3:19 PM, Miles Fertel <
>>> milesfertel at college.harvard.edu> wrote:
>>>
>>>> Will do,
>>>> Thanks.
>>>>
>>>> On Mon, Aug 14, 2017 at 2:54 PM, Gavin Atkinson <gavin at freebsd.org>
>>>>  wrote:
>>>>
>>>>> Hi Miles,
>>>>>
>>>>> Apologies for this.  I'll try and contact Brooks through a different
>>>>> method and see if I can get hold of him - it may be that he's not receiving
>>>>> your emails for some reason or he may be unexpectedly busy, but I'll try to
>>>>> make contact with him and find out.
>>>>>
>>>>> If you don't hear anything in a couple more days please let soc-admins
>>>>> know again.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Gavin
>>>>>
>>>>> On 14 August 2017 at 13:03, Miles Fertel <
>>>>> milesfertel at college.harvard.edu> wrote:
>>>>>
>>>>>> Hey Gavin,
>>>>>>
>>>>>> I'm working on FreeBSD mergesort through summer of code and we had
>>>>>> been in the process of merging some benchmarking and testing code when I
>>>>>> lost contact with Brooks. I have been sending him updates on my work and
>>>>>> emails with questions but I haven't received any comments from him since
>>>>>> August 4th. Nevertheless the project is still on track with respect to
>>>>>> deliverables, but i'm roadblocked on some questions I had that would allow
>>>>>> for a merge-able product by summer's end. I'd appreciate if you could
>>>>>> advise on where I might direct some of those questions or how I might get
>>>>>> in contact with Brooks.
>>>>>>
>>>>>> Thanks a lot,
>>>>>> Miles Fertel
>>>>>>
>>>>>> Project: https://wiki.freebsd.org/SummerOfCode2017/Mergesort
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>


More information about the soc-status mailing list