zenodoopen

359,569 commits with source code density; 1149 commits of which have software maintenance activity labels (adaptive, corrective, perfective)

This dataset comes as SQL-importable file and is compatible with the widely available MariaDB- and MySQL-databases. It is based on (and incorporates/extends) the dataset "1151 commits with software maintenance activity labels (corrective,perfective,adaptive)" by Levin and Yehudai (<a href="https://doi.org/10.5281/zenodo.835534">https://doi.org/10.5281/zenodo.835534</a>). The extensions to this dataset were obtained using Git-Tools, a tool that is included in the Git-Density (<a href="https://doi.org/10.5281/zenodo.2565238">https://doi.org/10.5281/zenodo.2565238</a>) suite. For each of the projects in the original dataset, Git-Tools was run in extended mode. The dataset contains these tables: <ul> <li>x1151: The original dataset from Levin and Yehudai. <ul> <li>despite its name, this dataset has only 1,149 commits, as two commits were duplicates in the original dataset.</li> <li>This dataset spanned 11 projects, each of which had between 99 and 114 commits</li> <li>This dataset has 71 features and spans the projects RxJava, hbase, elasticsearch, intellij-community, hadoop, drools, Kotlin, restlet-framework-java, orientdb, camel and spring-framework.</li> </ul> </li> <li>gtools_ex (short for Git-Tools, extended) <ul> <li>Contains 359,569 commits, analyzed using Git-Tools in extended mode</li> <li>It spans all commits and projects from the x1151 dataset as well.</li> <li>All 11 projects were analyzed, from the initial commit until the end of January 2019. For the projects Intellij and Kotlin, the first 35,000 resp. 30,000 commits were analyzed.</li> <li>This dataset introduces 35 new features (see list below), 22 of which are size- or density-related.</li> </ul> </li> </ul> The dataset contains these views: <ul> <li>geX_L (short for Git-tools, extended, with labels) <ul> <li>Joins the commits' labels from x1151 with the extended attributes from gtools_ex, using the commits' hashes.</li> </ul> </li> <li>jeX_L (short for joined, extended, with labels) <ul> <li>Joins the datasets x1151 and gtools_ex entirely, based on the commits' hashes.</li> </ul> </li> </ul>   Features of the gtools_ex dataset: <ul> <li>SHA1</li> <li>RepoPathOrUrl</li> <li>AuthorName</li> <li>CommitterName</li> <li>AuthorTime (UTC)</li> <li>CommitterTime (UTC)</li> <li>MinutesSincePreviousCommit: Double, describing the amount of minutes that passed since the previous commit. Previous refers to the parent commit, not the previous in time.</li> <li>Message: The commit's message/comment</li> <li>AuthorEmail</li> <li>CommitterEmail</li> <li>AuthorNominalLabel: All authors of a repository are analyzed and merged by Git-Density using some heuristic, even if they do not always use the same email address or name. This label is a unique string that helps identifying the same author across commits, even if the author did not always use the exact same identity.</li> <li>CommitterNominalLabel: The same as AuthorNominalLabel, but for the committer this time.</li> <li>IsInitialCommit: A boolean indicating, whether a commit is preceded by a parent or not.</li> <li>IsMergeCommit: A boolean indicating whether a commit has more than one parent.</li> <li>NumberOfParentCommits</li> <li>ParentCommitSHA1s: A comma-concatenated string of the parents' SHA1 IDs</li> <li>NumberOfFilesAdded</li> <li>NumberOfFilesAddedNet: Like the previous property, but if the net-size of all changes of an added file is zero (i.e. when adding a file that is empty/whitespace or does not contain code), then this property does not count the file.</li> <li>NumberOfLinesAddedByAddedFiles</li> <li>NumberOfLinesAddedByAddedFilesNet: Like the previous property, but counts the net-lines</li> <li>NumberOfFilesDeleted</li> <li>NumberOfFilesDeletedNet: Like the previous property, but considers only files that had net-changes</li> <li>NumberOfLinesDeletedByDeletedFiles</li> <li>NumberOfLinesDeletedByDeletedFilesNet: Like the previous property, but counts the net-lines</li> <li>NumberOfFilesModified</li> <li>NumberOfFilesModifiedNet: Like the previous property, but considers only files that had net-changes</li> <li>NumberOfFilesRenamed</li> <li>NumberOfFilesRenamedNet: Like the previous property, but considers only files that had net-changes</li> <li>NumberOfLinesAddedByModifiedFiles</li> <li>NumberOfLinesAddedByModifiedFilesNet: Like the previous property, but counts the net-lines</li> <li>NumberOfLinesDeletedByModifiedFiles</li> <li>NumberOfLinesDeletedByModifiedFilesNet: Like the previous property, but counts the net-lines</li> <li>NumberOfLinesAddedByRenamedFiles</li> <li>NumberOfLinesAddedByRenamedFilesNet: Like the previous property, but counts the net-lines</li> <li>NumberOfLinesDeletedByRenamedFiles</li> <li>NumberOfLinesDeletedByRenamedFilesNet: Like the previous property, but counts the net-lines</li> <li>Density: The ratio between the two sums of all lines added+deleted+modified+renamed and their resp. gross-version. A density of zero means that the sum of net-lines is zero (i.e. all lines changes were just whitespace, comments etc.). A density of of 1 means that all changed net-lines contribute to the gross-size of the commit (i.e. no useless lines with e.g. only comments or whitespace).</li> <li>AffectedFilesRatioNet: The ratio between the sums of NumberOfFilesXXX and NumberOfFilesXXXNet</li> </ul>   This dataset is supporting the paper "Importance and Aptitude of Source code Density for Commit Classification into Maintenance Activities", as submitted to the QRS2019 conference (The 19th IEEE International Conference on Software Quality, Reliability, and Security). Citation: Hönel, S., Ericsson, M., Löwe, W. and Wingkvist, A., 2019. Importance and Aptitude of Source code Density for Commit Classification into Maintenance Activities. In The 19th IEEE International Conference on Software Quality, Reliability, and Security.

ShareScore

36/100

Overall dataset sharing score

Score breakdown

These five areas show where the dataset supports — or may limit — practical reuse.

Stewardship: 8
Harmonization: 8
Access: 16
Reuse readiness: 0
Engagement: 4

Topics

Software Maintenance Software Evolution Mining Software Repositories Predictive Modeling Software Quality