MAJ terminée. Nous sommes passés en version 14.6.2 . Pour consulter les "releases notes" associées c'est ici :

https://about.gitlab.com/releases/2022/01/11/security-release-gitlab-14-6-2-released/
https://about.gitlab.com/releases/2022/01/04/gitlab-14-6-1-released/

Commit 9951d55f authored by Ludovic Courtès's avatar Ludovic Courtès
Browse files

article: Add basic metadata and structure.

* article/bibliography.bib, article/content.tex, article/metadata.yaml:
Initialize.
parent 8dfa286e
@article{Rougier:2018,
doi = {10.1038/d41586-018-04628-w},
year = {2018},
month = apr,
publisher = {Springer Nature},
volume = {556},
number = {7701},
pages = {309--309},
author = {Rougier, Nicolas P. and Hinsen, Konrad},
title = {Code reviewing puts extra demands on referees },
journal = {Nature},
}
@article{Science:2018,
doi = {10.1126/science.359.6377.725},
author = {Hutson, Matthew},
url = {http://science.sciencemag.org/content/359/6377/725},
year = {2018},
month = feb,
volume = {359},
number = {6377},
title = {Artificial intelligence faces a replication crisis},
journal = {Science},
}
@Misc{Roboto:2011,
author = {Christian Robertson},
title = {The Roboto family of fonts (Google)},
url = {https://github.com/google/roboto},
year = 2011,
note = {Apache License, verison 2.0},
}
@Misc{SourceSerifPro:2014,
author = {Frank Grießhammer},
title = {Source Serif Pro (Adobe Systems)},
url = {https://github.com/adobe-fonts/source-serif-pro},
year = 2014,
note = {SIL Open Font License, version 1.1},
}
@Misc{SourceCodePro:2012,
author = {Paul D. Hunt},
title = {Source Code Pro (Adobe Systems)},
url = {https://github.com/adobe-fonts/source-code-pro},
year = 2012,
note = {SIL Open Font License, version 1.1},
}
@article{Topalidou:2015,
author = {Topalidou, Meropi and Rougier, Nicolas P.},
title = {{[Re] Interaction between cognitive and motor cortico-basal
ganglia loops during decision making: a computational study}},
journal = {ReScience},
year = 2015,
volume = 1,
number = 1,
doi = {10.5281/zenodo.27944},
}
@article{Rougier:2017,
doi = {10.7717/peerj-cs.142},
author = {Nicolas P. Rougier and Konrad Hinsen and Frédéric Alexandre
and Thomas Arildsen and Lorena Barba and Fabien
C. Y. Benureau and C. Titus Brown and Pierre de Buyl and Ozan
Caglayan and Andrew P. Davison and Marc André Delsuc and
Georgios Detorakis and Alexandra K. Diem and Damien Drix and
Pierre Enel and Benoît Girard and Olivia Guest and Matt
G. Hall and Rafael Neto Henriques and Xavier Hinaut and Kamil
S Jaron and Mehdi Khamassi and Almar Klein and Tiina Manninen
and Pietro Marchesi and Dan McGlinn and Christoph Metzner and
Owen L. Petchey and Hans Ekkehard Plesser and Timothée Poisot
and Karthik Ram and Yoav Ram and Etienne Roesch and Cyrille
Rossant and Vahid Rostami and Aaron Shifman and Joseph
Stachelek and Marcel Stimberg and Frank Stollmeier and
Federico Vaggi and Guillaume Viejo and Julien Vitay and Anya
Vostinar and Roman Yurchak and Tiziano Zito},
title = {{Sustainable computational science: the ReScience
initiative}},
journal = {{PeerJ} Computer Science},
month = 12,
volume = 3,
pages = {e142},
year = 2017,
github = {https://github.com/ReScience/ReScience-article-2},
keywords = {journal},
tags = {OS},
@inproceedings{courtes06:storage,
author = {Courtès, Ludovic and Killijian, Marc-Olivier and Powell, David},
institution = {{LAAS-CNRS}},
title = {Storage Tradeoffs in a Collaborative Backup Service for Mobile Devices},
booktitle = {Proceedings of the Sixth European Dependable Computing Conference},
year = 2006,
month = oct,
address = {Coimbra, Portugal},
pages = {129--138},
publisher = {{IEEE CS Press}},
url = http://www.laas.fr/mosaic/,
}
Three years, we launched ReScience, a new scientific journal aimed at publishing the
replication of existing computational research. Since ReScience published its first
article\supercite{Topalidou:2015}, things have been
going steadily. We are still alive, independent and without a budget. In the
meantime, we have published around 24 articles (mostly in computational
neuroscience \& computational ecology) and the initial
\href{https://rescience-c.github.io/board/}{editorial board} has grown from
around 10 to roughly 100 members (editors and reviewers), we have advertised
ReScience at several conferences worldwide, gave some
interviews\supercite{Science:2018}, and published an article introducing
ReScience in PeerJ~CS\supercite{Rougier:2017}. Based on our
experience\supercite{Rougier:2018} at managing the journal during these three
years, we think that time is ripe for some changes.
This article reports on the effort to reproduce the results shown
in \textit{Storage Tradeoffs in a Collaborative Backup Service for
Mobile Devices}\supercite{courtes06:storage}, an article published in
2006, more than thirteen years ago. Additionally, it describes a way to
capture the complete dependency graph of this article and the software
and data it refers to, making it fully reproducible.
\subsubsection{ReScience C \& ReScience X}
\subsubsection{Getting the Source Code}
The biggest and most visible change we would like to propose is to change the
name of the journal ``ReScience'' in favor of ``ReScience C'' where the C
stands for (c)omputational. This change would be necessary to have consistent
naming with the upcoming creation of the ``ReScience X'' journal that will be
dedicated to e(x)perimental replications and co-directed by E.Roesch
(University of Reading) and N.Rougier (University of Bordeaux). The name
``ReScience'' would then be used for the name of a non-profit organization
(that is yet to be created) for the two journals as well as future journals
(such as the utopian CoScience\supercite{Rougier:2017} or a future and
tentative ``ReScience T'' for theoretical science).
\subsubsection{Building the Source Code}
\subsubsection{Running the Benchmarks}
\subsubsection{A new submission process}
The current submission process requires authors to fork, clone and branch the
submission repository in order to write their article and to place code and
data at the relevant places in the forked repository. Once done, authors have
to push their changes and to make a pull request that is considered as a
submission. This process is cumbersome for authors and has induced many
troubles for editors as well once the article is accepted and ready to be
published, mostly because of the complexity of the editing procedure. In order
to make life easier for everyone, we greatly simplified the submission process
for ReScience C and X. Authors are now responsible for getting a DOI for their
code \& data and only have to submit a PDF and a metadata file in a GitHub
issue.
We also provide Python programs that largely automate the subsequent editing
process. We will still archive the submission on Zenodo but this archive will
be made for the final PDF only. However, both the PDF and the Zenodo entry will
contain all associated DOIs (data and code).
\subsubsection{A simplified publishing process}
In ReScience, we have have been using a combination of
\href{https://daringfireball.net/projects/markdown/syntax}{markdown} and
\href{http://pandoc.org/}{pandoc} for producing both the draft and the final
version of all the published articles. This had worked reasonably well until it
started to cause all kind of problems for both authors and editors, especially
with the reference and citation plugins. Consequently, articles will be now
submitted directly in PDF with accompanying metadata in a separate file using
the \href{https://en.wikipedia.org/wiki/YAML}{YAML} format (they were
previously embedded in the markdown file). Once an article has been accepted,
authors will be responsible for updating the metadata and for rebuilding the PDF if
necessary. We could also consider using the
\href{https://github.com/openjournals/whedon}{Whedon} API that helps with automating
most of the editorial tasks for \href{http://joss.theoj.org/}{JOSS} and
\href{http://jose.theoj.org/}{JOSE}. This will most probably require some
tweaking because our publishing pipeline is a bit different.
\subsubsection{A new design}
The combination of markdown and pandoc has also severely limited the layout and
style possibilities for the article template and since we are switching to
\LaTeX, this is the opportunity to propose a new design based on a more elegant
style, using a new font stack\supercite{SourceSerifPro:2014, Roboto:2011,
SourceCodePro:2012} (you are currently reading it). The goal is to have a
subtle but strong identity with enhanced readability. Considering that articles
will be mostly read on screen (as opposed to printed), we can benefit from a
more ethereal style. Once this design will have stabilized, an
\href{https://www.overleaf.com/}{overleaf} template will be made available for
those without a \TeX~installation. If a \TeX~expert is ready to help review
the template (and possibly rewrite it as a class), their help would be much
welcome and appreciated. The same holds for LibreOffice, Word or Pages, any
template is welcome, just contact us beforehand such that we can coordinate
efforts.
\subsubsection{Editorials, letters and special issues}
ReScience C remains dedicated to the publication of computational replications
but we (i.e., the editorial team) would like to have the opportunity to
publish \emph{editorials} when deemed necessary and to give anyone the
opportunity to write \emph{letters} to the community on a specific topic
related to reproducibility. Both editorials and letters are expected to be 1 or
2 pages long (but no hard limit will be enforced), will be (quickly) peer reviewed,
and will be assigned a DOI. Furthermore, with the advent of reproducibility
hackatons worldwide, we will host {\em special issues} with guest editors (such
as, for example, the organizers of a hackaton) in order to publish the results
and to enhance their discoverability. Each entry will have to go through the
regular open peer-reviewed pipeline.\\
We hope that most readers will agree on the proposed changes such that we can
commit to them in the next few weeks. The review for this editorial is open (as
usual) and anyone can comment on and/or oppose any of the proposed changes. New
ideas are also welcome.
\subsubsection{Reproducing this Article}
......@@ -5,57 +5,33 @@
# - For a successful replication, it shoudl be prefixed with "[Re]"
# - For a failed replication, it should be prefixed with "[¬Re]"
# - For other article types, no instruction (but please, not too long)
title: "ReScience (R)evolution"
title: "[Re] Storage Tradeoffs in a Collaborative Backup Service for Mobile Devices"
# List of authors with name, orcid number, email and affiliation
# Affiliation "*" means contact author (required even for single-authored papers)
authors:
- name: Konrad Hinsen
orcid: 0000-0003-0330-9428
email: konrad.hinsen@cnrs.fr
affiliations: 1,2
- name: Ludovic Courtès
orcid: 0000-0003-0330-XXXX
email: ludovic.courtes@inria.fr
affiliations: 1,*
- name: Nicolas P. Rougier
orcid: 0000-0002-6972-589X
email: Nicolas.Rougier@inria.fr
affiliations: 3,4,5,* # * is for contact author
# List of affiliations with code (corresponding to author affiliations), name
# and address. You can also use these affiliations to add text such as "Equal
# contributions" as name (with no address).
affiliations:
- code: 1
name: Centre de Biophysique Moléculaire, CNRS UPR4301
address: Orléans, France
- code: 2
name: Synchrotron SOLEIL, Division Expériences
address: Gif sur Yvette, France
- code: 3
name: INRIA Bordeaux Sud-Ouest
name: Inria
address: Bordeaux, France
- code: 4
name: LaBRI, Université de Bordeaux, Institut Polytechnique de Bordeaux,
Centre National de la Recherche Scientifique, UMR 5800
address: Talence, France
- code: 5
name: Institut des Maladies Neurodégénératives, Université de Bordeaux,
Centre National de la Recherche Scientifique, UMR 5293
address: Bordeaux, France
# List of keywords (adding the programming language might be a good idea)
keywords: rescience c, rescience x
keywords: rescience c, rescience x, resilience, fault tolerance, C, Scheme
# Code URL and DOI/SWH (url is mandatory for replication, doi after acceptance)
# You can get a DOI for your code from Zenodo, or an SWH identifier from
# Software Heritage.
# see https://guides.github.com/activities/citable-code/
code:
- url: https://github.com/rescience-c/template
- url: https://gitlab.inria.fr/lcourtes-phd/edcc-2006-redone
- doi:
- swh:
......@@ -66,22 +42,18 @@ data:
# Information about the original article that has been replicated
replication:
- cite: # Full textual citation
- bib: # Bibtex key (if any) in your bibliography file
- url: # URL to the PDF, try to link to a non-paywall version
- cite: Storage Tradeoffs in a Collaborative Backup Service for Mobile Devices
- bib: courtes06:storage
- url: https://hal.inria.fr/hal-00187069/en
- doi: # Regular digital object identifier
# Don't forget to surround abstract with double quotes
abstract: "Three years have passed since ReScience published its first article
and since September 2015, things have been going steadily. We're
still alive, independent and without a budget. In the meantime, we
have published around 20 articles (mostly in computational
neuroscience & computational ecology) and the initial has grown
from around 10 to roughly 100 members (editors and reviewers), we
have advertised ReScience at several conferences worldwide, gave
some interviews and we published an article introducing ReScience in
PeerJ. Based on our experience at managing the journal during these
three years, we think the time is ripe for proposing some changes."
abstract: "This article reports on the effort to reproduce the results
shown in \"Storage Tradeoffs in a Collaborative Backup
Service for Mobile Devices\", an article published in
2006. Additionally, it describes a way to capture the
complete dependency graph of this article and the software
and data it refers to, making it fully reproducible."
# Bibliography file (yours)
bibliography: bibliography.bib
......@@ -91,14 +63,14 @@ bibliography: bibliography.bib
# * Editorial
# * Letter
# * Replication
type: Editorial
type: Replication
# Scientific domain of the article (e.g. Computational Neuroscience)
# (one domain only & try to be not overly specific)
domain:
domain: Fault Tolerance
# Coding language (main one only if several)
language:
language: C
# To be filled by the author(s) after acceptance
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment