Sprint Details and Trends

[chessbyte]

Since #832 was merged, we now have the Sprints page. This page is fed by the sprint_artifacts file.

Next step is to add Sprint Details. The approach is to add a sprints directory here. At the end of each sprint, the output of the github_activity script will be stored as a file named gh_#{sprint_number}.yaml and the output of the code_climate script will be stored as a file named cc_#{sprint_number}.csv. Leveraging these files, we will add a Details button for each Sprint on the Sprints page which will display per-repo information for PRs and CodeClimate leveraging these new files in the sprints directory.

Once the Sprint Details are working, the next step is to add Trends. These trends are the charts we display at each sprint review representing the PR Velocity, PR Labeling, and Repo Health. In the images directory, 3 new files will be created named trend_pr_velocity.png, trend_pr_labeling.png, and trend_code_climate.png based on the details of the last 10 sprints. A new set of scripts will be implemented leveraging gruff that will generate the 3 trend graphs. These graphs will then be displayed on a new Sprint Trends page.

When a sprint is completed, the various scripts will be run and a new PR created, updating the sprint_artifacts file, creating new files in the sprints directory here, and updates to the trend files described above.

Since our website is based on Jekyll, a static site generator, this seems like the best approach given the technology we are using.

Related PRs:

• prs_per_repo script should work without human interaction
• prs_per_repo optimize interactions with GitHub
• Sprint Details Button to show per-repo PR information
• Sprint Details Button to show per-repo CodeClimate information
• Trends over last 10 sprints
• Top Contributors

[chessbyte]

@Fryguy @bdunne Please review before I start making PRs to implement this.

[chessbyte]

There may be an alternative to be more dynamic (especially on the generation of the trends) following the approach we use to generate the documentation. Would welcome your input.

[Fryguy]

I think this sounds good as a start and we can always tweak it as we move forward 👍