Week 7 and Evaluation Week 2

The past two weeks, we carried on with remaining implementations and tests. We also adding travis support for tests. I will be putting up a common post for Week 7 and Evaluation Week 2 since all mentors were not available this week and the week before, we postponed Friday’s meet to the Tuesday of the following week. Next week onwards, posts will be put up as usual.

Tasks for the week

  • Continue adding tests
  • Continue adding non-pandas implementations
  • Finish the renaming of metrics
  • Integrate tests with travis
  • Allow for adding charts to analysis script

Summary for the week

  • Continue adding tests (#211 #212 #228)
    Not much to say here! I added tests for several metrics as well as the conditions and utils modules.

  • Continue with non-pandas hierarchy of metrics(#223 #210 #227) Among others, I added non-pandas reference implementations odeChangesLines, Reviews, Reviews Accepted, Reviews Declined

  • Clean up metrics and rename them(#222)
    Made several minor changes like renaming modules and classes and a few formatting errors that had slipped through.

  • Integrate tests with travis (#226)
    Jesus had requested Valerio to setup travis integration for tests for the implementations. This is the PR he proposed.

  • Allow for adding charts to analyze script(#207)
    Over the past few days, I added a lot more functionality to the script. Date parameters, hierarchy of metrics and several other things are in working order. Unfortunately, I did not focus too much on adding chart functionality to the script since I wanted to finish implementing the rest of the metrics.

$ \ $

Meeting details

The last week, we also had a small meeting on the 23rd regarding travis integration. The log for that meeting can be found here.

The weekly IRC meeting with my mentors held on Friday (the 26th) is summarized below.

Agenda

  • Regarding the script for metric evaluation
  • Minor points on Travis Integration

Summary

  • Regarding the script for metric evaluation
    We discussed possible structures for the code. The main point we discussed was whether to allow the user to input Perceval data files to the script or to abstract that part — the user would specify owner and repository name and Perceval would be called internally to fetch the required data. Ultimately, we decided to go with the latter. Also, the output of the script would be a PDF report.

  • Points on travis integration
    A few points on the structure of tests (having two separate folders testsand tests_df vs having a single tests directory) were discussed. This was not finalized in the meeting, and would be discussed next week.

$ \ $

  • Tasks for the next week

    • Carry on with non-pandas implementations

    • Continue with tests

    • Continue with the script to compute all metrics

    • Continue with the non-pandas reference implementations

    • Add charting to the analysis script

    • Continue implementing other metrics that are as yet undergoing discussion, if possible

The log for this meeting can be found here.

For older GSoC posts, please click here.