On this page, we publish the dataset used in the our paper \u201cOnboarding to Open Source Projects with Good First Issues: A Preliminary Analysis (Hyuga Horiguchi, Itsuki Omori and Masao Ohira)\u201d has been accepted for inclusion in the Early Research Achievements (ERA) track of the 28th IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER \u201921). <\/p>\n\n\n\n
The first file was used for the analysis of RQ1. The second file was used for the analysis of RQ2. The third file was used for the analysis of RQ3. Hyuga Horiguchi (hhyuga201515xx<\/span>@xx<\/span>gmail.com) About On this page, we publish the datas … \u7d9a\u304d\u3092\u8aad\u3080
The violin plot in Fig. 1 shows the distribution of the prs_num<\/code> in the 4th column of the file for each issue_type<\/code> in the 3rd column.
The 1st column, dev_id<\/code> is the ID to identify the developer. It is used to anonymize the account information of GitHub.
The 2nd column, issue_url<\/code> is the URL of the issue resolved by the developer.
The 3rd column, issue_type<\/code> shows whether the issue is a Regular Issue or a Good First Issue.
The 4th column, prs_num<\/code> is the number of PRs that the developer with the dev_id<\/code> has posted on GitHub before resolving the issue with the issue_url<\/code>.<\/p>\n\n\n\n
Table II shows the 1st, 4th, and 7th columns of the file as shown below.
The 1st column, repo_url<\/code> is the URL of the repository.
The 2nd column, issues_num<\/code> is the number of Regular Issues that the repository has.
The 3rd column, resolved_issues_num<\/code> is the number of resolved Regular Issues.
The 4th column, resolved_issues_percentage<\/code> is the value of the resolved_issues_num<\/code> (3rd column) divided by the issues_num<\/code> (2nd column).
The 5th column, good_first_issues_num<\/code> is the number of Good First Issues that the repository has.
The 6th column, resolved_good_first_issues_num<\/code> is the number of resolved Good First Issues.
The 7th column, resolved_good_first_issues_percentage<\/code> is the value of the resolved_good_first_issues_num<\/code> (6th column) divided by the good_first_issues_num<\/code> (5th column).
The 8th column, resolved_ratio<\/code> is the ratio of the resolved_good_first_issues_percentage<\/code> (7th column) divided by the resolved_issues_percentage<\/code> (4th column).<\/p>\n\n\n\n
Table III shows the percentage of developers for each repository whose the prs_num<\/code>(4th column) is 1 or higher among the Good First Issue of the issue_type<\/code>(3rd column).
The 1st column, dev_id<\/code> is the ID to identify the developer.
The 2nd column, issue_url<\/code> is the URL of the issue resolved by the developer.
The 3rd column, issue_type<\/code> shown whether the issue is a Regular Issue or a Good First Issue.
The 4th column, prs_num<\/code> is the number of PRs that the developer with the dev_id<\/code> has posted to the same repository as the issue_url<\/code> after resolving the issue with the issue_url<\/code>.<\/p>\n\n\n\nContact<\/h2>\n\n\n\n
Masao Ohira (masaoxx<\/span>@xx<\/span>wakayama-u.ac.jp)<\/p>\n","protected":false},"excerpt":{"rendered":"