Write a Blog >>
MSR 2018
Mon 28 - Tue 29 May 2018 Gothenburg, Sweden
co-located with ICSE 2018

The Mining Software Repositories (MSR) field analyzes the rich data available in software repositories to uncover interesting and actionable information about software systems and projects. The goal of this two-day conference is to advance the science and practice of MSR. The 15th International Conference on Mining Software Repositories is sponsored will be co-located with ICSE 2018 in Gothenburg, Sweden.

Software repositories such as source control systems, archived communications between project personnel, and defect tracking systems are used to help manage the progress of software projects. Software practitioners and researchers are recognizing the benefits of mining this information to support the maintenance of software systems, improve software design/reuse, and empirically validate novel ideas and techniques. Research is now proceeding to uncover the ways in which mining these repositories can help to understand software development and software evolution, to support predictions about software development, and to exploit this knowledge in planning future development. The goal of this two-day international conference is to advance the science and practice of software engineering via the analysis of data stored in software repositories.

This year, we solicit three types of papers: research, practice, and data. As in previous MSR editions, there will be a Mining Challenge and a special issue of the best MSR papers published in the Empirical Software Engineering journal. For the research and practice papers, we especially encourage submissions that facilitate reproducibility and follow up research by publicly providing data sets and tools. Publicly providing reusable research artifacts (data or tools) is not mandatory, but will strengthen the reproducibility of the research, which is an explicit evaluation criterion.

The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of ICSE 2017. The official publication date affects the deadline for any patent filings related to published work. Purchases of additional pages in the proceedings is not allowed.

The Impact and Value of MSR publications:

The impact of the MSR conference is similar to a CORE A conference, which is an “excellent conference, and highly respected in a discipline area”. For additional information concerning the impact and value of MSR publications, please consult this document.

EMSE Special Issue

A selection of the best research and data papers will be invited to be revised and extended for consideration in a special issue of the for consideration in a special issue of the Empirical Software Engineering (EMSE) journal edited by Springer.

MSR FOSS Impact Paper Award (New this year)

In an effort to encourage research on understanding and improving FOSS (Free, Open Source Software), MSR is establishing the “FOSS Impact paper” award. The award will be granted to papers that show outstanding contributions to the FOSS community. For many years, the MSR community has leveraged public data from FOSS projects, and in the process the community has contributed new insights, tools and techniques to assist FOSS projects in different ways. This award recognizes and encourages such line of research.

The award will be adjudicated by an independent committee composed of prominent FOSS figures. The award is open to all accepted research papers in 2018. Authors should self nominate their papers when submitting to EasyChair. Nominated papers should include a short blurb that highlights the FOSS relevance of the work. The awarded papers will be announced at MSR 2018.

Technical Papers: Call for Papers

View track page for all details

Technical papers can be short papers (4 pages plus 1 additional page for references) and full papers (10 pages plus 2 additional pages for references).

Research Papers

Short research papers should discuss controversial issues in the >ield, or describe interesting or thought provoking ideas that are not yet fully developed. Accepted short papers will present their ideas in a short lightning talk. Full research papers are expected to describe new research results, and have a higher degree of technical rigor than short papers.

Practice Experiences

MSR encourages the submission of papers on practice experiences. They should report experiences of applying mining repository algorithms in an industry/open source organization context. They aim at reporting positive or negative experiences of applying known algorithms, but adapting existing algorithms or proposing new algorithms for practical use would be plus.

Reusable Tools

MSR wants to promote and recognize the creation and use of tools that are designed and built not only for a specific research project, but for the MSR community as a whole. Those tools may let researchers focus on specific aspects of research, let their work be more reproducible, lower the barriers to reuse previous research efforts. Therefore, MSR encourages the submission of papers about these tools. These papers can be descriptions of tools built by the authors, that can be used by other researchers, and/or descriptions of use of tools built by others to obtain some specific research results in the area of mining software repositories.

The public availability of the tool and its internal details, its usefulness for other researchers, the measures taken to simplify its installation and use, and the availability of documentation about it should be clearly discussed in the paper. Both long papers, for complete descriptions of mature tools and/or use cases, and short papers, for summaries of promising use cases and tools, will be accepted. The papers will be reviewed both on their academic merits, and on the specific usefulness of the tools, and the experiences described, for the whole MSR community.

Submission and Review of Research Papers

All research papers, including those describing practical experiences or tools, will face the same level of review and scrutiny. To take their peculiarities into account, if you consider a paper qualifies as practice or tool paper, specify that using the corresponding option when submitting. Submissions should follow ACM formatting guidelines. Papers submitted for consideration should not have been published elsewhere and should not be under review or submitted for review elsewhere for the duration of consideration. ACM plagiarism policies and procedures shall be followed for cases of double submission.

