Find Target 🎯 Communicate 📡 Raid ⚔️ Push Code 🎉

The OSS Raid Group is what happens when you combine MMORPGs (Gamification), Mob Programming, Crowdsourcing, and Open Source Software - a group dedicated to defeating the Raid Bosses of OSS!

For those who aren't aware of these 'gamer' terms, and even those that are; here are the definitions we use when operating as a Raid Guild.

Objectives:

• To make contributing to OSS enjoyable, engaging, and with a low barrier-to-entry for those who have never done it before
• To have a high impact in a small amount of time; specifically targetting low-medium contributor activity, medium-high usage of the project, with only a handful of maintainers

What it's about:

• It's about winning the Raid as a group, not about who made the biggest contribution(s).
• It's about learning together; teaching each other, flattening the learning curve.
• It's about having fun and getting into something you may not have done on your own.
• Its's about lowering or even removing the bar of entry for OSS contributing for everyone.
• Most of all it is about having FUN!

Website: https://osrg.t3.gg/

Anyone is welcome to participate in our Raids - no matter your experience level! Never contributed to an OSS project? No worries! We are all learning something or another, so come along for the ride!

1. Say hello to your fellow Guild Members in Discord
2. Jump into a Raid, and start contributing!

When you are:

• Actively contributing to Raids
• Being an active community member on the OSRG Discord Server

Then we can determine responsibilities and get you running as either an outside collaborator on new Raids, eventually becoming a member on the Raid Org

• One Raid at a time to maximize impact in a short amount of time.

• We primarily communicate via Discord
• Guild Roles are assigned to individuals based on time, activity in Raids and contributions to OSRG as a whole, everyone starts off as an Guild Initiate who joins.

When participating in a Raid, use the following steps.

1. Raise an issue in the Raid repo with a one-liner title describing what you are working on - for example Migrate page-header/breadcrumbs tests to testing-library
2. Fork the Raid Repo (Raid Git Workflow)
3. Create a branch named after your GitHub username - e.g. nobrayner
4. Hack away 😎💻
5. Create a PR titled the same as your issue, and a description of Fixes #{ISSUE_NO} - like this PR for example

Thanks goes to these wonderful people (emoji key):

Jacob M-G Evans ⚔ 🤔 🖋 📖 🐛 🚇	Braydon Hall ⚔ 🤔 🖋 📖 🚇 🔧	Theo Browne ⚔ 🤔 📖 🚇	Juhana Jauhiainen ⚔ 🤔	Amr A.Mohammed ⚔ 🤔	Tiger Abrodi ⚔ 🤔	Marco Moretti ⚔
Peter Hozák ⚔ 🤔	Joseph Psychas ⚔	Proful Sadangi ⚔ 🤔	Sudhanshu ⚔	Michael Peyper ⚔ 🤔 🚇 🔧	Emma ⚔ 🤔	Zied.Touibi ⚔ 🤔 🎨
Kiran Jd ⚔	Cody Rose ⚔ 🤔	Datner ⚔	Ahmed ElDessouki ⚔	abeprincec ⚔	Mohit 🤔 ⚔	Yago Pereira Azevedo 🤔 ⚔
Jesse Alan Johnson ⚔ 💻

This project follows the all-contributors specification. Contributions of any kind welcome!