Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Project Proposal]: IOOS report env #28

Open
7yl4r opened this issue Dec 12, 2023 · 4 comments
Open

[Project Proposal]: IOOS report env #28

7yl4r opened this issue Dec 12, 2023 · 4 comments
Labels
code sprint topic Proposed topic for a code sprint activity wont fix 2024 Topic will not be executed during 2024 event

Comments

@7yl4r
Copy link
Contributor

7yl4r commented Dec 12, 2023

Project Description

Management of technical reporting environments (ie research devops) is the greatest barrier between researchers and the technical means to create maximally reproducible research publications.

The goal of this project is to establish standard "boilerplate" aka "cookie-cutter" templates that researchers can use as starting points for drafting reports leveraging FAIR data and FOSS software.

This project will combine extant technologies for research-notebook publication (quarto, jupyter) with technologies for environment management (docker, pyenv, renv).

Expected Outcomes

Minimal git repositories that can be easily cloned and used to create a web-browser-compatible report.

Skills required

git

Expertise

Intermediate

Topic Lead(s)

@7yl4r (Tylar Murray)

Relevant links

No response

@7yl4r 7yl4r added the code sprint topic Proposed topic for a code sprint activity label Dec 12, 2023
@7yl4r 7yl4r changed the title [Project Proposal]: IOOS dev env [Project Proposal]: IOOS report env Dec 12, 2023
@MathewBiddle MathewBiddle added the 2024 Topic to be executed during 2024 event label Jan 4, 2024
@Harish-2003
Copy link

I am interested,may i know how can I able to get familiar with this project

@MathewBiddle MathewBiddle assigned 7yl4r and unassigned mwengren and MathewBiddle May 3, 2024
@MathewBiddle
Copy link
Contributor

MathewBiddle commented May 3, 2024

Thank you for taking the time to propose this topic! From the Code Sprint topic survey, this has garnered a lot of interest.

Following the contributing guidelines on selecting a code sprint topic I have assigned this topic to @7yl4r. Unless indicated otherwise, the assignee will be responsible for identifying a plan for the code sprint topic, establishing a team, and taking the lead on executing said plan. The first action for the lead is to:

@MathewBiddle
Copy link
Contributor

standby on this topic.

@MathewBiddle MathewBiddle added the wont fix 2024 Topic will not be executed during 2024 event label May 14, 2024
@MathewBiddle
Copy link
Contributor

This topic will not be executed during 2024 event.

@MathewBiddle MathewBiddle removed the 2024 Topic to be executed during 2024 event label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code sprint topic Proposed topic for a code sprint activity wont fix 2024 Topic will not be executed during 2024 event
Projects
None yet
Development

No branches or pull requests

4 participants