When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
- Update the CHANGES.md with details of changes to the modules - this includes corrections, syllabus updates for new features, or practical information.
- You may merge the Pull Request in once you have the sign-off of another developer, or if you do not have permission to do that, you may request the reviewer to merge it for you.
Before making a DevOps Girls module, consider asking the following questions:
It's important to identify who your target audience is, and what their knowledge baselines would be. Put into practical terms: are you planning to cater for absolute beginners? Or do you aim to teach people with existing backgrounds in tech?
Even then, it's important to identify the level of experience you're working with. This is critical as you define the level of depth you want to dive in - e.g., do you assume that the attendees have experience with the command line, or do you also need to cover CLI basics?
It is also good to be able to articulate what you want the attendees to be able to do: the workshop aims to empower people, and it's useful to declare where you'd want them to be by the end of the day.
To put it into questions: do you want the attendees to be able to remember what you covered, or do you want them to be able to create a solution? Would they be able to evaluate between different solutions?
Consider using Bloom's Taxonomy of Learning as a guide.
Knowledge checks are a powerful tool - they let you verify if the attendees understand your content, while at the same time encouraging knowledge retention. This is why teachers usually structure lessons so that there are quizzes at the end of it.
Feedback can take many shapes: a quiz, a poll, or a question at the end of your practicals. Maybe make it fun even - have some small prizes for attendees who ask good questions.
It's good to have a fun, informative talk before diving into the practicals. Consider covering the following areas:
- The history and context of the particular technology
- How it works
- How and when to use it
- How it's valuable to the business
Keep it short, but remember to pace down. It's better to take your time than rush too fast and risk leaving people behind - remember: not everyone is willing to ask you to repeat concepts and facts.
Consider running a practical exercise that the attendees can follow. A few things to keep in mind:
- Make sure that everyone knows beforehand what they need to go through it. Do they need
awscliinstalled? Do they need their own AWS account? - Make sure that the environments the attendees are deploying/building to are enclosed and free of dependencies.
- Make sure that coaches have gone through the material beforehand.
If you're feeling up for it, moonshots are also a good idea - optional exercises for those who blitz through the material.
Consider saving a portion of time for reflection and self-evaluation. Ask the attendees questions (whether in text or face-to-face):
- What did you learn?
- How would you apply this to something you want to do?
It's worth thinking about the day as a whole. There's multiple ways that you can structure an all-day DevOps Girls workshop.
The "Kata" is essentially a way of structuring your content so that all your modules produce roughly the same output. Imagine an EC2, ECS, and Lambda modules all producing a standard webapp.
This approach works if you want to enable attendees by giving them the ability to distinguish between different ways to approach a problem. When do I use an EC2 versus a Lambda? would be the kind of questions that they will be able to answer.
The "Castle" is a way of structuring your content so that your modules contribute to one big thing. Imagine an EC2, RDS, and ELB module all contributing towards building a reasonably complex ecosystem.
This approach works if you want to enable attendees by giving them the experience of wiring up several systems and making them understand how to make everything work together. AWS thrives on providing "lego blocks" that you can stitch together, and this is a good way to highlight that.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4