├── PowerShell_Team └── README.md ├── README.md └── octocat └── holiday-octocat.png /PowerShell_Team/README.md: -------------------------------------------------------------------------------- 1 | Team PowerShell Repo -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Commitmas 3: Return of Commitmas! 2 | Welcome back to another year of Commitmas! This year is all about keeping it small and team focused. 3 | 4 | ![Holiday octocat](octocat/holiday-octocat.png) 5 | 6 | 7 | #### Table of Contents 8 | 9 | 1. [Overview](#overview) 10 | 2. [vBrownBag Schedule](#vbrownbag-schedule) 11 | 3. [The Teams](#the-teams) 12 | 4. [The Standard Challenge](#the-standard-challenge) 13 | 5. [Commit to Your Skill Level](#commit-to-your-skill-level) 14 | * [Beginner](#beginner) 15 | * [Intermediate](#intermediate) 16 | * [Expert](#expert) 17 | 6. [Resources](#resources) 18 | 19 | ## Overview 20 | 21 | We have organized 5 groups, each with a "lead" to coordinate the efforts of contributing to the project or repository. There are different projects based upon different technologies, whether you are an experienced practitioner of PowerShell, or want to learn Ansible, there is a project for you to join! 22 | 23 | This year we are focused on working together, whether you are contributing to an Open Source project or scripts at work. Working collaboratively together requires communication, coordination, and of course some practice with forking, branching, merging, and pull requests! 24 | 25 | ## vBrownBag Schedule 26 | 27 | - **Wednesday 11/30** - Git'ing Ops in shape for DevOps with [Taylor Riggan](https://twitter.com/triggan) 28 | - **Monday 12/5** - Lessons learned from writing the DevOps Handbook with [Gene Kim](https://twitter.com/realgenekim) 29 | - **Wednesday 12/7** - Forking public work, committing to it, and managing the PR process with [Safia Abdalla](https://twitter.com/captainsafia) 30 | - **Wednesday 12/14** - Curating a group of people that build tools together with [Matthew Brender](https://twitter.com/mjbrender) 31 | - **Tuesday 12/20** - Gitting out of a mess [Katie Sylor-Miller](https://twitter.com/ksylor) 32 | - **Wednesday 12/21** - DevOps Discussion with [John Hildebrand](https://twitter.com/snoopj123) 33 | - **Thursday 12/22** - Writing a good README.md for your Git repo [Mike Marseglia](https://twitter.com/mmars) 34 | 35 | Registration for the Commitmas online webinars may be completed through the [US #vBrownBag](https://attendee.gotowebinar.com/register/4381236442732324866) page. 36 | 37 | ## The Teams 38 | 39 | Follow these steps to play along with one of the team leads! 40 | 41 | ## Team Ansible with [Larry Smith](https://twitter.com/mrlesmithjr) 42 | 43 | * [30 Days of Ansible Roles](https://github.com/mrlesmithjr/commitmas-ansible) 44 | 45 | ## Team Chef with [Jesse Anderson](https://twitter.com/sockeyes51) 46 | 47 | * [Deploying LAMP Stack to Docker Containers with Chef](https://github.com/jessecanderson/commitmas-2016-chef-project) 48 | 49 | ## Team PowerShell with [Kyle Ruddy](https://twitter.com/kmruddy) 50 | 51 | * Fork the [PowerShell_Team repo](https://github.com/commitmas/return-of-commitmas/tree/master/PowerShell_Team) and make contributions 52 | * Fork the [PowerCLI Community repo](https://github.com/vmware/PowerCLI-Example-Scripts) and make contributions 53 | * Join some of the available Slack Teams, ask for help, offer help, and be a generally good community member! 54 | * [Commitmas Slack](https://commitmas-invite.herokuapp.com/) and then join the PowerShell Team channel 55 | * [PowerShell User Group Slack](http://slack.poshcode.org/) 56 | * [VMware Code Slack](https://code.vmware.com/slack/) and join the PowerCLI channel 57 | 58 | ## Team Puppet with [Rob Nelson](https://twitter.com/rnelson0) 59 | 60 | * Find some Puppet tickets that meet your skill and interest levels within Puppet itself or in Puppet modules 61 | * A curated set of tickets maintained by [Vox Pupuli](https://voxpupuli.org/) can be found [here](https://waffle.io/commitmas/return-of-commitmas), organized by skill and type 62 | * Join the [Puppet Community Slack](https://puppetcommunity.slack.com/) for assistance with Puppet and Modules 63 | * Feel free to participate in the [Puppet Community Hack Day](https://www.eventbrite.com/e/online-puppet-community-hack-day-december-2016-registration-28614705354) on December 13th! 64 | * Contact [Rob Nelson](https://twitter.com/rnelson0) if you have any questions 65 | 66 | ## Team Python with [Matt Oswalt](https://twitter.com/mierdin) 67 | 68 | * [pybluedot](https://github.com/commitmas/pybluedot), a Python project exploring NASA's public APIs 69 | 70 | 71 | ## The Standard Challenge 72 | 73 | Push yourself to use GitHub everyday throughout the holiday season so that by 2016 you're ready to share your next project. Here's how: 74 | 75 | 1. Schedule time in your calendar for gitting in shape **everyday** for 30 days between December 1st - January 1st 76 | 2. Choose your skill level: [Beginner](#beginner), [Intermediate](#intermediate), or [Expert](#expert) 77 | 5. Choose your team: [Ansible](#ansible), [Chef](#chef), [PowerShell](#powershell), [Puppet](#puppet), or [Python](#python) 78 | 3. Follow the directions for your team and contribute to making something awesome! 79 | 4. Fork and favorite this repository to show that you're participating! 80 | 81 | That's it! If you get stuck or just want to chat with others, be sure to [tweet with the hashtag `#vBrownBag`](https://twitter.com/hashtag/vbrownbag) or on [the Geek Speak Slack Channel]( https://commitmas-invite.herokuapp.com ) in the `#learn-github` channel. We'll be out there to help. 82 | 83 | *Note:* The Slack link doesn't always load due to using Heroku free tier. If you want a faster response, ping [Rob on Twitter](https://twitter.com/rnelson0). 84 | 85 | We'll have regularly scheduled [vBrownBag](http://vbrownbag.com) podcasts that focus on working together in git. 86 | 87 | Don't worry about getting stuck, or being rusty, we have all of last years recordings available on YouTube in our [Commitmas Playlist] (https://www.youtube.com/playlist?list=PL2rC-8e38bUXloBOYChAl0EcbbuVjbE3t) and in [iTunes](https://itunes.apple.com/us/podcast/professionalvmware-vbrownbag/id468638808?mt=2) 88 | 89 | We all have different level of expertise when it comes to GitHub. Here are a few options based on your comfort level. Remember: **focus on learning how git works** and let the other topics follow. 90 | 91 | ### Beginner 92 | *You're a beginner if:* You're new enough to git that just the act of using it daily will be a lot of learning. 93 | 94 | **Setup**: 95 | * Create a GitHub account. 96 | * [Setup Git.](https://help.github.com/articles/set-up-git/) 97 | * Initialize your own new repository with a README.md. 98 | * Clone your repository to your local development system. 99 | 100 | **Your challenge**: 101 | * Update the README.md file for your **every single day** with some new feature or functionality that your team created. This is similar to maintaining project documentation 102 | * Add a meaningful comment to your commit. [Learn the right way to comment your commits.](https://github.com/phonegap/phonegap/wiki/Git-Commit-Message-Format) 103 | * Push that commit to your GitHub repository. 104 | * Create additional repositories for scripts that you've created to do your job. 105 | * Learn how to use [`git commit --amend`](http://rnelson0.com/2014/12/26/using-git-amend-for-quick-corrections). 106 | * [Keep your fork in sync with the original repo.](http://rnelson0.com/2014/12/27/updating-your-git-fork-from-the-original-repo/) 107 | 108 | **Helpful hints**: 109 | * Remember that the goal of this is to *learn how to use GitHub*, so focus on git, not other code you'd also like to learn. 110 | * Feel free to use the GitHub website, native apps or command line. [Watch this vBB](http://neckbeardinfluence.com/technical-quick-hacking-your-way-into-github/) on GitHub to help you along. 111 | * Markdown is awesomely powerful, so challenge yourself to use some of the more complex syntax. [You can learn it all here.](http://daringfireball.net/projects/markdown/syntax) 112 | 113 | 114 | ### Intermediate 115 | *You're at an intermediate level if:* You're comfortable with the basics of using git, have lurked around on GitHub but never contributed to a project. 116 | 117 | **Setup**: 118 | * Fork your teams repository. 119 | * Clone your repository to your local development system. 120 | * Create a new branch to develop a new feature, or to fix a bug in. 121 | 122 | **Your challenge**: 123 | * Update the repository's Master branch **every single day** in some way. 124 | * On your new branch, work on a meaningful contribution to your fork of the repository. 125 | * Add meaningful comments to your commits when you commit on both branches. 126 | * Open a Pull Request on the original repository from your new branch by the end of the 30 days of Commitmas! 127 | * Learn how to use [`git rebase`](http://rnelson0.com/2014/12/23/using-git-rebase-to-rewrite-history/). 128 | 129 | **Helpful hints**: 130 | * Remember, *documentation is code too (especially when using Markdown)!* Find a project you want to support by improving documentation. Fork it and then make your contributions during this challenge. 131 | 132 | ### Expert 133 | *You're an expert if:* You've managed multiple contributor repositories before, have more than 5 pull request accepted, and want to join in Commitmas to really push yourself. 134 | 135 | **Setup**: 136 | * You've done this a few times, we don't need to tell you how! 137 | 138 | **Your challenge**: 139 | * Open a new Pull Request on open source repositories you use **every single day** for the 30 days of Commitmas! Don't forget to help out your beginner and intermediate level friends! 140 | * Find stalled PRs, cherry-pick the valuable commits, fix any failing tests or merge conflicts, and provide a new PR. 141 | 142 | **Helpful hints**: 143 | * You really don't need any, but if you complete this challenge, please tell me ([@mjbrender](http://twitter.com/mjbrender)) and I'll definitely buy you a beer. 144 | 145 | ## Resources 146 | Commitmas years past: 147 | 148 | * [12 Days of Commitmas](https://github.com/commitmas/12-days-of-commitmas) 149 | * [Commitmas 2: A Month of Merriment](http://bit.ly/Commitmas2) 150 | * [vBrownBag DevOps Series](http://vbrownbag.com/vbrownbag-technology-series/vbrownbag-devops-series/) 151 | 152 | Here are some of our favorite resources for getting going with git: 153 | 154 | * [The Git Book](https://git-scm.com/book/en/v2) 155 | * [Git - the simple guide](http://rogerdudler.github.io/git-guide/) 156 | -------------------------------------------------------------------------------- /octocat/holiday-octocat.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/commitmas/commitmas-3-return-of-commitmas/50d179ab7e9287f1612e2820701ee49debbe8d35/octocat/holiday-octocat.png --------------------------------------------------------------------------------