# eLife Innovation Sprint - 2021

## Registration form: https://crm.elifesciences.org/crm/node/115

### Previous year doc: https://docs.google.com/document/d/1p7nAh_5c1KxhUDXu2bn4SjdWBvqiqTcTCvubG3AKDBA/edit#heading=h.yflbr0lwcpy3

# Team
- Pritish Samal - [e-mail]
- Isaac Miti - [e-mail]
- Name Here

# Project Details

1. The Problem *
In no more than 200 words, please tell us about the problem you plan to address through your work at the Sprint: how does it relate to the Sprint’s themes, who is this issue affecting, and why is it an important issue to solve at the moment?

When code is written for research and science purposes, it should be open source so that others can benefit from it. We’d like to help researchers find journals that require open source code easily. Science requires peer review. One of the basic prerequisites for any published scientific results is that it should be reviewed by peers, to ensure the research and conclusions are valid.

2. The Solution *
In no more than 200 words, tell us more about your idea for a technology-focussed solution to the problem you described above. Please feel free to include any relevant links (GitHub, Twitter, etc), but please prioritise them so reviewers can focus on the important ones within their time limit.

Whilst it is generally agreed that scientific research needs to be peer-reviewed as part of the publication, this stipulation doesn’t always extend to the peer-reviewing code. We aim to build infrastructure that clearly lists not only journal policies with regards to code artifacts, but also compliance with journal policy.
GitHub: https://github.com/codeisscience
Website: https://codeisscience.com/
Twitter: https://twitter.com/codeisscience

3. Proposed work at the Sprint *
In no more than 200 words, describe the work that you plan to carry out at the Sprint: what do you envision achieving within the two days of the event, and how can the Sprint help drive it forward? If you can write down a couple of deliverables/milestones you would like to complete.

Non-coders: Research journals and add them to our list, improving on the UI/UX, Testing our prototypes.
Coders: Writing unit and integration tests for the frontend using Jest or React Testing Library, integrating Auth0 to authenticate users, containerizing the web application, add CI/CD pipeline, deploy it on Digital Ocean or AWS.

4. The Contributors *
In no more than 100 words, please tell us what skills are you looking for from contributors at the Sprint, e.g. software development, UX, cloud infrastructure, design, communication, users with the domain expertise to test with. (Find out more about the expected participants and roles at the Sprint).

Non-coding skills: familiarity with academia, research journals.
Coding skills list: React, React Testing, Javascript Testing, DevOps, Docker, Kubernetes, UI/UX, Flask, Cloud Infrastructure, GitHub Actions, Git & GitHub, Communication

5. Facilitating participation and contribution *
In no more than 200 words, please explain your plans to facilitate contributions from Sprint participants: How do you plan to engage with and incorporate the voices of Sprint participants with diverse backgrounds, experiences and skill sets? What should contributors get from working on the project?

We will haveg frequent Zoom and text-based check-ins, share what hours we're available, what people can do when someone isn't around, how we might facilitate non-technical contributions, and what skills people might get from participating. We can help newbies to tech/code make initial commits on GitHub or techies will learn more about academic credit systems.