Contributions are welcome, and greatly appreciated! Every little bit helps, and credit will always be given.
Read on if you want to learn about how our team contributes to our project's development (Internal Contributions) and how you can get involved (External Contributions).
Our team follows the GitHub Flow. This includes creating new branches to work on changes. When the changes are ready a pull request is made, accompanied by linked issues to facilitate discussion and review. After approval, the changes are merged to incorporate the new feature or fix to our project. Branches no longer in use are deleted to maintain a tidy repository.
Here are the different types of contributions you can make!
If you are reporting a bug, please open an issue and include:
- A clear, yet concise, description of the bug, indicating details that would be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope narrow, so its easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Here's how to set up for local development.
-
Clone the repository locally. In your terminal run:
$ git clone https://github.com/UBC-MDS/DSCI-532_2024_9_solar-savers.git
-
Create and activate the
conda
environment. In the root of the repository run:$ conda env create --file environment.yml
$ conda activate solar-saver
-
Create a branch for local development and make your changes:
$ git checkout -b name-of-your-fix-or-feature
-
To run the dashboard, from the root of the directory (
DSCI-532_2024_9_solar-savers
) run:$ python -m src.app
-
Click on the displayed link to open view the dashboard on a browser.
-
When you're done making changes, check that your changes conform to any code formatting requirements.
-
Commit and push your changes, then open a pull request with a detailed description outlining your contribution.
Please note that the Solar Savers project is released with a Code of Conduct. By contributing to the development of this project you agree to abide by its terms.
This document was adpated from the eda_mds
package, developed in DSCI 524 held in 2024, found here.