|
1 | | -# ProLUG Automation Engineering Course |
| 1 | +# ProLUG Automation Engineering Course Book |
| 2 | + |
| 3 | +## Goals |
| 4 | + |
| 5 | +The overarching goal of this project is to provide a free, open source Systems Automation course |
| 6 | +predicated on the work produced by Scott Champine, an experienced and skilled Senior Systems Engineer. |
| 7 | + |
| 8 | +Scott has over 20+ years administering and engineering Linux systems across a broad variety of |
| 9 | +fields and teams. He has built and maintains systems like High Performance Compute (HPC) clusters |
| 10 | +for [NOAA (The National Oceanic and Atmospheric Administration)](https://www.noaa.gov/) and more. |
| 11 | + |
| 12 | +ProLUG looks forward to working with contributors who want to give back to the community and produce |
| 13 | +skilled Systems Administrators and Systems enthusiasts. |
| 14 | + |
| 15 | +## Objectives |
| 16 | + |
| 17 | +Contributors will be tasked with developing templated course material provided by Scott Champine. |
| 18 | +Outlined below are a set of objectives this repository attempts to provide. |
| 19 | + |
| 20 | +- Provide a centralized set of worksheets and labs for prospective learners to begin understanding Automation Engineering. |
| 21 | +- Deliver templated versions of course work per unit along with supplementary material and video. |
| 22 | +- Provide learners with foundational knowledge in computer systems to include: |
| 23 | + TBD |
| 24 | + |
| 25 | +## To Begin Contributing |
| 26 | + |
| 27 | +ProLUG asks all contributors to understand and adhere to the principles and guidelines detailed |
| 28 | +in the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/src/contributing.md) markdown file. |
| 29 | +Contributors found significantly deviating from these policies will have their work discarded appropriately. |
| 30 | + |
| 31 | +Contributors will be provided with supplementary material to begin building out unit worksheet labs |
| 32 | +and templates within the project managed issues board. |
| 33 | + |
| 34 | +To start contributing: |
| 35 | + |
| 36 | +- Understand the repository objectives |
| 37 | +- Read the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/src/contributing.md) markdown |
| 38 | +- Look over the template pages here: |
| 39 | + - Pages: [intro](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/ref/intro.md), |
| 40 | + [bonus](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/ref/ub.md), |
| 41 | + [lab](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/ref/ulab.md), |
| 42 | + [worksheet](https://github.com/ProfessionalLinuxUsersGroup/pcae/blob/main/ref/uws.md) |
| 43 | +- Request to be assigned a task within the repo [Issues](https://github.com/ProfessionalLinuxUsersGroup/pcae/issues) tab |
| 44 | +- Fork this repository and create a development branch for eventual pull requests |
| 45 | +- Strictly adhere to contemporary GitHub contribution decorum to facilitate the version control process |
0 commit comments