diff options
author | Raul Infante-Sainz <infantesainz@gmail.com> | 2020-11-23 11:13:54 +0000 |
---|---|---|
committer | Raul Infante-Sainz <infantesainz@gmail.com> | 2020-11-23 11:13:54 +0000 |
commit | d382f1b610e05096b45055826b8f823b6ca796c3 (patch) | |
tree | bd0af045724de261f8ac85c7ec8a875c0967e003 | |
parent | 94cbed6c63ad4362547b4cbcc579c63937a780a6 (diff) |
Minor corrections to referees answer
With this commit, I am just adding several minor corrections to the
answer to the referees. They are very minor typos. I would only
emphasize the fact that in Maneage there is the "Minimal complexity"
criteria, and because of that, even if the project is not able to be
executed in the future, the interested reader could have a look at the
analysis steps (because it is in plain text). Note that I put "Raul" at
the beginning of the line, so my name should have to be removed in the
final document to be sent to the referees.
-rw-r--r-- | peer-review/1-answer.txt | 19 |
1 files changed, 13 insertions, 6 deletions
diff --git a/peer-review/1-answer.txt b/peer-review/1-answer.txt index 76244bc..6ccf8d4 100644 --- a/peer-review/1-answer.txt +++ b/peer-review/1-answer.txt @@ -12,7 +12,7 @@ is in line with the very limited word-count and maximum of 12 references to be used in bibliography. We were also eager to get that extensive review out (which took a lot of -time, and most of the tools were actually run andtested). Hence we +time, and most of the tools were actually run and tested). Hence we discussed this privately with the editors and this solution was agreed upon: we include that extended review as appendices on the arXiv[2] and Zenodo[3] pre-prints of this paper and mention those publicly available @@ -43,7 +43,7 @@ ANSWER: (e.g. longevity). ANSWER: It has now been clearly defined in the first paragraph of Section -II. With this definition, the main argument of the paper much more clear, +II. With this definition, the main argument of the paper is much more clear, thank you (and the referees for highlighting this). ------------------------------ @@ -229,7 +229,7 @@ ANSWER: ANSWER: Thank you for highlighting these points. Appendix B starts with a subsection titled "suggested rules, checklists or criteria" that review of -existing criteria. that include the proposed sources here (and others). +existing criteria. That include the proposed sources here (and others). arXiv:1401.2000 has been added in Appendix A as an example paper using virtual machines. We thank the referee for bringing up this paper, because @@ -496,7 +496,7 @@ paper. the maintaining community, which creates another problem within the perspective of the article. -ANSWER: Thank you very much for highlighting this point it was not included +ANSWER: Thank you very much for highlighting that this point was not included for the sake of length, it has been fitted into the introduction now. ------------------------------ @@ -539,7 +539,7 @@ but it has been cited in Appendix A (where we discuss Singularity). ANSWER: The FAIR principles have been mentioned in the main body of the paper, but unfortunately we had to remove its citation the main paper (like -MANY others) within the maximum limit 12 references. We have cited it in +many others) within the maximum limit 12 references. We have cited it in Appendix B. ------------------------------ @@ -828,7 +828,7 @@ particular project in their own particular repository. They can also use all types of Git-based collaborating models to work together on a project that is not yet finished. -Figure 2 infact explicitly shows such a case: the main project leader is +Figure 2 in fact explicitly shows such a case: the main project leader is committing on the "project" branch. But a collaborator creates a separate branch over commit '01dd812' and makes a couple of commits ('f69e1f4' and '716b56b'), and finally asks the project leader to merge them into the @@ -925,6 +925,13 @@ VMs in 2011 and 2014 are no longer active, and how even Dockerhub will be deleting containers that are not used for more than 6 months in free accounts (due to the large storage costs). +Raul: it would be interesting to mention here that Maneage has the criterion of +"Minimal complexity". This means that even if for any reason the project is not +able to be run in the future, the content, analysis scripts, etc. are accesible +for the interested reader (because it is in plain text). So, it is transparent +in any case and the interested reader can follow the analysis and study the +different decissions of each step (why and how the analysis was done). + ------------------------------ |