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

2016-2017 Lesson Overhaul #121

Merged
merged 3 commits into from
Sep 27, 2016
Merged

2016-2017 Lesson Overhaul #121

merged 3 commits into from
Sep 27, 2016

Conversation

pop
Copy link
Contributor

@pop pop commented Aug 23, 2016

NOTE: I know it's a big diff, a lot of the content previously in the repository will be added back in (images, etc).

Major Changes Include:

  • Organized all content to focus on lessons.
    • In the side-bar you can now see Lessons in order.
    • Clicking the 'next' button goes to the next lesson.
  • Re-writing all content.
    • Re-writing content with a focus on HTML pages over of slides.
  • De-constructed lessons to be smaller.
    • This is so we can pick, choose, and move lessons around more easily.

TODO:

  • index
    • Drafted
    • Edited
  • start-here
    • Drafted
    • Edited
    • HTML & Slides Look good
  • first-steps
    • Drafted
    • Edited
    • HTML & Slides Look good
  • operating-systems
    • Drafted
    • Edited
    • HTML & Slides Look good
  • shell-navigation-os
    • Drafted
    • Edited
    • HTML & Slides Look good
  • users-groups-permissions
    • Drafted
    • Edited
    • HTML & Slides Look good
  • files
    • Drafted
    • Edited
    • HTML & Slides Look good
  • packages-software-libraries
    • Drafted
    • Edited
    • HTML & Slides Look good
  • questions-answers-documentation
    • Drafted
    • Edited
    • HTML & Slides Look good
  • version-control
    • Drafted
    • Edited
    • HTML & Slides Look good
  • programming
    • Drafted
    • Edited
    • HTML & Slides Look good
  • frameworks
    • Drafted
    • Edited
    • HTML & Slides Look good
  • testing
    • Drafted
    • Edited
    • HTML & Slides Look good
  • continuous-integration
    • Drafted
    • Edited
    • HTML & Slides Look good
  • security
    • Drafted
    • Edited
    • HTML & Slides Look good
  • databases
    • Drafted
    • Edited
    • HTML & Slides Look good
  • development-processes-tools
    • Drafted
    • Edited
    • HTML & Slides Look good
  • dns
    • Drafted
    • Edited
    • HTML & Slides Look good
  • configuration-management
    • Drafted
    • Edited
    • HTML & Slides Look good
  • application-isolation
    • Drafted
    • Edited
    • HTML & Slides Look good
  • cloud-infrastructure
    • Drafted
    • Edited
    • HTML & Slides Look good
  • contributing-to-open-source
    • Drafted
    • Edited
    • HTML & Slides Look good
  • about
    • Drafted
    • Edited
  • schedule
    • Drafted
    • Edited

Contributing:

I have a few notes for people that want to help contribute:

RST Formatting:

This is the top Heading  (h1)
=======================

This is one topic  (h2)
-----------------

This is a subtopic  (h3)
~~~~~~~~~~~~~~~~~~

This is another topic  (h2)
---------------------

etc  (h3)
~~~
  • Leave two newlines above any heading (lesson, topic, subtopic, sub-sub-topic).
  • Use the .. ifnotslides:: directive to include paragraphs for the HTML pages but not the slides.
  • Lines have an 80 character limit.

Adding Content

If you want to fill out the lessons do the following:

  • Call dibs in this pull request.
  • Reference the old content when filling in the new content. DO NOT COPY-PASTE CONTENT
  • Feel free to expand on topics/subtopics where you feel it appropriate.

Follow git-flow. Before making changes git pull and new change and avoid conflicts. If we start stepping on eachother's toes too much we'll start making proper pull-requests to this branch.

Of course, feel free to edit where it is needed.

refs #120

@pop pop self-assigned this Aug 23, 2016
@pop
Copy link
Contributor Author

pop commented Aug 24, 2016

I am going to do the drafts for:

  • shell-navigation-os
  • users-groups-permissions
  • files

I am also adding an 'overview' section to each lesson.

@pop pop changed the title 2016-2017 inital overhaul 2016-2017 Lesson Overhaul Aug 25, 2016
@pop
Copy link
Contributor Author

pop commented Aug 25, 2016

Now I'm calling dibs on:

  • packages-software-libraries
  • questions-answers-documentation
  • version control

@pop pop force-pushed the overhaul-2016 branch 2 times, most recently from 2fed1bf to 43407a9 Compare August 29, 2016 20:01
@pop
Copy link
Contributor Author

pop commented Aug 29, 2016

I'm calling dibs on

  • Programming
  • Frameworks
  • Testing
  • CI

@pop
Copy link
Contributor Author

pop commented Aug 30, 2016

Calling dibs on

  • Security
  • Databases
  • Development Tools
  • DNS

@@ -41,7 +41,7 @@

# General information about the project.
project = u'OSU DevOps BootCamp'
copyright = u'2013, OSU OSL & OSU LUG'
copyright = u'2013-2016, OSU Open Soruce Lab & OSU Linux Users Group'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Soruce

@pop
Copy link
Contributor Author

pop commented Sep 7, 2016

Calling dibs on

  • configuration-management
  • application-isolation
  • cloud-infrastructure
  • contributing-to-open-source

Major Changes Include:

- Organized all content to focus on lessons.
  - In the side-bar you can now see Lessons in order.
  - Clicking the 'next' button goes to the next lesson.
- Re-writing all content.
  - Re-writing content with a focus on HTML pages over of slides.
- De-constructed lessons to be smaller.
  - This is so we can pick, choose, and move lessons around more easily.
- Lessons are lightly-edited.
  - Most lessons need a bit more polish / have room for improvement.
- Removed unecessary images.
- Added 'Running DOBC' doc with advice and guidelines for running a DOBC.

refs #120
They didn't trigger a build failure. Might want to fix that later.
Copy link

@fahlmant fahlmant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not done yet, but here is the first part of my review

engineering and many modern security roles require a background with a balance
between development and operations.
**DevOps** is a hybrid of skills from both Software Development (Dev) and
Computer Operations (ops) intended to meet the unique demands of `cloud

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capital Ops?

**DevOps** is a hybrid of skills from both Software Development (Dev) and
Computer Operations (ops) intended to meet the unique demands of `cloud
computing`_. *Software Developer* and *Systems Administrator* are no longer
mutually exclusive job titles. Devs need more ops knowledge to understand how

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here if you make the change to Ops


"The Deal"
~~~~~~~~~~
DevOps BootCamp is an OSU Open Source Lab program dedicated to teaching core

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a link to osuosl.org

with its new status as part of the school of EECS
* The open source community gets more contributors to its projects
interested in recruiting students.
* The OSL gets to work with a wider variety of students, benefiting its status

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Benefiting sounds a bit awkward here

Copy link
Contributor

@ramereth ramereth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builds, looks OK. Too big of a diff to check everything but LGTM.

@aaroncohen73
Copy link
Member

A bit of feedback for Lesson 13: Security:

When you suggest that people consider using pass phrases instead of passwords, you should probably also mention some of the pitfalls of pass phrases that might make them as vulnerable as passwords. For example, pass phrases should be made of random words, and not popular quotes, actor names, etc. It's not infeasible that a dictionary attack could target common phrases such as these.

@pop pop merged commit 110f89d into master Sep 27, 2016
@ramereth ramereth deleted the overhaul-2016 branch October 30, 2017 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants