Thank you for your interest in contributing to Study Group Event Visualization 🎉! If you're interested in contributing, you should find all of the details here. We've centralized it into this repository, we'd like to keep things tidy and focused. Issues and roadmap goals will reflect changes across multiple repositories on Github, so you'll have the opportunity to contribute to multiple aspects of this project.
Study Group Event Visualization is to create a friendly, no-pressure environment where people can share their work, ask for help on a coding problem, and learn and work together with their peers.We'd like to create a useful workflow between these tools and datasets, enabling us to create visualizations of the activities or events from all Study Groups globally. There are multiple steps to this process, with the overall goal of improving web visibility and accessibility for our Study Group community.
This document is a set of guidelines for contributing to Study Group Event Visualization on GitHub. These are guidelines, not rules. This guide is meant to make it easy for you to get involved.
- Participation guidelines
- What we're working on
- How to submit changes
- How to report bugs
- Communication channels
This project adheres to a Mozilla Community Guidelines. By participating, you are expected to uphold this code. Please report unacceptable behavior to Aurelia.
Take a look at the issues in our current milestone or browse for some good first bugs to get started!
Once you've identified one of the issues above that you feel you can contribute to, you're ready to make a change to the project repository! Try not to pollute your pull request with unintended changes – keep them simple and small. If possible, squash your commits.
- Fork this repository. This makes your own version of this project you can edit and use.
- Make your changes! You can do this in the GitHub interface on your own local machine. Once you're happy with your changes...
- Submit a pull request. This opens a discussion around your project and lets the project lead know you are proposing changes.
First time contributing to open source? Check out this free series, How to Contribute to an Open Source Project on GitHub.
Notice a mistake? Please file any bugs, requests, or questions in our issue tracker!
- Search for existing issues. Please check to see if someone else has reported the same issue.
- Share as much information as possible. Include operating system and version, browser and version. Also, include steps to reproduce the bug.
If you have anything to share, anything at all, feel free to drop by the Study Group room on Gitter and say hi. We would love to hear from you. You can also contact Aurelia or Anamika.