Feature Request

I was recommended the book during a presentation about it and was told this was the link to browse.

https://the-environmental-ds-book.netlify.app/welcome.html

When I browsed the book I first clicked on Oceans but it says "under construction" I then clicked "Forests" it said the same. I think clicked on Forest: Sensors. It also said under construction.

As a casual reader it was difficult to find the non-blank parts of the book. To be honest, if I had had less time I would have simply assumed there was an error and the book was completely empty.

Describe the solution you'd like

Is there some way the filled in sections could be highlighted more prominently or the generic sections (E.g. Forest, Ocean) could contains pointers to actual content.

Describe alternatives you've considered

Any mechanism that made the filled in sections more prominent than the non filled in ones would work. But I'm not familiar enough with the technology that turns text into the book to make a coherent suggestion.

Additional information

Notebook Review: Issue #171

Submitting author: @ancazugo @SkirOwen @ViktorDomazetoski

Repository: https://github.com/eds-book-gallery/CI2023-RC-team2

Paper: https://doi.org/10.1017/eds.2022.17

Editor: @ampersandmcd @annefou

Reviewer: @asthanameghna @NHomer-Edi @dbhatedin

Managing EiC: @acocac

Status

Reviewer instructions & questions

Hi 👋 @asthanameghna @NHomer-Edi @dbhatedin, please carry out your review in this issue by updating the checklist below.

As a reviewer, you contribute to the technical quality of the content published by our community.

Before the review, EiC checked if the submission fits the minimum requirements.

The quality of the proposed contribution can be assessed through scientific, technical and code criteria.

The reviewer guidelines are available here: https://edsbook.org/publishing/guidelines/guidelines-reviewers.html.
Any questions/concerns please let @ampersandmcd know.

Review checklist for @asthanameghna

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Review checklist for @NHomer-Edi

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Review checklist for @dbhatedin

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Additional instructions

Reviewer general comments are welcome on this REVIEW issue or directly to the notebook repository.

If you do the latter, you will find a Pull Request titled REVIEW where you can carry out the discussion with authors through ReviewNB, a third-party plugin in GitHub for displaying and commenting Jupyter Notebooks (see further details here).

In addition to ReviewNB, we suggest to explore or run the notebook in:

• Binder (run): Click the Launch Binder button at the top level of this message.

Feature Request

The book is currently build locally and hosted in GH pages. While this is the common and fastest way to host a jupyter book, it won't be the optimal way to deploy the book.

Describe the solution you'd like

Netlify is a continuous deployment service that can automatically build an updated online copy of a Jupyter Book. Netlify also supports open-source projects with a dedicated policy. One of the main advantages of Netlify is a larger build minutes allowance (3 Builds per minute) than GH pages (10 Builds per hour). Further info of the additional features can be found here.

Describe alternatives you've considered

Whilst commercial alternative exists, Netlify loves open-source projects and for instance The Turing Way uses it to deploy, build and host its book.

