nickel
<p>This is a PROMISE Software Engineering Repository data set made publicly available in order to encourage repeatable, verifiable, refutable, and/or improvable predictive models of software engineering.</p> <ol> <li> <p>Title: Nickle Repository Transaction Data</p> </li> <li> <p>Sources: (a) Original creators of database: Bart Massey 01 503 725-5393 Computer Science Dept. PO Box 751 MS CMPS Portland State University Portland, OR USA 97207-0751 bart@cs.pdx.edu</p> </li> </ol> <p>(b) Donor of database: owner</p> <p>(c) Date received: 31 March 2005</p> <ol> <li> <p>Past Usage: none</p> </li> <li> <p>Relevant Information:</p> </li> </ol> <p>This dataset was assembled by analyzing the publicly-available CVS archives of the Nickle programming language (http://nickle.org) using a modified version of CVSAnalY (http://metricsgrimoire.github.io/CVSAnalY). It is intended for a wide variety of uses, and thus no dependent variable is specified. See Massey’s PROMISE 2005 paper, “Longitudinal Analysis of Long-Timescale Open Source Repository Data”, for further information.</p> <ol> <li> <p>Number of Instances: 2972</p> </li> <li> <p>Number of Attributes: 10 (incl. 2 inferred)</p> </li> <li> <p>Attribute information:</p> <ul> <li>Inferred filetype: <ul> <li>non-numeric—nominal</li> <li>9 values (documentation,images,i18n,ui,multimedia,code,build,devel-doc,unknown)</li> </ul> </li> <li>File Pathname: UNIX relative path name <ul> <li>non-numeric—structured</li> <li>15 directories, 265 files</li> </ul> </li> <li>Revision: dotted-decimal revision string <ul> <li>non-numeric—structured</li> <li>161 unique revision numbers</li> </ul> </li> <li>Author ID: integer identifier <ul> <li>non-numeric—nominal</li> <li>6 unique authors</li> </ul> </li> <li>Lines added: integer <ul> <li>numeric—integer</li> <li>MIN: 0 MAX: 1011 MEAN: 24.0148 STDEV: 65.6858</li> </ul> </li> <li>Lines removed: integer <ul> <li>numeric—integer</li> <li>MIN: 0 MAX: 678 MEAN: 11.6413 STDEV: 42.4373)</li> </ul> </li> <li>File has since been removed (“in Attic”): boolean (0, 1) <ul> <li>non-numeric—nominal</li> <li>11.98% positive</li> </ul> </li> <li>Commit has CVS_SILENT flag: boolean (0, 1) <ul> <li>non-numeric—nominal</li> <li>never set</li> </ul> </li> <li>Inferred that committer was not author: boolean (0, 1) <ul> <li>non-numeric—nominal</li> <li>never set</li> </ul> </li> <li>Commit date: date <ul> <li>MIN: “1999-01-13 06:22:11” MAX: “2005-01-14 16:58:53”</li> <li>Note: CVS has trouble with timezones; we assume all dates are UTC.</li> </ul> </li> </ul> </li> <li> <p>Missing Attribute Values:</p> </li> </ol> <ul> <li>unknown inferred filetype (attr 1): 69</li> </ul> <ol> <li>Class Distribution: N/A</li> </ol>
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
- 4
- Access
- 16
- Reuse readiness
- 8
- Engagement
- 0