Github Issues

Help Us Make Rock Better

Assisting with Github issues is a great way to help the community move Rock forward. You don't need to be able to write code to lend a hand. Several steps only require some time and basic understanding of how to use and configure Rock.

1. Classify Issues

current count

4

 Start Here

We have a brand new issue here that needs to be classified (by labeling issues) as either:

  • Bug - Something is broken
  • Enhancement - Something can be improved
  • Duplicate - An issue already exists
  • Documentation - This is really more of a documentation thing (prefer these to be documentation requests from the Learn pages)
  • Discussion - These usually go hand-in-hand with enhancements

2. Confirm Issues that Are Labeled As Bugs

current count

1

 Confirm These

These issues have been labeled as bugs, but before developers can look at them we need someone to confirm they are real. It's best to reproduce the issue on the demo or prealpha site. The submitter should have provided steps to reproduce the issue. If not, feel free to push back.

3. Fix Issues

Available Bugs

0

 View Items

Once issues have been classified and confirmed, the core team will label some for the community to take. These are labeled 'Status: Available'. When you find an issue you'd like to tackle, assign the issue to yourself. This tells everyone you're on it. If you'd like guidence on your solution, feel free to add comments to the issue. Other community and core team members are happy to help brainstorm your proposed fixes.