Additional information

          My other comment relates to the landing page. I suggest steer users more directly towards the gallary, e.g., by showing 3-4 highlight gallary cards with a link to the full set (similar to https://sci.vision), or even merge the front page and gallary into one page. 

The gallary is really clear and my sense is that a user would instantly undertand what the EDSbook is all about - by comparison the current front page is a little text heavy and isn't as eye catching

Originally posted by @scotthosking in #139 (comment)

Notebook Pre-Review

Submitting author: @garimamalhotra @jedpe @dapivei

Repository: https://github.com/eds-book-gallery/repro-challenge-team-3

Paper: https://doi.org/10.1017/eds.2022.10

Editor: @annefou

Reviewer: @christopheredsall @oscarbau @RachelFurner

Managing EiC: @acocac

Status

Author instructions

Thanks for submitting your notebook to EDS book.

Editor instructions

Thank you for considering managing the review workflow of a notebook submission to EDS book.

Please find and assign reviewers and start the main review.

Feature Request

In other gitbooks such as this course
(see course repo) there are "Click to show" buttons for code which make the pages tidier as code is hidden by default.

This would be a nice feature for the environmental AI book to implement.

What is the notebook about?

Landsat data is probably the longest standardized timeseries of remotely sensed data for land use. Plant phenology is an important proxy for climate change effects. Using long time series of RS data, would allow to see long-term trends, such as drifts on Start-of-season (SOS) and End-of-season (EOS) dates over decades, and how this occurs in the globe.

A secondary goal of the notebook would be how to pull out Landsat data and work on longer time-scales.

• Landsat datasets are available at Google STAC repository : https://gee.stac.cloud/?cp=1&t=catalogs
• This would be loosely inspired on NASA ARSET training on Phenology: https://appliedsciences.nasa.gov/join-mission/training/english/arset-understanding-phenology-remote-sensing
• We would use some concepts of Pangeo as a stack:
  • Using STAC endpoints of repositories;
  • Using intake as an ETL/Exploratory tool;
  • Using Rasterio for Viz.

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

What is the notebook about?

This notebook introduces raster land cover data with simple manipulation and basic exploratory analysis techniques. The notebook will be based largely on the existing notebooks I have used for teaching and will examine:

• Overview of raster data characteristics
• Reading raster data
• Plotting categorical raster maps
• Analysing aggregate change (through bars charts and similar visualisation)
• Analysing zonal change (using ancillary vector data)
• Analysing pixel-by-pixel change (including use of sankey diagrams)

There are now many data sources of classified (categorical) land cover data that are useful for Environmental Data Science. These include:

• ESA CCI land cover, 300m spatial resolution global extent for years 1992-2015
• Copernicus Global Land Cover, 100m spatial resolution global extent for years 2015-2019
• USGS LCMAP, 30m spatial resolution for USA for years 1985-2020
• UKCEH LCMs, various spatial resolutions for UK for various years 1990-2020
• mapbiomas, 30m spatial resolution for Brazil for years 1985-2020

Considerations for deciding which of these sources to use in this notebook include:

• licencing: some of these data sources are have open licences, others are more restrictive (notably UKCEH LCMs)
• data access: some data sources can easily be accessed programmatically via API, others less easily
• data volume: fine-grained data over large extents result in large data (e.g. ESA CCI 300m global extent for a single year is ~300MB)

Code and packages used in this notebook will initially be those used in the original teaching notebooks, notably:

• rasterio with numpy ndarrays
• pandas and geopandas
• matplotlib and seaborn

In time, the code can be changed to use packages from the pangeo ecosystem

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other: Data Manipulation and Basic Analysis (best fits in the Exploration section of the current Gallery)

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Hi @acocac Yes, happy to help develop the submission guidelines, mainly by asking questions to help my understanding of the review process! (and then I can suggest text later).

For example, the Reviewing guidelines state that

the interaction of the authors [and reviewers?] is facilitated through ReviewNB

This would benefit (me at least!) from providing a little more guidance. ReviewNB looks great but I'm not entirely clear on how to use it within the process of deciding on changes (and editing the notebook). For example, I see that I can write responses to comments from reviewers in the text box - should I make a reply about a suggested edit in ReviewNB before making a notebook edit? Or just go ahead and make the notebook edit (see below) as I see fit and then reply? Who clicks the Resolve Conversation button? I assume that's for the reviewer to do once they are happy the comment has been appropriately addressed? How does that link to the editor's responsibility of approving PRs?

Then, the second major issue for me currently: how should I actually make edits to the notebook in response to the reviewer comments? I saw you have made some commits (editing file paths), so I pulled the repo - that has brought in the change that you made to the notebook file (now named general-exploration-landcover_io.ipyn) but not your suggested edits in the notebook itself. I then realised that's because I pulled from the main branch, but your edits within the notebook are on the review_round1 branch with an outstanding PR than needs to be merged to main.

As you noted above, you are editor so have responsibility for approving PRs. Do I just checkout the review_round1 branch, make edits, and submit PRs that you (as editor) then deal with merging into main? (What it a reviewer doesn't like my edit - which links back to my first set of questions).

Thanks!

Originally posted by @jamesdamillington in #99 (comment)

Describe the proposed improvement to the documentation

The current domain, https://the-environmental-ds-book.netlify.app/, is provided by Netlify. If Netlify doesn't longer exist, we should anticipate a more long-term sustainable solution. We use Netlify to primarily deploy documentation previews. Read the Docs offers the same service (see here), so this could be an alternative too.

The list of available domains in namecheap are:

• www.edsbook.org
• www.edsbook.io
• www.edsbook.net

If you have any additional suggestion(s), please post it/them in the issue thread.

Additional information

Related to WIP release of a new version #126 and roadmap of EDS book.

We expect to release it soon before AIUK (21-22 March) and annoucement of the CI2023 hackathon (14 March), when we will have some reasonable number of visitors/readers of the online resource.

Notebook Pre-Review

Submitting author: @Mukulikaa @Rutika-16

Repository: https://github.com/eds-book-gallery/reproduce-deep-prior-4Dvar

Paper: https://doi.org/10.1017/eds.2022.31

Editor: @acocac

Reviewer: @crlna16 @tinaok @polpel

Managing EiC: @acocac

Status

Author instructions

Thanks for submitting your notebook to EDS book.

Editor instructions

Thank you for considering managing the review workflow of a notebook submission to EDS book.

Please find and assign reviewers and start the main review.

Notebook Pre-Review

Submitting author: @annefou

Repository: https://github.com/eds-book-gallery/teamX-toy-repo

Notebook idea issue: N/A

Editor: @acocac

Reviewer: @acocac

Managing EiC: @acocac

Status

Author instructions

Thanks for submitting your notebook to EDS book.

@acocac if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @).

Editor instructions

Thank you for considering managing the review workflow of a notebook submission to EDS book.

Please find and assign reviewers and start the main review.

Feature Request

The Environmental AI book has evolved since its relatively short inception. As the content and sections grow, we think it would be better to rename the book to the Environmental Data Science book or Environmental Data Stories. The proposed names reflect better the vision of the project as we aim to showcase and increase the awareness of open-source tools for collaborative, reproducible and transparent Environmental Data Science.

Describe the solution you'd like

This change will take effect immediately after a consultation to the community. The only drawback is URLs of previous demonstrators (incl. Binder) won't work so we'll have to notify this to all contributors/end-users. Note there is a journal named Environmental Data Science. To differentiate and avoid confusions with the journal, Environmental Data Stories seems to be a feasible alternative. At some point, it would be great to join forces with the Turing Data Stories project and collaborate together towards a common goal.

Describe alternatives you've considered

Keep the actual name, however, this could limit future contributions to only AI-related topics. Some potential contributions are data preprocessing, post-processing, dashboards, etc which would be better suited under the Data Science umbrella.

Additional information

I'm consulting the proposed change with the existing contributors.

Describe the proposed improvement to the documentation

Inspired by TTW Way of Working, this files facilitates the understanding of the project to readers, contributors and users.

The propose file should contain:

• Project Members (current and previous)
• Commitments
• Communication
• Project management

Additional information

Feature Request

Describe the solution you'd like

To support the transparency of the open-source tools used by the EnvDS notebooks, it would be great to inform them and their connections through interactive plotting or dashboards. This can be added as a new section in the EnvDS book.

Describe alternatives you've considered

• Exploit existing platforms for interactive plotting and dashboards e.g. panel.
• Build upon existing open-source developments to map dependencies e.g. pygieons

Additional information

• We should think in optimal solutions to serve the proposed visualisations/dashboard.

Feature Request

The click to show feature was implemented according to a previous issue #17. However, for user experience it might be not clear that the button refers to a code block.

Describe the solution you'd like

Following the standard hide-input' tag, it would be great to customise the following new tag types:

• hide-input-plot > Click to show plotting code
• hide-input-libraries > Click to show libraries code
• hide-input-table > Click to show table code

Describe alternatives you've considered

The current documentation in jupyter book doesn't provide details how to customise tabs (see here). This information might be already addressed in other groups.

Additional information

Describe the proposed improvement to the documentation

The README of the current notebook repository template has the original instructions of 2i2c hub-user-image-template. We should improve the template of the available programming languages.

I wil report here the progress in each of the following templates:

• Python
• R
• Julia

And additional step is to set up the license as indicated in pyopencl.

Additional information

We should attribute the license of the original hub-user-image-template, but leave MIT as the main one.

What is the notebook about?

lorum asrs

Data Science Component

• Exploration
• Preprocessing
• Modelling
• Post-processing
• Other (e.g. Reproducibility): Reproducibility

Submission type

• Standard
• Special Issue
• Other (e.g. CI2023 Reproducibility Challenge): CI2023 Reproducibility Challenge

Programming language

• Python
• R
• Julia
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

xarray

• existing

Describe the proposed improvement to the documentation

The Pythia project has a new resource gallery which aims to refer useful resources for the geoscientific Python community. We should submit the EDSbook through the issue template.

Additional information

None

What is the notebook about?

Calculate dry season rainfall averages in Borneo based on a gridded dataset and create a time series

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Source of data: https://psl.noaa.gov/data/gridded/data.ncep.reanalysis.html
Publication: https://journals.ametsoc.org/view/journals/bams/102/12/BAMS-D-20-0117.1.xml

Steps are as follows:

1. Load gridded rainfall dataset
2. Create seasonal means
3. Extract the study region
4. Create area-averaged time series
5. Extract the dry season and restrict to the study timeframe
6. Plot the time series

Feature Request

The published notebook repositories uses Setup Miniconda from GitHub Marketplace to render the Jupyter file. While this is optimal to conda environments, 2i2c hub-user-image-template offers a wider support to other programming languages e.g. R and Julia.

Describe the solution you'd like

Implement changes i.e. replacing workflow actions according to the adapted python template from 2i2c hub-user-image-template.

Steps

• Set up the Quay.io repository
  • Use same name as the notebook repository
  • Add edsbook+github_actions in User and Robot Permissions
  • Add Quay.io credentials in the notebook repository
• Add 2i2c adapted workflow YML files into .github folder/workflows
• Remove Setup Miniconda YML file from .github folder/workflows
• Add new config file into the .github folder
• Remove old config file in the repo directory.
• Edit License and change Environmental-DS-Book to EDS book
• Add credits to 2i2c template in Attribution.
  • The workflow actions were adapted from 2i2c’s hub-user-image-template released under BSD-3-Clause license.
• Replace Published badge in README by Render badge.
• Check if the Render action works
  • If errors in cell outputs, ping according to the conda lock files
  • Regenerate and replace conda files

Notebooks

• Detecting floating objects using deep learning and Sentinel-2 imagery - OK
• Met Office UKV high-resolution atmosphere model data - OK
• MODIS MOD021KM and FIRMS - Fixed bug with dates (see #3)
• Tree crown detection using DeepForest - OK (additional changes in environment.yml)
• SEVIRI Level 1.5 - OK (additional changes in environment.yml)
• Tree crown delineation using detectreeRGB (additional changes in environment.yml and added apt.txt)
• Sea ice forecasting using IceNet (additional changes in environment.yml)
• Cosmos-UK soil moisture
• Concatenating a gridded rainfall reanalysis dataset into a time series
• Exploring Land Cover Data (Impact Observatory) (additional changes in environment.yml)

Describe alternatives you've considered

• 2i2c hub-user-image-template
• Customise GitHub actions using repo2docker
• Continue with Setup Miniconda

Additional information

Notebook Pre-Review

Submitting author: @ancazugo @SkirOwen @ViktorDomazetoski

Repository: https://github.com/eds-book-gallery/CI2023-RC-team2

Paper: https://doi.org/10.1017/eds.2022.17

Editor: @ampersandmcd

Reviewer: @asthanameghna @NHomer-Edi @dbhatedin

Managing EiC: @acocac

Status

Author instructions

Thanks for submitting your notebook to EDS book.

Editor instructions

Thank you for considering managing the review workflow of a notebook submission to EDS book.

Please find and assign reviewers and start the main review.

Feature Request

The current gallery chapter contains all notebooks indexed by theme with a drop-down list. This isn't the most attractive and accessible format for readers/users.

Describe the solution you'd like

@scotthosking has suggested a great idea to replace the drop-down list with a single section pointing to a gridded gallery similar to Pangeo Gallery or Scivision.

Describe alternatives you've considered

• Manually adding grids using Sphinx-design
• Automatically add items to the gallery with a YML. See JupyterBook Gallery

Additional information

What is the notebook about?

The idea of this notebook is to promote the use of MagGeo, a data fusion tool we developed at the University of St Andrews with the support of the British Geology Survey - BGS. The tool helps ecologists or animal movement researchers to link the earth's magnetic field data from satellite sources to GPS trajectories. Inspired by the Environmental Data Automated Track Annotation System (Env-DATA) Service a tool from Movebank and help researchers to get a better understanding of the geomagnetic variations across any GPS trajectories.

Despite there are several approaches in this regard, and in the last 5 to 10 years there are a lot of studies using controlled geomagnetic fields with particular species, what can be experienced in the wild might be completely different, in particular, because the earth's magnetic field is a highly dynamic force with sort spatio-temporal variations that may vary from day to hours. Therefore, despite years of study in this field, we still have little knowledge on how the wildlife can use or be affected by the geomagnetic field in their migration patterns, especially long-distance migrants. We can build in here a notebook describing why linking geomagnetic components is important to the study of wildlife migrations, describing what has been done at the moment, how our data fusion tool works and plotting some maps to display the results.

The tool is already public and can be found in: MagGeo

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Describe the proposed improvement to the documentation

Update the community templates to reflect the new general guidelines according to the new infrastructure.

Additional information

Local environment and OS

What is the notebook about?

Mapping nutrient flows in coastal waters using remotely-sensed multispectral data

Sentinel-2, https://scihub.copernicus.eu/
intake, xarray, hvplot, numpy

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Feature Request

The feature isn't an issue at all, but it is related in a long-term sustainability of the project. So far, the EnvAI book project started as a prototype (6 months). Thanks to the contributions and continuos feedback from the community, the overall structure, content and notebooks of the book look very solid to start a proper promotion among the target audience.

Describe the solution you'd like

Transfer the repository to the Alan Turing organisation. I've made some tests with a dummy repo to double check the existing community interactions (PR and issues) are transferred completely. The only drawback is URLs of previous demonstrators (incl. Binder) won't work so I have to notify this to all contributors.

Describe alternatives you've considered

Maintain the project in my personal GitHub account, however the visibility could be lower than being in the Turing repository.

Additional information

I'm consulting the transfer idea with the existing contributors.

Describe the proposed improvement to the documentation

The presentation decks should have new identity #132 and screenshots of the website and gallery.

Additional information

The current versions of the modelling and sensor templates don't include key metadata of the versioning (notebook and codebase), list of authors and contributions.

Describe the proposed improvement to the documentation

The community chapter should include a dedicated section for informing scientific open-source stacks suited to Environmental research. This might guide EDS book community-driven notebooks.

Additional information

Some features to be considered:

• Which criteria should we use to highlight specific scientific ecosystems?
• How and to what extend can we monitor automatically those developments?
• Which are the best metrics to monitor their health and traffic?

Preparation to the CI2023 Reproducibility Challenge

• Create a repo using FOSS4G Pangeo template
• Structure
  • Welcome [name=Alejandro]
    • About
    • Code of Conduct
    • Acknowledgements
  • Details
    • Timeline
    • Application
      • Participants
      • Reviewers
    • Judging [to improve]
    • Incentives
    • Our team
  • Preparation [name=Anne]
    • GitHub and ORCID account
    • Cloud EGI JupyterHub
    • Local Dockerised Environments
    • Data managment
      • Zenodo
      • Storage
  • Tutorials Resources [name=Alejandro]
    • Scientific Ecosystems
      • Pythia [Python]
      • OpenScape [R]
      • JuliaGeo [Julia]
    • GitHub
    • Jupyter
    • Zenodo
  • Teams [name=Anne]
    • Overview [add TTW scriberia image about Teams]
    • Team roles and responsability
    • Team logistics
    • Workflow for a Notebook Project [add screenshots]
  • Reference [name=All]
    • Glossary
    • Bibliography

Describe the proposed improvement to the documentation

So that the book remains consistent, it would be nice to have a "style guide" included in the contributor documentation so that contributors know how to write narrative pieces for the book.

For example, I notice some inconsistencies between the use of “Deep Learning” & “deep learning” and “Environmental data science” & “Environmental Data Science” and "AI" & "Artificial Intelligence"

Additional information

Other things this could include:
• Rules on capitalisation.
• A list of accepted abbreviations and acronyms which will be at the beginning/end of the book so that they do not need to be defined by every contributor.
• Number formatting like time and date and “%” vs. “per cent”.
• Punctuation guidelines.
• Formatting guidelines including bold/italic/underline and links

What is the notebook about?

This notebook would be about the data exploration, tidying, and analysis of ice-cycle variables calculated from the open-sourced database, the Water Survey of Canada (https://wateroffice.ec.gc.ca/)

Climate change is causing shifts in the timing and volume of river flow, ice coverage, and ice break-up. Northern boreal rivers maintain thick ice coverage every winter, and a predictable seasonal spring-break up season called freshet. This ice-break up is linked to key ecological processes: for example, it creates ice jams and floods, which replenish nearby wetlands with water and sustain rich habitat for aquatic life. In some cases, these flood events are the main source of water, and many species rely on these fresh water inputs to complete their life cycles and reproduce.

With climate change, it is unclear how the timing of freeze-up and spring break-up events is changing, and what this might mean for life downstream. Understanding historical ice cycles in northern rivers in addition to how they might be changing can help scientists, managers, and communities know how to adapt in the face of this change.

In this notebook, I will extract, tidy, explore, and clean open-sourced hydrological data, and calculate the timing and onset of freshet, the timing of freeze-up and break-up dates, and length of continuous ice coverage each year. I will calculate a Mann-Kendall statistical test, which is a non-parametric test that detects a monotonic trend (upwards or downwards) in the data. I will also visualize the data using line graphs.

Data is open-source, from the Water Survey of Canada: https://wateroffice.ec.gc.ca/
R package (tidyhydat) used to extract the data from the database: https://cran.r-project.org/web/packages/tidyhydat/index.html
R package (trend) used for change analysis: https://cran.r-project.org/web/packages/trend/index.html
Functions to calculate the ice-variables: functions created by author: https://github.com/Jacqui-123/EFlows-Project/blob/main/Eflows_FUNCTIONS.R
other packages used: tidyverse/ggplot

Data Science Component

• Exploration
• Preprocessing
• Modelling
• Post-processing
• Other (e.g. Reproducibility):

Submission type

• Standard
• Special Issue
• Other (e.g. CI2023 Reproducibility Challenge):

Programming language

• Python
• R
• Julia
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Feature Request

Describe the solution you'd like

Let others know how to correctly cite the Environmental Data Science book.

Describe alternatives you've considered

None.

Additional information

The file will be generated through cffinit.

Describe the proposed improvement to the documentation

The proposed version aims to cover major changes addressed in separated issues, some of them linked to specific PRs. See the detailed changes below:

Core Features

Notebooks Infrastructure

• #108
  • #127
  • #135
  • #137

Project management

• #130
• #138
• #125
  • #132
• #129
  • #133

Web interface

Notebooks Gallery

• #122
• #134
  • #139
  • #140
• #144
  • #145

Notebooks Publishing

• #115
  • #117
  • #131
• #136

Community

• #149

Additional information

Following the SemVer, the proposed version 0.1.0 breaks some previous URLs of published notebooks. All them will be placed under the chapter section. The current and previous versions have separate subsections by theme i.e. exploration, preprocessing, etc. This is unfeasible for long term maintainance (themes name might change i.e. recategorisation).

Special note: all coming releases with minor version increments (in development or production) will include a codename. As a lead of EDS book it's my desire to start with Matilda. Future codenames will be consulted with the EDS book community!

Describe the bug

Research objects of listed notebooks below are pointing to old URLs.

• Detecting floating objects using deep learning and Sentinel-2 imagery
• Met Office UKV high-resolution atmosphere model data
• MODIS MOD021KM and FIRMS
• Tree crown detection using DeepForest
• SEVIRI Level 1.5
• Tree crown delineation using detectreeRGB
• Sea ice forecasting using IceNet
• Cosmos-UK soil moisture
• Concatenating a gridded rainfall reanalysis dataset into a time series
• Exploring Land Cover Data (Impact Observatory)

How To Reproduce

1. Go to RoHub
2. Open URLs in the tool folder
3. Broken website

Expected behaviour

Open a working URL

Environment (generate for Linux, macOS and 64-bit Windows)

N/A. Browser.

Additional information

Additional checks include:

• Set main entity as Jupyter Notebook
• Set publisher and copyright to EDS book community
• Associate a community, in this case EDS book community
• Approximate to 100% completeness
• Assign a DOI (snapshop) using Zenodo

Notebook Review: Issue #170

Submitting author: @garimamalhotra @jedpe @dapivei

Repository: https://github.com/eds-book-gallery/repro-challenge-team-3

Paper: https://doi.org/10.1017/eds.2022.10

Editor: @annefou

Reviewer: @oscarbau @RachelFurner @ricardobarroslourenco

Managing EiC: @acocac

Status

Reviewer instructions & questions

Hi @christopheredsall @oscarbau @RachelFurner @ricardobarroslourenco, please carry out your review in this issue by updating the checklist below.

As a reviewer, you contribute to the technical quality of the content published by our community.

Before the review, EiC checked if the submission fits the minimum requirements.

The quality of the proposed contribution can be assessed through scientific, technical and code criteria.

The reviewer guidelines are available here: https://edsbook.org/publishing/guidelines/guidelines-reviewers.html.
Any questions/concerns please let @annefou know.

Review checklist for @christopheredsall (replaced by @ricardobarroslourenco)

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• #181
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.~~

Review checklist for @oscarbau

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment? See comment #9
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Review checklist for @RachelFurner

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Review checklist for @ricardobarroslourenco (replacing @christopheredsall)

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• #179
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• #180
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Additional instructions

Reviewer general comments are welcome on this REVIEW issue or directly to the notebook repository.

If you do the latter, you will find a Pull Request titled REVIEW where you can carry out the discussion with authors through ReviewNB, a third-party plugin in GitHub for displaying and commenting Jupyter Notebooks (see further details here).

In addition to ReviewNB, we suggest to explore or run the notebook in:

• Binder (run): Click the Launch Binder button at the top level of this message.

The current version declares the environmental setting within the notebook title p.e. Polar: . This needs to be replace by tags indicating the target setting and type of notebook e.g. visualisation, modelling, data preprocessing, etc.

Feature Request

The current template of notebook repository in the Environmental-DS-Book only supports conda python-based environments. This limits potential contributions with other environment settings or/and programming languages. It would be interesting that EnvDS book connects scalable open-source developments across programming languages. For instance, there are some efforts to translate python-based xarray to Julia, see YAXArrays.jl.

Describe the solution you'd like

A single and well-documented template supporting jupyter notebooks in python, r, Julia, among others commonly used by Environmental Data Scientists.

Describe alternatives you've considered

Implement repo2docker-action which works with multiple programming languages.

Additional information

What is the notebook about?

• COSMOS-UK, https://catalogue.ceh.ac.uk/documents/b5c190e4-e35d-40ea-8fbe-598da03a1185
• intake, hvplot, xarray

Data Science Component

• Sensor visualisation
• Preprocessing
• Modelling
• Post-processing
• Other:

Checklist:

• Input data, pipeline and/or model are public with license/citation
• The proposed notebook reuses existing codebase
• The proposed notebook uses open-source packages
• The proposed notebook is associated to existing publication(s)

Additional information

Describe the proposed improvement to the documentation

The tag for submission types includes a category named regular, this should be renamed to standard which would be better and less confusing (see @scotthosking comments in #139).

Additional information

Describe the proposed improvement to the documentation

The notebook repositories don't have a consistent folder/file structure.

The optimal folder and files structure is:
.binder (contain the environment.yml file)
.github (contain the workflow for automating notebooks)
.lock (contain lock files)
.gitignore
LICENSE
README.md
config.json
.ipynb

In addition, the README.md should contain further instructions how to run the notebook in Binder or locally. See for example general-preprocessing-rainfall_noaa.

Additional information

The suggested changes require access to the EnvDSbook organisation. In most of the notebooks, the lock files are inside .binder folder so they should be moved to the .locks folder.

Describe the proposed improvement to the documentation

Standarised notebook repository names. Most of published notebook repositories follow the naming convention, except the following:

• ocean-modelling-litter-philab > change to ocean-modelling-litter_philab
• polar-modelling-icenet > change to polar-modelling-icenet_bas
• agriculture-exploration-cosmosuk > change to agriculture-exploration-cosmosuk_ukceh

Additional information

Changes in the repository name will affect the main repository. We should report changes to notebook authors if they're using or citing them.
We can skip this change if it implies a major break in users accessing the aforementioned notebooks.

Feature Request

EDS book should be aligned to global initiatives promoting FAIR in the Earth Systems and Environmental Sciences to advance a common interest in open science.

Describe the solution you'd like

A community consultation to sign COPDESS Enabling FAIR Commitment Statement.

Describe alternatives you've considered

Look for other domain-agnostic initiatives promoting good scientific software practises and FAIR.

Additional information

Summary

Let's use this issue to add contributors information with @allcontributors.

What needs to be done?

Write a comment with the contribution information with the following nomenclature:
@all-contributors please add @<username> for <contributions>

We suggest typing up to 5 contribution types (see the available Emoji Key ✨ here).
Feel free to list those contribution types you find more relevant to the EDS book community.

Further info of the all-contributors bot here.

Who can help?

Anyone

Info
Abstract ID: 1072564
Abstract Title: Environmental Data Science Book: a community-driven resource showcasing open-source Environmental science
Final Paper Number: ED16B-03
Presentation Type: Oral
Session Date and Time: Monday, 12 December 2022; 16:45 - 18:15 CST
Session Number and Title: ED16B: Open Science Practices and Success Stories Across the Earth, Space, and Environmental Sciences IV

Deadline
Upload pre-recorded video, 10-min, 8th December

Slides

• Check AGU templates
• Add scriberia notebook communities and Reseach object illustrations
• Demo EGI binder (video), 3 min, start from renderend notebook in the EDS book, then click RoHub badge, then open EGI binder.

Repositories

• Add RoHub URL to Jupyter notebook [EGI binder]
• Associate conda environment to all notebooks

Notebook Review: Issue #168

Submitting author: @annefou

Repository: https://github.com/eds-book-gallery/teamX-toy-repo

Notebook idea issue: N/A

Editor: @acocac

Reviewer: @acocac

Managing EiC: @acocac

Status

Reviewer instructions & questions

Hi 👋 @acocac, please carry out your review in this issue by updating the checklist below.

As a reviewer, you contribute to the technical quality of the content published by our community.

Before the review, EiC checked if the submission fits the minimum requirements.

The quality of the proposed contribution can be assessed through scientific, technical and code criteria.

The reviewer guidelines are available here: https://edsbook.org/publishing/guidelines/guidelines-reviewers.html.
Any questions/concerns please let @acocac know.

Review checklist for @acocac

Please check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide.

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (If you are unsure whether you are in conflict, please speak to your editor before starting your review).

Code of conduct an peer-review principles

• I confirm that I read and will adhere to the Environmental Data Science code of conduct.
• I confirm that I read and will adhere to Open Science Peer Review Oath

General checks

• Notebook: Is the notebook file (notebook.ipynb) part of the notebook repository?
• Contribution and authorship: Does the author list seem appropriate and complete (full name, affiliation, and GitHub/ORCID handle)?
• Scope and eligibility: Does the submission contain an original and complete analysis according to the scope of EDS book?

Reproducibility

• Does the notebook run in a local environment?
• Does the notebook build and run in binder?
• Are all data sources openly accessible and properly cited (e.g. with citation to a persistent DOI) in the heading section?

Pedagogy

• Are the notebook purpose and highlights clear?
• Does the notebook demonstrate some specific data analysis or visualisation techniques?
• Is the notebook well documented, using both markdown cells and comments in code cells?
• Does the conclusion section provide clear and concise final say on the tools, analysis and/or datasets used?
• Is the notebook narrative well written (it does not require editing for structure, language, or writing quality)?

Ethical

• Is any linkage of datasets in the notebook unlikely to lead to an increased risk of the personal identification of individuals?
• Is the notebook truthful and clear about any limitations of the analysis (and potential biases in data and/or tools)?
• Is the notebook unlikely to lead to negative social outcomes, such as (but not limited to) increasing discrimination or injustice?

Other Requirements

• All mentioned software should be formally and consistently cited wherever possible.
• Acronyms should be spelled out upon first mention.
• License conditions on images and figures must be respected (Creative Commons, etc.).

Final approval (post-review)

• Authors has responded to my review and made changes to my satisfaction. I recommend approving the notebook for publication.

Additional instructions

Reviewer general comments are welcome on this REVIEW issue or directly to the notebook repository.

If you do the latter, you will find a Pull Request titled REVIEW where you can carry out the discussion with authors through ReviewNB, a third-party plugin in GitHub for displaying and commenting Jupyter Notebooks (see further details here).

In addition to ReviewNB, we suggest to explore or run the notebook in:

• Binder (run): Click the Launch Binder button at the top level of this message.

Describe the proposed improvement to the documentation

Update the How to use this book section in preamble which contains old instructions using the version 0.0.2.

Additional information

The instructions should indicate how to run individual notebooks hosted in the Environmental Data Science book organisation.

Describe the proposed improvement to the documentation

Hi folks!

Additional to my WIP #117 aimed at improving guidelines and documentation of the EDS book, I’m excited to share recent developments in our branding 🎨 . I would like to propose a new intentionally designed logo for the EDS book.

The current logo (please see it below) only reflects the digitalisation of the planet earth, in this case represented by three consecutive icons: the natural earth (left), binary code referring to the means i.e. data, code, software, etc (mid) and digital earth (right).

The updated logo builds upon the original one, but highlighting new components:

• People network icons at the start and end of EDS initials indicating an end-to-end community-driven goal i.e. improving scientific software and data management practises through the publication of FAIR peer-reviewed computational notebooks.
• Rope knots (proposal 1) or plugs (proposal 2) connecting all capital letters referring to a healthy and strong collaboration.
• Lettermark-oriented. The original logo missed the name. The proposed versions comprise the initials to make it easy to remember and recognise.

Here's a comparison of two variants of the proposed logo (feel free to vote 🐶 or 🐱):

Rope knot (:dog:)	Plugs (:cat:)

Who can help?

Thoughts from the EDS book community and friends are welcome. I'm completely open to playing around with:

• the final colours (is a B&W version ok?)
• whether or not to have a "binary code" icon.
• whether or not to have a "rope knots” or “plugs”
• whether or not to have a “people network icons”

Feel free to tag anyone who might be interested. I’m aiming to release the new logo with the updated documentation in March.

I also attach PDF versions of both logo variants which include some variations for stickers or social networks.

Additional information

I initially designed the proposed logo in MS Powerpoint using the default gallery of icons which are free to use with no copyright.

Thanks to @aleesteele, I recently learnt about penpot, a great open-source design prototyping tool. If you’re familiar with the tool or want to try your graphic designer skills, I can provide access to the EDS book penpot project group.