Papers must be submitted electronically through EasyChair.

Upon notification of acceptance, all authors of accepted papers will be asked to complete an ACM Copyright form and will receive further instructions for preparing their camera ready versions. At least one author of each paper is expected to present the results at the MSR 2018 conference. All accepted contributions will be published in the conference electronic proceedings.

A selection of the best papers will be invited to EMSE Special Issue. All accepted research papers in 2018 have a chance to win the "MSR FOSS Impact Paper Award“.

Double-blind Submission Guideline

MSR 2018 will conduct double-blind reviewing. All submissions should not reveal the identity of the authors in any way. Authors should leave out author names and affiliations from the body of their submission. They should also ensure that any citations to related work by themselves are written in the third person, that is, “the prior work of XYZ” as opposed to “our prior work”. Authors having further questions on double-blind reviewing are encouraged to contact the Program Co-Chairs by email.

Important Dates

Abstract Due 23:59 AOE, January 23, 2018
Papers Due23:59 AOE, January 30, 2018,
Author Notification 23:59 AOE, March 2, 2018
Camera Ready 23:59 AOE, March 16, 2018

Organization

Program Committee Chairs

Data Showcase: Call for Papers

View track page for all details

Since 2013, the MSR conference has included a Data Showcase. The purpose of the Data Showcase is to provide a forum to share and discuss the important data sets that underpin the work of the Mining Software Repositories community.

Data Showcase papers should describe data sets that are curated by their authors and made available to use by others. Ideally, these data sets should be of value to others in the community, should be preprocessed or filtered in some way, and should provide an easy-to-understand schema. Data showcase papers are expected to include:

  • a description of the data source
  • a description of the methodology used to gather it (preferably with the tool used to create/generate the data)
  • a description of the storage mechanism, including a schema if applicable,
  • a description of how the data has been used by others,
  • ideas for what future research questions could be answered or what further improvements could be made to the data set, and
  • any limitations and/or challenges in creating or using this data set.

The data set should be made available at the time of submission of the paper for review, but will be considered confidential until publication of the paper.

Data showcase papers are not:

  • empirical studies
  • tool demos
  • based on poorly explained or untrustworthy heuristics for data collection, or
  • simply applying generic tools to generate data that is quick and easy for others to gather.

New this year: We expect all datasets to be accompanied by the source code that was used to create them, along with clear documentation on how to recreate them. The source code should be open source, accompanied by an appropriate license. If you cannot provide the source code or the source code clause is not applicable (e.g. because the dataset consists of qualitative data), please provide a short explanation of why this is not possible.

Submission

Submit your data paper (maximum 4 pages) to EasyChair on or before February 5, 2018. Submitted papers will undergo double-blind peer review, so please remove identifying information from the paper, including author names and funding information. We request that you use third person when referring to your own previous work (Use “This paper extends the work of Smith and Jones (2010)” rather than “This paper extends our previous work (2010)”). Identifying information should be removed during review, and, if the paper is accepted, can be added back into the paper before publication.

Papers submitted for consideration should not have been published elsewhere and should not be under review or submitted for review elsewhere during the duration of consideration. ACM plagiarism policies and procedures shall be followed for cases of double submission. Submissions should follow ACM formatting guidelines and should be submitted using the EasyChair link.

Upon notification of acceptance, all authors of accepted papers will be asked to complete an ACM Copyright form and will receive further instructions for preparing their camera ready versions. At least one author of each paper is expected to present the results at the MSR conference. All accepted contributions will be published in the conference electronic proceedings.

A selection of the best papers will be invited to EMSE Special Issue.

Important Dates

Papers Due 23:59 AOE, February 5, 2018
Author Notification 23:59 AOE, March 2, 2018
Camera Ready 23:59 AOE, March 16, 2018

Organization

Program Committee Chairs

Mining Challenge: Call for Papers

View track page for all details

The International Conference on Mining Software Repositories (MSR) has hosted a mining challenge since 2006. With this challenge we call upon everyone interested to apply their tools to bring research and industry closer together by analyzing a common data set. The challenge is for researchers and practitioners to bravely use their mining tools and approaches on a dare.

