Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE: ContentMine Training Resources
GITHUB REPOSITORY/CODE: https://github.com/ContentMine/workshop-resources
DESCRIPTION: This repository contains material helping to set up a ContentMine workshop. It also includes tutorials for learning the ContentMine tools on ones own.

LINKS

• README.md: https://github.com/ContentMine/workshop-resources
• Roadmap:
• CONTRIBUTING.md: https://github.com/ContentMine/workshop-resources/blob/master/CONTRIBUTING.md
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Code of Conduct:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides
  @arlissc can you review & discuss with me?

Spoke with Cassie about this. Here's the issue in the Mofo /plan repo
Next steps:

• follow up with Cassie
• provide content as needed
  ...

Please make an issue of your own, like this template (below), with all links that you have, before the end of the workshop.

Bolded items are for you to fill in vis-à-vis your project/study group.

PROJECT

TITLE: Working Open Workshop
PROJECT REPO: https://github.com/mozillascience/working-open-workshop
DESCRIPTION: A repo to collect all materials and resources related to Mozilla Science Lab's Working Open Workshop.

LINKS

• README.md:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/README.md
• Code of Conduct:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/CODE_OF_CONDUCT.md
• Roadmap:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/roadmap.md
• CONTRIBUTING.md:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/CONTRIBUTING.md
• LICENSE:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/LICENSE.md
• humans.txt (if applicable):
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/humans.txt
• Data reuse plan:
  https://github.com/mozillascience/working-open-workshop/blob/gh-pages/handouts/data_reuse_plan_template.md
• Personas:

PROJECT

TITLE: SunPy
GITHUB REPOSITORY/CODE: https://github.com/sunpy/sunpy
DESCRIPTION: SunPy is an open-source Python library for solar physics data analysis.

LINKS

• README.md
• Code of Conduct:
• Roadmap:
• CONTRIBUTING.md
• LICENSE
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

PROJECT

TITLE:

WorldBrain - Verifying the Internet with Science

GITHUB REPOSITORY/CODE:

http://github.com/WorldBrain/

DESCRIPTION:

With WorldBrain, our goal is to build a browser plugin, which lets you check the trustworthiness of web articles and blog posts, based on how scientifically correct their statements are.
To provide the content for this, we develop a web-note taking app for the literate crowd we need: Skeptics, (science) bloggers and journalists. For more, visit our website.

LINKS

• README.md: https://github.com/WorldBrain/Webmarks/blob/master/README.md
• Code of Conduct: https://github.com/WorldBrain/Webmarks/blob/master/CODE_OF_CONDUCT.md
• Roadmap: https://github.com/WorldBrain/Webmarks/blob/master/ROADMAP.md
• CONTRIBUTING.md: https://github.com/WorldBrain/Webmarks/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/WorldBrain/Webmarks/edit/master/LICENSE
• humans.txt (if applicable): https://github.com/WorldBrain/Webmarks/blob/master/ACKNOWLEDGEMENTS.md
• Data reuse plan:
  not yet needed.
• Personas:

Please fill out the links in this issue, like this template here, with all links that you have.

I added you both because you likely are working on the same project, feel free to author a separate issue if that is not the case.

PROJECT

TITLE: Everware
GITHUB REPOSITORY/CODE: https://github.com/everware/everware
DESCRIPTION: Everware is about re-useable science, it allows people
to jump right in to your research code.

It lets you launch Jupyter notebooks from a git repository
with a click of a button. Everware is implemented as an
add-on for JupyterHub. The main component is a custom
spawner based on docker. The aim of the project is to
encourage reuse of software between researchers.

LINKS

• README.md: https://github.com/everware/everware/blob/master/README.md
• Code of Conduct:
• Roadmap: everware/everware#39
• CONTRIBUTING.md: https://github.com/everware/everware/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/everware/everware/blob/master/LICENSE
• humans.txt (if applicable):
• Data reuse plan:
• Personas:
• Open web stretch or other exercise to keep fit: https://www.strava.com/activities/487849487

@Saallen and I are going to try to add a humans.txt file to the repo.

