training-docker

Software carpentry lesson about Docker

https://github.com/ome/training-docker

Science Score: 54.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    9 of 48 committers (18.8%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.8%) to scientific vocabulary

Keywords

docker software-carpentry training

Keywords from Contributors

ansible english lesson prediction pre-alpha auroc bootstrapping carpentries-incubator data-leakage ecology
Last synced: 6 months ago · JSON representation ·

Repository

Software carpentry lesson about Docker

Basic Info
Statistics
  • Stars: 4
  • Watchers: 7
  • Forks: 4
  • Open Issues: 0
  • Releases: 0
Topics
docker software-carpentry training
Created over 7 years ago · Last pushed 8 months ago
Metadata Files
Readme Contributing License Citation Authors

README.md

lesson-example

This repository shows how to create a lesson using the Software Carpentry lesson template, and is itself an example of the use of that template. Please see https://swcarpentry.github.io/lesson-example/ for a rendered version of this material, including detailed instructions on design, setup, and formatting.

Quick Instructions

  1. Do not fork this repository directly on GitHub. Instead, please follow the instructions in the setup instructions to create a repository for your lesson by importing material from the styles repository.

  2. Once you have created your repository, run bin/lesson_initialize.py to create standard lesson-specific files. You must edit several values in _config.yml so that GitHub Pages will render your lesson correctly.

  3. Please read the episodes of this lesson to format your material.

  4. Please keep the master copy of your lesson in your repository's master branch, since that is what is automatically published as a website by GitHub.

  5. To preview material, please run make serve from the command line to launch Jekyll with the correct parameters, or push to your repository's master branch and let GitHub take care of the rendering.

  6. Run make lesson-check to check that your files follow our formatting rules.

  7. If you find an error or omission in this documentation, please file an issue in this repository. If you find an error or omission in the lesson template, please file an issue in the styles repository instead.

Layout

The layout of this repository is explained in this site's episodes. In brief:

  1. The source for pages that appear as top-level items in the navigation bar are stored in the root directory, including the home page (index.md), the reference page (reference.md), and the setup instructions (setup.md).

  2. Source files for lesson episodes are stored in _episodes; _episodes/01-xyz.md generates /01-xyz/index.html, which can be linked to using /01-xyz/.

  3. If you are writing lessons in R Markdown, source files go in _episodes_rmd. You must run make lesson-rmd to turn these into Markdown in _episodes and commit those Markdown files to the repository (since GitHub won't run anything except Jekyll to format material). You must also commit any figures generated from your lessons, which are stored in the fig directory.

  4. Files that appear under the "extras" menu are stored in _extras.

  5. Figures are stored in the fig directory, data sets in data, source code in code, and miscellaneous files in files.

Getting Started

  1. Run bin/lesson_initialize.py to create files that can't be stored in the template repository (because they would cause repeated merge conflicts), then edit _config.yml as described in the documentation.

  2. Run make lesson-check at any time to check that your lesson files follow our formatting rules. If you come across formatting issues that the checker doesn't report, please file an issue in the styles repository.

  3. For a list of helpful commands run make in this directory. If you are looking for things to work on, please see the list of issues for this repository.

Owner

  • Name: Open Microscopy Environment
  • Login: ome
  • Kind: organization
  • Email: ome-users@lists.openmicroscopy.org.uk

Software and data format standards for management of microscopy image data. Joint project between international private and public research

Citation (CITATION)

Please cite as:

Greg Wilson (ed.): "Software Carpentry: Lesson Example."  Version
2016.06, June 2016, https://github.com/swcarpentry/lesson-example,
10.5281/zenodo.58153.

GitHub Events

Total
  • Issues event: 1
  • Issue comment event: 1
  • Push event: 9
  • Pull request event: 3
  • Fork event: 1
Last Year
  • Issues event: 1
  • Issue comment event: 1
  • Push event: 9
  • Pull request event: 3
  • Fork event: 1

Committers

Last synced: 8 months ago

All Time
  • Total Commits: 839
  • Total Committers: 48
  • Avg Commits per committer: 17.479
  • Development Distribution Score (DDS): 0.477
Past Year
  • Commits: 35
  • Committers: 2
  • Avg Commits per committer: 17.5
  • Development Distribution Score (DDS): 0.057
Top Committers
Name Email Commits
Greg Wilson g****n@s****g 439
Raniere Silva r****e@r****m 120
François Michonneau f****u@g****m 37
Jean-Marie Burel j****l@d****k 33
Andy Boughton a****t@g****m 31
Abigail Cabunoc Mayes a****c@g****m 25
Rémi Emonet r****i@h****m 21
W. Trevor King w****g@t****s 20
Simon Li s****i@d****k 19
Aaron O'Leary a****y@g****m 14
James Allen j****s@s****m 5
John Blischak j****k@g****m 5
Jonah Duckles j****h@d****g 5
Piotr Banaszkiewicz p****r@b****g 5
Kate Hertweck k****k@g****m 4
Kenny Gillen k****n@d****k 4
Naupaka Zimmerman n****a@g****m 4
Ivan Gonzalez i****c@g****m 3
Pete Bachant p****t@g****m 3
Trevor Bekolay t****y@g****m 3
Timothée Poisot t****t@g****m 2
Amy Brown a****a@g****m 2
Bill Mills m****j@g****m 2
C. Titus Brown t****s@i****g 2
Donny Winston d****n@a****u 2
Evan P. Williamson e****w@g****m 2
Jon Pipitone j****e@u****a 2
Maxim Belkin m****n@g****m 2
Thomas Guignard t****m@t****h 2
pwalczysko p****o@d****k 2
and 18 more...

Issues and Pull Requests

Last synced: 8 months ago

All Time
  • Total issues: 2
  • Total pull requests: 3
  • Average time to close issues: 7 minutes
  • Average time to close pull requests: 19 minutes
  • Total issue authors: 2
  • Total pull request authors: 1
  • Average comments per issue: 1.0
  • Average comments per pull request: 0.33
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 1
  • Pull requests: 3
  • Average time to close issues: 13 minutes
  • Average time to close pull requests: 19 minutes
  • Issue authors: 1
  • Pull request authors: 1
  • Average comments per issue: 1.0
  • Average comments per pull request: 0.33
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • pwalczysko (1)
  • amandamiotto (1)
Pull Request Authors
  • pwalczysko (5)
Top Labels
Issue Labels
Pull Request Labels