Home

1. Github Best Practices

• The promises and perils of mining GitHub

1.1 Patches

• Detecting Patch Submission and Acceptance in OSS Projects

2. Issue Labeling and Best Practices

• The missing links: bugs and bug-fix commits
• Filling the Gaps of Development Logs and Bug Issue Data
• ReLink: recovering links between bugs and changes
• Fair and balanced?: bias in bug-fix datasets
• Discovering Loners and Phantoms in Commit and Issue Data

3. Collaboration and Communication Networks, and Best Practices

• Putting It All Together: Using Socio-technical Networks to Predict Failures
• Validity of network analyses in Open Source Projects
• Mining email social networks
• An Empirical Study of Multiple Names and Email Addresses in OSS Version Control Repositories
• Communication in open source software development mailing lists
  • "Our investigation reveals that implementation details are discussed only in about 35% of the threads, and that a range of other topics is discussed. Moreover, core developers participate in less than 75% of the threads. We observed that the development mailing list is not the main player in OSS project communication, as it also includes other channels such as the issue repository."
• Episodic volunteering in open source communities
  • "Episodic volunteers, who prefer short term engagement to habitual contributions, are present in Free/Libre and Open Source Software (FLOSS) communities."
• Let's talk about it: evaluating contributions through discussion in GitHub
  • Pull Request discussion analysis and interviews with Github developers.

3.1 User Networks

• User and developer mediation in an Open Source Software community: Boundary spanning through cross participation in online discussions
  • "several key participants act as boundary spanners between the user and the developer communities. This emerging role is characterized by cross-participation in parallel same-topic discussions in both mailing-lists, cohesion between cross-participants, the occupation of a central position in the social network linking users and developers, as well as active, distinctive and adapted contributions"
• Joining Free/Open Source Software Communities: An Analysis of Newbies' First Interactions on Project Mailing Lists
  • "We found that nearly 80% of newbie posts received replies, and that receiving timely responses, especially within 48 hours, was positively correlated with future participation. We also found that while the majority of interactions were positive, 1.5% of responses were rude or hostile."
• Newcomer integration and learning in technical support communities for open source software
  • "We found that one third of newcomers' transition into a role of help givers in the community and demonstrate evidence of learning."
• Understanding the process of participating in open source communities
  • "the number of active developers does not change significantly when the total number of committers increases for the selected OSS projects."

3.2 Tools

• git2net - Mining Time-Stamped Co-Editing Networks from Large git Repositories
  • Tool: Line-Level Collaboration Networks

4. Other ideas

• Detect Related Bugs from Source Code Using Bug Information
• Supplementary Bug Fixes vs. Re-opened Bugs
• On measuring affects of github issues' commenters
• An Empirical Study on the Structural Complexity Introduced by Core and Peripheral Developers in Free Software Projects
• Characterizing the Roles of Contributors in Open-Source Scientific Software Projects
• Exploratory Study of Slack Q&A Chats as a Mining Source for Software Engineering Tools
• Exploring the patterns of social behavior in GitHub

5. Metric Definitions

• Scitools Understand Metrics

6. Software Vulnerabilities

6.1 Threats to Validity

• • Automated Software Vulnerability Assessment with Concept Drift

6.2 Datasets

• Predicting Vulnerable Components: Software Metrics vs Text Mining
  • Manually curated dataset of when Software Vulnerabilities are introduced and fixed.
• Software Metrics and Security Vulnerabilities: Dataset and Exploratory Study
  • Two SQL dump datasets of software vulnerabilities
• Fixing of Security Vulnerabilities in Open Source Projects: A Case Study of Apache HTTP Server and Apache Tomcat
  • Case Study for Apache Tomcat and Apache HTTP Server. Suggests CVE data may be obtained from these projects.
• When a Patch Goes Bad: Exploring the Properties of Vulnerability-Contributing Commits
  • Another study on Apache HTTP Server.
• A Manually-Curated Dataset of Fixes to Vulnerabilities of Open-Source Software
  • Dataset: https://snyk.io/vuln
• VulinOSS: a dataset of security vulnerabilities in open-source systems

6.3 Security Issue Classification

• Security and Emotion: Sentiment Analysis of Security Discussions on GitHub
  • List of security keywords to identify issues as software vulnerabilities for other analysis.
  • An Empirical Study of Security Issues Posted in Open Source Projects uses this list of keywords.

6.4 Culture

• An empirical study of security culture in open source software communities

6.5 Misc

• Apache Security Report
• ConPan: A Tool to Analyze Packages in Software Containers

7. Similar efforts to this project

• On development of a framework for massive source code analysis using static code analyzers
• Boa Meets Python: A Boa Dataset of Data Science Software in Python Language
• The SmartSHARK Ecosystem for Software Repository Mining - ICSE 2020 Demo Track

8. Repo Maintenance Best Practices

• https://devguide.ropensci.org/
• A Large-Scale Study About Quality and Reproducibility of Jupyter Notebooks
• I'm leaving you, Travis: a continuous integration breakup story
• Studying the impact of adopting continuous integration on the delivery time of pull requests
• Machine Learning Technical Debt

9. Big Datasets

• World of Code: An Infrastructure for Mining the Universe of Open Source VCS Data
• Public git archive: a big code dataset for all
• The Maven Dependency Graph: A Temporal Graph-Based Representation of Maven Central
• SOTorrent: Studying the Origin, Evolution, and Usage of Stack Overflow Code Snippets
  • See also SOTorrent: reconstructing and analyzing the evolution of stack overflow posts

10. Other types of Dataset

• A Dataset of Non-Functional Bugs
• SeSaMe: A Data Set of Semantically Similar Java Methods
• CROP: linking code reviews to source code changes

11. Architectural Flaws

• Identifying design problems in the source code: a grounded theory

12. Qualitative Analysis

• Grounded theory in software engineering research: a critical review and guidelines