All Projects → OpenScienceRoadmap → mozilla-sprint-2018

OpenScienceRoadmap / mozilla-sprint-2018

Licence: other
DEPRECATED & Materials Moved: This sprint was to focus on brainstorming for the Joint Roadmap for Open Science Tools.

Programming Languages

python
139335 projects - #7 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to mozilla-sprint-2018

awesome-utrecht-university
A curated list of awesome open source projects from Utrecht University.
Stars: ✭ 31 (+29.17%)
Mutual labels:  research, open-science
Repairnator
Software development bot that automatically repairs build failures on continuous integration. Join the bot revolution! 🌟🤖🌟💞
Stars: ✭ 340 (+1316.67%)
Mutual labels:  research, open-science
linkedresearch.org
🌐 linkedresearch.org
Stars: ✭ 32 (+33.33%)
Mutual labels:  research, open-science
Open-Data-Lab
an initiative to provide infrastructure for reproducible workflows around open data
Stars: ✭ 26 (+8.33%)
Mutual labels:  open-science, workflows
partinfra-terraform
Terraform configuration for Participation Infrastructure
Stars: ✭ 46 (+91.67%)
Mutual labels:  infrastructure, mozilla
Electrophysiologydata
A list of openly available datasets in (mostly human) electrophysiology.
Stars: ✭ 143 (+495.83%)
Mutual labels:  research, open-science
ck-mlops
A collection of portable workflows, automation recipes and components for MLOps in a unified CK format. Note that this repository is outdated - please check the 2nd generation of the CK workflow automation meta-framework with portable MLOps and DevOps components here:
Stars: ✭ 15 (-37.5%)
Mutual labels:  open-science, workflows
datascience
Keeping track of activities around research data
Stars: ✭ 29 (+20.83%)
Mutual labels:  research, open-science
Catalyst
Accelerated deep learning R&D
Stars: ✭ 2,804 (+11583.33%)
Mutual labels:  infrastructure, research
Mlcomp
Distributed DAG (Directed acyclic graph) framework for machine learning with UI
Stars: ✭ 183 (+662.5%)
Mutual labels:  infrastructure, research
alchemy
Experiments logging & visualization
Stars: ✭ 49 (+104.17%)
Mutual labels:  infrastructure, research
events
Materials related to events I might attend, and to talks I am giving
Stars: ✭ 22 (-8.33%)
Mutual labels:  research, open-science
ElectricPy
Electrical Engineering Python Module
Stars: ✭ 35 (+45.83%)
Mutual labels:  research
infrastructure
This repo contains all information about machine maintenance.
Stars: ✭ 75 (+212.5%)
Mutual labels:  infrastructure
plumbing
This repo holds configuration for infrastructure used across the tektoncd org 🏗️
Stars: ✭ 41 (+70.83%)
Mutual labels:  infrastructure
AutomaticMixingPapers
Important papers and associated code on automatic mixing research
Stars: ✭ 75 (+212.5%)
Mutual labels:  research
parler-py-api
UNOFFICIAL Python API to interface with Parler.com
Stars: ✭ 52 (+116.67%)
Mutual labels:  research
mlst check
Multilocus sequence typing by blast using the schemes from PubMLST
Stars: ✭ 22 (-8.33%)
Mutual labels:  research
terraform-pb
Programmatic management of infrastructure using Terraform and Protocol Buffers
Stars: ✭ 18 (-25%)
Mutual labels:  infrastructure
infraform
Creating infrastructure and running applications using different platforms
Stars: ✭ 31 (+29.17%)
Mutual labels:  infrastructure

Notice

This document outlined how to contribute to the Joint Roadmap during the May 2018 Mozilla Global Sprint, which is now over and materials generated during the sprint have moved.

Learn more about making ongoing contributions to the Joint Roadmap and please continue any work on or reference to materials generated during the sprint in their new locations: roadmap or ecosystem.


Welcome

This repo is a contribution to the Mozilla Global Sprint 2018 and focused on brainstorming for the Joint Roadmap for Open Science Tools (JROST).

We aim to improve the open science landscape systemically by bringing together a range of open projects to explore how they can be improved collectively and integrated towards a more interoperable open science ecosystem. Participants include Wikidata, Mozilla, Zotero, Hypothesis, DAT, Jupyter, bioRxiv, ORCID, Crossref, OJS, Meta, OSF, PLOS and others (see full list).

Stonehenge, assembled from a variety of sources over an extended period of time Stonehenge is an example where pieces from different sources had been integrated in a way that harmonized (and still does) with the surrounding landscape. We aim at a similar integration across the open science landscape that is accessible to the public and mindful of the long term, albeit with a more flexible arrangement, and closer to contemporary research workflows.

Painting by Jasper Francis Cropsey (1876), photographed by Daderot (2011), with roadmap logo by Dan Whaley (2018). Public Domain (via Wikimedia Commons).

Coordination

Channels

We will have a Zoom channel and the #opensciroadmap channel on IRC available throughout the sprint. We will also be monitoring the @OpenSciRoadmap handle and the #OpenSciRoadmap hashtag on Twitter, along with related handles and hashtags.

Stand-up Meetings

In addition to ongoing communication, participants will gather for short stand-up meetings three times per day live in the Zoom channel during the sprint on Thu 10 and Fri 11 May 2018. Join us there, or on Twitter or IRC to ask and answer questions, talk through ideas, and report on work:

  • 9-9:30am EDT (UTC -4)
  • 12-12:30pm EDT (UTC -4)
  • 16-16:30am EDT (UTC -4)

Activities

We expect the bulk of the activities during the sprint to result in modifications to this GitHub repo and its issue tracker, to the repo and issue tracker for the JROST website and (with pointers from our respective issues) to issue trackers and other fora used by projects that form part of the open science landscape, particularly those that participate in the current Mozsprint or that participated in past ones.

Collaboration

Contributions are welcome from individuals and groups — physically co-located or distributed, formally established or not — and we encourage participants to use the above channels to coordinate if, when and how they are working on particular tasks.

Getting started

We are using labels to tag the issues in this repo:

  • Welcome: A place where we can share a few words about ourselves and our background or expectations regarding the project.
  • Good first issue: these issues provide ways to familiarize yourself with this project, its contributors and the ecosystem around it
  • most of the issues have been tagged with the mozsprint label that we are using for tickets specific to the sprint
  • most of the issues have also been tagged with help wanted because that is how Mozsprint projects are expected to highlight issues where help from project-external contributors is particularly welcome.
    • for issues not tagged this way, help is still welcome, but the tag helps prioritize a bit
  • most issues have some additional labels:
    • Review: for issues focused on reviewing what is already there, so as to avoid accidental re-inventions of the wheel, and facilitate intentional collaboration
    • Curate: when existing information needs to be indexed, updated, highlighted, restructured, converted or otherwise curated
    • Create: when something needs to be created, be it code, documentation, communication, visualization or whatever seems necessary or fruitful
    • question: if anything needs discussion or other forms of input from others
  • some issues might be about other things, e.g.
    • logo: for activities related to design a JROST logo
    • events: for upcoming activites after this sprint

FAQ

For questions that need attention prior to or during the sprint, please use any of the above channels.

If the sprint activities lead to questions or insights that may be of interest to the broader open science community and beyond this sprint, they should probably go to Ask Open Science, as per issue 6.

Timing

The default for participating in Mozsprint activities is 9am-5pm in your time zone. We encourage you to follow that for our project as well, and we will try to be available across multiple time zones to facilitate remote interactions. Our core time zone for the sprint will be US Eastern Daylight Saving Time (UTC-4).

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].