Dear Colleague,

The reproducibility report is a companion article for you original IS
paper. The idea of this report is to give incentives to reproducibility,
and it describes your experiment as a computational resource: it gives
details on software used, versions, useful links, how to compile/install,
examples on how to use and replicate the results and plots of the paper,
etc.

Once you submit this report together with the artifact (i.e., software,
data, and a ReproZip package, which we strongly encourage to use),
reviewers will analyze them and try to reproduce, vary, and validate the
results published in your original paper (raw results, tables, plots, ...).
Reviewers may suggest ways to improve your code and reproducibility
coverage as well. I should note that the review is not blinded -- authors
will know who the reviewers are. Here, we are trying to be as transparent
as possible.

If your results can be validated, and if your artifact is in good shape,
then your report and artifact are accepted: (1) the companion paper
(reproducibility report) is published by Elsevier, having the reviewers as
co-authors as well -- reviewers (and the editor) can add information in the
report w.r.t. the reproducibility aspect; and (2) a reference to the
artifact will be created for the reproducibility report.
PS: when I say code in "good shape", I mean code and data that can be
understood and reproduced without too much effort. We certainly understand
that the code comes from a research environment, rather than a
multi-million dollar company!

Please find attached the guidelines for authors.
Let me know if you have any further questions.

If you are interested in submitting this report (and we hope you are!),
kindly let me know.

Best regards,

Fernando Chirigati
fernando.chirigati@gmail.com 
Editor for the Reproducibility Section
Information Systems