This year, the challenge is on Enriched Event Streams, a public data set for empirical studies on in-IDE activities of software developers. The data set contains over 11M events that correspond to 15K hours of working time of 81 developers. We have collected the events using FeedBaG, a general-purpose interaction tracker for Visual Studio that is built as a plugin to Jetbrains ReSharper framework. FeedBaG captures all commands invoked in the IDE, together with additional context information, and stores them in an Enriched Event Stream that provides a holistic picture of the in-IDE development process.

Enriched Event Streams can help answer, for example, the following research questions:

  • Which IDE commands do developer use?
  • How are test cases executed?
  • Does refactoring lead to more failed tests?
  • How do developers navigate the code base?
  • What kind of changes do developer revert?

How to Participate in the Challenge

  1. Familiarize yourself with the CARET plattform and the dataset.
  2. Access and analyze the Enriched Event Streams data set (download the newest dataset).
  3. Use our mailing list to ask questions about the dataset and follow the KaVE project on Twitter for updates.
  4. Report your findings in a four-page document.
  5. Submit your report on or before February 5, 2018.
  6. If your report is accepted, present your results at MSR 2018!

Challenge Data

Our March 1, 2017 release contains 11M interaction events that have been uploaded by a diverse group of 81 developers (developers that contributed less than 2,500 events are already filtered out). Out of these developers, 43 come from industry, three are researchers, give are students, and six are hobby programmers. Twenty-four participants did not provide this (optional) information about their position. The data covers a total of 1,527 aggregated days and was collected over eleven month, byt not all developers participated the entire time. On average, each developer provided 136K events (median 54K) that have been collected over 10 days (media 18.9 days) and that represent 185 hours of active work (median 48 hours). In total the data set aggregates 15K hours of development work.

Enriched Event Streams provide detailed context information about code completion, test execution, and source-code evolution. The data set contains detailed data about 200K usages of the code completion, including a snapshot of the surrounding source code, as well as 3.6K test executions. An average user provided 2.5K usages of the code completion (median 640) and 44 test executions.

We provide an API for both Java and C# that allows reading the data and we created examples in both languages that help you get started. Technically, the data set stores a JSON representation of the collected events and can also be read and processed using other languages.

If you used the Enriched Event Streams data set, please cite our challenge proposal:

    @inproceedings{msr18challenge,
      title={Enriched Event Streams: A General Dataset for Empirical Studies on In-IDE Activities of Software Developers},
      author={Proksch, Sebastian and Amann, Sven and Nadi, Sarah},
      year={2018},
      booktitle={Proceedings of the 15th Working Conference on Mining Software Repositories},
      preprint={http://www.st.informatik.tu-darmstadt.de/artifacts/msr18-challenge/MSR-Challenge-Proposal.pdf}
    }

Challenge Report

The challenge report should describe the results of your work by providing an introduction to the problem you address and why it is worth studying, the version of the data set you used, the approach and tools you used, your results and their implications, and conclusions. Make sure your report highlights the contributions and the importance of your work. We appreciate submissions that make reproducing their results easy, for example by providing (possibly external) replication instructions and open-sourcing additionally created tools.

Challenge reports must be at most 4 pages long and must conform at time of submission to the MSR 2018 Format and Submission Guidelines. Similar to the main track, the Challenge reports will undergo a light-weight double-blind review process. Therefore, the submitted paper must not reveal the authors’ identities. In particular, the names, organizations, and number of authors must not be present, and a reasonable effort should be made to blind externally available material. The identifying information may be re-added, in case of acceptance, in the camera-ready paper.

Submission

Submit your challenge report (maximum 4 pages) to EasyChair on or before February 5, 2018. Please submit your challenge reports to the “Mining Challenge Track”. Papers submitted for consideration should not have been published elsewhere and should not be under review or submitted for review elsewhere during the duration of consideration. ACM plagiarism policies and procedures shall be followed for cases of double submission.

Similar to the main track, the Challenge reports will undergo a double-blind review process. Therefore, the submitted paper must not reveal the authors’ identities. In particular, the names, organizations, and number of authors must not be present, and a reasonable effort should be made to blind externally available material. The identifying information can of course be re-added in case of acceptance in the camera ready paper. Submissions should follow ACM formatting guidelines and should be submitted using the EasyChair link.

Upon notification of acceptance, all authors of accepted papers will be asked to complete an ACM Copyright form and will receive further instructions for preparing their camera ready versions. At least one author of each paper is expected to present the results at the MSR 2018 conference. All accepted contributions will be published in the conference electronic proceedings.

Important Dates

Papers Due 23:59 AOE, February 5, 2018
Author Notification 23:59 AOE, March 2, 2018
Camera Ready 23:59 AOE, March 16, 2018

Organization

Program Committee Chairs