👍 😄

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT 1

TITLE: phageParser
GITHUB REPOSITORY/CODE: https://github.com/goyalsid/phageParser
DESCRIPTION: A project to created enhanced datasets from published bacterial, archaeal, and viral genomes using the CRISPR system to infer connections between organisms. (Mozilla Collaborate link)

LINKS

• README.md: https://github.com/goyalsid/phageParser/blob/master/README.md
• Code of Conduct:
• Roadmap: phageParser/phageParser#55
• CONTRIBUTING.md: phageParser/phageParser#57
• LICENSE: https://github.com/goyalsid/phageParser/blob/master/LICENSE
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

PROJECT 2

TITLE: University of Toronto Scientific Coders
GITHUB REPOSITORY/CODE: https://github.com/UofTCoders
DESCRIPTION: A group of (mostly) grad students at the University of Toronto who meet weekly to learn programming and discuss all things research.

LINKS

• README.md: https://github.com/UofTCoders/studyGroup/blob/gh-pages/README.md
• Code of Conduct: https://github.com/UofTCoders/studyGroup/blob/gh-pages/codeOfConduct.md
• Roadmap: N/A
• CONTRIBUTING.md: https://github.com/UofTCoders/studyGroup/wiki/Contributing-a-lesson
• LICENSE: https://github.com/UofTCoders/studyGroup/blob/gh-pages/LICENSE
• humans.txt: Kind of: https://github.com/UofTCoders/studyGroup/blob/gh-pages/_data/members.yml
• Data reuse plan: N/A
• Personas: TBA

Remix the Lean Canvas for use on open source projects

Create html handouts for:

• Roadmapping
• User Personas and Pathways
• README
• Contributor Guidelines
• GitHub for newbies
• Code of Conduct
• Sprints and Events
• Data Use and Reuse Plan
• more that I forgot..

owner: @zee-moz? (but pls assign as many as you like to me)

Steps to complete:

1. clone the repo & go on the gh-pages branch

   git clone [email protected]:mozillascience/working-open-workshop.git
   cd working-open-workshop
   git checkout gh-pages
   

   If you've already cloned the repo, use this to bring in new changes that may have occured:

   git fetch origin
   git merge origin/gh-pages
   

2. copy the template folder to a folder named with your lesson

   cp -r template/ YOUR_LESSON
   

3. Edit the YOUR_LESSON/index.html to include content for your lesson

   • Use your favourite text editor

4. commit & push your changes to gh-pages

   git add YOUR_LESSON/
   git commit -m "Adding html version of the YOUR_LESSON handout"
   git push origin gh-pages
   

Your beautiful handout will now appear at:
http://mozillascience.github.io/working-open-workshop/YOUR_LESSON

Live template is here:
http://mozillascience.github.io/working-open-workshop/template

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT

TITLE: STEMM Role Models app
GITHUB REPOSITORY/CODE: https://github.com/KirstieJane/STEMMRoleModels
DESCRIPTION: Code, funding application materials and development discussions for the STEMM Role Models app. The project seeks to ensure that conference organizers are best placed to inspire future generations by easily linking them to the most exciting and diverse speakers in their field.

LINKS

• README.md: https://github.com/KirstieJane/STEMMRoleModels/blob/master/README.md
• Code of Conduct: https://github.com/KirstieJane/STEMMRoleModels/blob/master/CODE_OF_CONDUCT.md
• Roadmap: KirstieJane/STEMMRoleModels#1
• [x ] CONTRIBUTING.md: https://github.com/KirstieJane/STEMMRoleModels/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/KirstieJane/STEMMRoleModels/blob/master/LICENSE.md
• humans.txt (if applicable): Not exactly, but we do have this static link created on 17th March 2016 and documentation on how to update it from the dynamic site
• Data reuse plan: No plans for data reuse
• Personas: Not exactly, but we have an issue to encourage contributors to outline who might be interested in the app

TITLE: Genomics Hacky Hour - Study Group

GITHUB REPOSITORY/CODE:

https://github.com/anelda/GenomicsHackyHour/

