Figure 1
Screenshot of GitHub network graph for MOOSE developer (friedmud; Derek Gaston) fork of Stork that contains branches for each of the derivative applications that required an update due to a change in the MOOSE framework (https://github.com/friedmud/stork/network).
Figure 2
GitHub screenshots showing: (a) the patch for a Pull Request created via the GitHub API, and (b) the list of automatically generated Pull Requests for various forks.
Figure 3
Flowchart depicting the development process and associated MooseBuild testing system. For a more detailed description, see Section 2.3.
Table 1
Number of lines added/removed, commits, and unique contributors both before and after the open sourcing of MOOSE. “Before” and “After” refer to the four month periods immediately before and after the open sourcing of MOOSE, respectively (see the Appendix for how these value were determined).
| Lines Added/Removed | Number of Commits | Number of Contributers | |
|---|---|---|---|
| Before | +24373/–12618 | 377 | 16 |
| After | +49964/–33164 | 1069 | 24 |
Figure 4
Number of source code lines added (green) or deleted (red) per week for the MOOSE repository (as reported by GitHub). Note the increased activity after MOOSE was open-sourced in March, 2014.
Figure 5
Left axis: commit history for the top ten MOOSE developers compared to all “other” contributors. Right axis: cumulative number of unique contributors over time (thick black line). The shaded region highlights the time frame during which MOOSE has been available as an open source library on GitHub.