Skip to article frontmatterSkip to article content

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

This section provides a high-level guide to contributing to EDS book via the core repository and/or notebook submissions. We encourage you to read through the following sections to learn more about how you can contribute under open review principles (Figure 1).

Scriberia illustration showcasing some features of the Open Peer Review process. The figure has a title Open Peer Review with a three layer cake. The top layer of the cake has three individuals (authors) looking at a document with a subtitle Supporting Quality. The mid layer has five individuals, one of them in a wheelchair, looking at the top floor. Three of the individuals have a comment icon with an eye symbol referring to transparency. The bottom layer has seven individuals, five of them with the eye comment icon, representing that they are reviewing the 'cake', or paper. The left side of the cake has an individual with the subtitle recognition. The right side has a paper with some annotations of the review process with the subtitle content and process.

Figure 1:EDS book follows open review principles where identities, participation, interactions are publicly available and acknowledged. Illustration by Scriberia as part of The Turing Way book dash in May 2023 Community & Scriberia, 2023.

If you find that you have questions that are not discussed below, please let us know through one of the many ways to get in touch.

Core repository

Structure

The public GitHub repository has the following structure:

| Environmental Data Science book
| ├── **/.github**
| │   ├── ISSUE_template
| │   ├── workflows
| │   └── ...
| ├── **/book**
| │   ├── myst.yml
| │   └── ...
| ├── CODE_OF_CONDUCT.md
| ├── CONTRIBUTING.md
| └── ...

The .github folder refers to GitHub related deployment files and templates of issues/pull requests usually curated by the repository maintainers or developers. The book folder holds the website content and other relevant files (e.g. configuration files).

The myst.yml file dictates the project and site configurations. For instance, the project part declares the table of content i.e. sections found in the book folder. The current version of the book consists of six key sections:

Who can contribute

We describe two defined roles for contributing to the core repository:

Maintainers/Developers

Keep the source code updated, track new contributions and/or implement features.

Readers/Users

Read/share content, occasionally raise errors such as typos and bugs and fix them.

Notebooks

Scope

We consider submissions from all areas of environmental science. This includes (but it is not restricted to):

Submissions could be at any stage from notebook idea to a working prototype from an existing GitHub repository. The notebook should address scientific and/or technical aspects that EDS book audience could adopt, reuse, and/or extend for their purposes.

The optimal notebook has between 100 and 500 for physical lines of code in Code Cells, and 500 to 5000 comments in Markdown Cells. We have determined these ranges from the pool of published notebooks (by March 2023) using cloc, a handy open-source tool to count blank lines, comment lines, and physical lines of source code in many programming languages.

Notebook submissions to EDS book must:

Themes

EDS notebooks are categorized under four proposed topics or themes:

Publication process

The main steps when submitting and publishing EDS book notebooks are:

Who can contribute

The publishing process of EDS book notebooks is open to all members of the community. We list below the main roles and their responsibilities:

Community

Propose, explore and/or make constructive comments of the notebook at the idea stage (optional) or after publication.

View guidelines for community »

The table below indicates the key roles within the publication of EDS book notebooks according to the publication steps mentioned above. Mandatory and optional participation are illustrated by ✅ and ⭕ icons, respectively.

StageWhere in GitHubAuthorsReviewersEditor-in-ChiefEditorsCommunity
Notebook ideaEDS repo (issues)
PreparationNotebook repo (pull request)
Prereview and ReviewEDS repo (issues)
Post-printNotebook repo (pull request)
PublicationNotebook repo (main branch)⭕ ️
Post-publicationNotebook repo (issues)⭕ ️

Conflict of interest

The definition of a conflict of Interest in peer review is a circumstance that makes you “unable to make an impartial scientific judgement or evaluation” (PNAS Conflict of Interest Policy). EDS book community is concerned with avoiding any actual conflicts of interest, and being sufficiently transparent that we avoid the appearance of conflicts of interest as well.

Authorship

The authors themselves assume responsibility for deciding who should be credited with co-authorship, and co-authors must always agree to be listed. In addition, co-authors agree to be accountable for all aspects of the work, and to notify EDS book if any retraction or correction of mistakes are needed after publication.

Confidential requests

Please write environmental.ds.book@gmail.com with confidential matters such as retraction requests, report of misconduct, and retroactive author name changes. In case of a name change, the DOI will be unchanged and the notebook will be updated without publishing a correction notice or notifying co-authors.

Recognising Contributions

We recognise all kinds of contributions, from fixing small errors, to developing documentation, maintaining the project infrastructure, writing or reviewing narrative and/or executable notebooks.

EDS book follows the all-contributors specifications. The all-contributors bot usage is described here. You can see a list of contributors here.

Need Help?

If you’re stuck or need assistance:

Code of Conduct

Please note that EDS book open-source repository and community are aligned with a Contributor Code of Conduct. By contributing to EDS book you agree to abide by its terms.

Attribution

Some material in this section and derived guidelines have been adapted from Neurolibre, the Journal of Open Source Education and pyOpenSci reviewing guidelines, released under CC BY 3.0, CC BY 4.0 and CC BY-SA 4.0, respectively.

References
  1. Community, T. T. W., & Scriberia. (2023). Illustrations from The Turing Way: Shared under CC-BY 4.0 for reuse. Zenodo. 10.5281/ZENODO.7587336