DESCRIPTION:

A meeting place for people interested in Genomics - initially focused on researchers and postgraduate students at the North-West University in South Africa, but possibly open to anyone who could participate virtually

LINKS

README.md: TBC

Code of Conduct: https://github.com/anelda/GenomicsHackyHour/blob/gh-pages/codeOfConduct.md

Roadmap: TBC

CONTRIBUTING.md: TBC

LICENSE: TBC

@acabunoc @arlissc @kaythaney @auremoser
@stephwright

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides

Your required text does not appear to be correct

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC003)

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE: CHROMA (Collaborative Hub for Reproducible Open Meta-Analysis)
GITHUB REPOSITORY/CODE: Work in progress
DESCRIPTION: A tool for building open interactive meta-analyses using Github, R, and Shiny

LINKS

• README.md: N/A
• Roadmap: N/A
• CONTRIBUTING.md: N/A
• LICENSE: N/A
• humans.txt (if applicable): N/A
• Data reuse plan: N/A
• Personas: N/A

Hey @flukeout! The compiled css doesn't have the arrow/triangle. The dev template using less has it!

Data reuse:

Dev template:

• make a rough wireframe
• figure out where this will live (github? gitbook? pdf? thimble?)
• design styles

Creative brief is here: https://docs.google.com/document/d/1EAYGXIcbawbLMWedDhKWH2-zPovxSMTx_YOkNpjDabI/edit#

Sample content is here: https://public.etherpad-mozilla.org/p/WOW-personas-pathways-handout

Here's some stuff to improve

• When scrolling to the bottom of the page, the Resources section doesn't necessarily get selected in the left-side nav because the "Glossary" is still the primary element.
  • I can address this by checking if you're at the bottom of the page when scrolling and selecting the last section.
• Sometimes when you click through items quickly in the left-side nav, the page scrolls to a different section than is ultimately indicated by the nav. Fix it.
• Print CSS
• Mobile CSS
• ...please add more.

I'll file these as issues when I start work on each one.

From Sara, as presented at #mozlando w/ EOY fundraising modifications (changed to grants)

Reaching for all of our open source dreams (arms up)
Reaching the grassroots (reach toes)
Come back up in the blowing of the winds of change (arms back and forth)
Reach out and shake the money tree in time for grant applications (arms forward, shake imaginary tree)
Lean left to avoid the NSA (hands on hips, lean left)
Lean right to avoid the NSA (hands on hips, lean right)
Go all around to avoid the NSA (hands on hips, lean all around)

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

The big research fox logo in the top left of pages like http://mozillascience.github.io/working-open-workshop/writing_readme/ could be a hyperlink to http://mozillascience.github.io/working-open-workshop/

It would make navigating around easier.

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT 1

TITLE: Open Cosmics
GITHUB REPOSITORY/CODE: https://github.com/OpenCosmics/opencosmics.github.io
DESCRIPTION: A meta-project for cosmic-ray projects · Cosmic-ray physics for everyone

LINKS

• README: https://github.com/OpenCosmics/opencosmics.github.io/blob/meta/README.md
• Code of Conduct:
• ROADMAP: https://github.com/OpenCosmics/opencosmics.github.io/blob/meta/ROADMAP.md
• CONTRIBUTING: https://github.com/OpenCosmics/opencosmics.github.io/blob/meta/CONTRIBUTING.md
• LICENSE: https://github.com/OpenCosmics/opencosmics.github.io/blob/meta/LICENSE.md
• humans.txt (if applicable):
• Data reuse plan: TBD once we have a data repository!
• Personas: –N.A.–

PROJECT 2

TITLE: huomata
GITHUB REPOSITORY/CODE: https://github.com/RaoOfPhysics/huomata
DESCRIPTION: An open-source cross-platform PDF reader with built-in hypothes.is annotations

LINKS

• README: https://github.com/RaoOfPhysics/huomata/blob/master/README.md
• Code of Conduct:
• ROADMAP:
• CONTRIBUTING:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan: This project is not generating any research data. :)
• Personas: –N.A.–

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

Now that we've basically settled on the format and styling of the handouts (Example - from #11) - let's figure out how to
make the content editable as markdown. The advantages of this are...

• Markup is easier to work with for non-technical contributors
• The underlying content will be readable and editable via the github interface

The General Idea
Our goal is to host each handout as a separate markdown file on Github but also to serve them as pretty, styled HTML & CSS documents via some service we come up with. This service will parse the markdown and generate the appropriate HTML - to help this along, we will probably have to include classnames in the markdown, ie. {.description}.

cc @acabunoc

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides
  @mbonsma helping!

Please fill out the links in this issue, like this template here, with all links that you have.

I added you both here @amelgh + @FatmaZG because I imagine you worked on these activities together and might want to collaborate :)

PROJECT:

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT

TITLE: Pending
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Code of Conduct:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT

TITLE: pmc-ref
GITHUB REPOSITORY/CODE: https://github.com/RobSullivan/pmc-ref
DESCRIPTION: Check an article's references for free access.

LINKS

• README.md: https://github.com/RobSullivan/pmc-ref/blob/master/README.md
• Code of Conduct: https://github.com/RobSullivan/pmc-ref/blob/master/CODE_OF_CONDUCT.md
• Roadmap: RobSullivan/pmc-ref#30
• CONTRIBUTING.md: https://github.com/RobSullivan/pmc-ref/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/RobSullivan/pmc-ref/blob/master/LICENSE.md
• humans.txt (if applicable): https://github.com/RobSullivan/pmc-ref/blob/master/humans.txt
• Data reuse plan:
• Personas: done.

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides

@joeyklee @zee-moz helping!

Our README is sadly missing the research fox! Add the research fox to our README!

Mentored by @acabunoc

README:
https://github.com/mozillascience/working-open-workshop/blob/gh-pages/README.md

Markdown for images:
![](IMAGE_LINK)

Link to research fox:
mozillascience.github.io/working-open-workshop/assets/images/science-fox.svg

This is kinda silly but the page at

http://mozillascience.github.io/working-open-workshop/

does not render correctly on Firefox.

Works fine in Epiphany.

PROJECT:

TITLE: githubr R package
GITHUB REPOSITORY: https://github.com/brian-bot/githubr
DESCRIPTION: Making it easy to talk to GitHub from R

LINKS

• README.md: https://github.com/brian-bot/githubr/blob/master/README.md
• CONTRIBUTING.md: https://github.com/brian-bot/githubr/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/brian-bot/githubr/blob/master/LICENSE.txt
• humans.txt (included at end of CONTRIBUTING): https://github.com/brian-bot/githubr/blob/master/CONTRIBUTING.md
• Roadmap: N/A
• Personas: N/A

Please fill out the links in this issue, like this template here, with all links that you have.

If your project links involves other participants, feel free to tag/assign them here.

PROJECT

TITLE: Repodoctor
GITHUB REPOSITORY/CODE: https://github.com/onyb/repodoctor
DESCRIPTION: Check your repository health, and make it more contributor friendly.

LINKS

• README.md: https://github.com/onyb/repodoctor/blob/master/README.md
• Code of Conduct:
• Roadmap:
• CONTRIBUTING.md: https://github.com/onyb/repodoctor/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/onyb/repodoctor/blob/master/LICENSE
• humans.txt (if applicable):
• Data reuse plan:
• Personas: https://github.com/onyb/repodoctor/blob/master/Extras/makingpersona.txt

Hi we need structure and edits to our guidelines.
Great issue for newcomers! 👍

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine

@auremoser let's talk ASAP about what specifically this will cover!

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides

• Review short talk guidelines
• Post a link to your outline here! For review and discussion. If you're just getting started, just link to wherever you're working.
• @zee-moz review & discuss
• Revise and Refine
• Create handout
• Draft Slides in Google Slides
• Present to @cbahlai OSRR class
• Revise based on feedback and for more general audience at WOW
• Review once more w/ @zee-moz

@cbahlai is helping

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT:

TITLE:
GITHUB REPOSITORY/CODE:
DESCRIPTION:

LINKS

• README.md:
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas:

Please fill out the links in this issue, like this template here, with all links that you have.

PROJECT

TITLE: CERN Mozilla Study Group
GITHUB REPOSITORY/CODE: https://github.com/CERNStudyGroup/cernstudygroup.github.io
DESCRIPTION: page for our newly created study group

LINKS

• README.md: https://github.com/CERNStudyGroup/cernstudygroup.github.io/blob/master/README.md - will be updated after the first meeting with more detail
• Code of Conduct: see above, so far only the Mozilla CoC there
• Roadmap:
• CONTRIBUTING.md:
• LICENSE:
• humans.txt (if applicable):
• Data reuse plan:
• Personas: https://drive.google.com/folderview?id=0B1zeuhvIN9yIa0hLcFJka3FYeDA&usp=sharing for my PhD and not the study group. Will be reviewed after this workshop

Please fill out the links in this issue, like this template here, with all links that you have.

If your project involves other participants, feel free to assign/add them here!

PROJECT

TITLE: Repo Doctor
GITHUB REPOSITORY/CODE: https://github.com/onyb/repodoctor
DESCRIPTION: Check your repository health, and find out if it is contributor friendly.

LINKS

• README.md: https://github.com/onyb/repodoctor/blob/master/README.md
• Code of Conduct:
• Roadmap:
• CONTRIBUTING.md: https://github.com/onyb/repodoctor/blob/master/CONTRIBUTING.md
• LICENSE: https://github.com/onyb/repodoctor/blob/master/LICENSE
• humans.txt (if applicable):
• Data reuse plan:
• Personas: https://github.com/onyb/repodoctor/blob/master/Extras/makingpersona.txt

OpenCosmics, Repodoctor

TITLE: OpenCosmics, Repodoctor
PROJECT REPO: https://github.com/onyb/repodoctor, https://github.com/harunurhan/open-cosmics-mean
DESCRIPTION: Repo for back and frond end applications of open cosmic ray data network, Repo of a tool that checks if your projects is contributor friendly and gives you suggestions to make it so.

LINKS

• README.md: https://github.com/harunurhan/open-cosmics-mean/blob/master/README.md
• Roadmap: https://github.com/harunurhan/open-cosmics-mean/blob/master/README.md#roadmap-and-long-term-todos
• CONTRIBUTING.md: https://github.com/harunurhan/open-cosmics-mean/blob/master/CONTRIBUTING.md
  • LICENSE: https://github.com/harunurhan/open-cosmics-mean/blob/master/LICENSE
  • Personas: https://github.com/onyb/repodoctor/blob/master/Extras/makingpersona.txt

We don't have human.txt yet and data to create reuse plans

Extras:
In addition I also changed one of my personal repos (tags, md files etc.), with the help of work shop:
(https://github.com/harunurhan/google-result-highlighter)
Also small but helpful PR to the project which I use and work on
ReactiveX/RxJava#3672

Styles for this can be based on the handouts template in #11

Design brief here:
https://docs.google.com/document/d/1EAYGXIcbawbLMWedDhKWH2-zPovxSMTx_YOkNpjDabI/edit#

openSNP

TITLE: openSNP
PROJECT REPO: https://github.com/gedankenstuecke/snpr
DESCRIPTION: The sources for openSNP.org

LINKS

• README.md: https://github.com/gedankenstuecke/snpr/blob/master/README.md
• Code of Conduct: https://github.com/gedankenstuecke/snpr/blob/master/CODE_OF_CONDUCT.md
• Roadmap: openSNP/snpr#261
• CONTRIBUTING.md: https://github.com/gedankenstuecke/snpr/blob/master/README.md#Contribute (will be moved)
• LICENSE: https://github.com/gedankenstuecke/snpr/blob/master/LICENSE.md
• humans.txt (if applicable): https://github.com/gedankenstuecke/snpr/issues/245
• Data Reuse Plan: yes, but ironically can't be shared yet
• Personas: https://gedankenstuecke.piratenpad.de/mozwow-personas