contributions.md

Contributing to our package

We welcome all contributions to this project! All contributors must abide by our code of conduct.

Summary of Contributions

Below, briefly describe the specific contribution(s) each team member (including yourself) made to our project.

How the team will work together

We will have a meeting to discuss which API we should be using. Once we come to an agreement, we will divide which functions we each would like to work on. Then, we work individually in our own branches to develop the functions from start to finish including the documentation and the tests. We then create a pull request to get each of our codes reviewed before merging. After reviewing the codes, we solve any pending conflicts. Then we ensure that our packages work properly before configuring the CircleCI. If we encounter any issues, then we will solve it together as a group through direct commits in a zoom call. We will then do integration tests through CircleCI to ensure that we have passing build stamps. Then we will finalize the contributions.md and readme.md file as a group.

Contributions

Development: Anqi, Evelyn, Val, Xin

Testing: Anqi, Evelyn, Val, Xin

Documentation: Anqi, Evelyn, Val, Xin

Project configuration: Anqi, Evelyn, Val, Xin

Integration: Anqi, Evelyn, Val, Xin

CircleCI configuration: Anqi, Evelyn, Val, Xin

Group Work

Everything went well and we learn a lot from each other. Each member actively and equally contributed to the project. We enjoy working together and supporting each other throughout this project. We were able to collaborate more which helped us a lot in carrying out this project. Also, we helped each other and took guidance whenever we thought we need help. Overall it was a combined efforts and as a result we are able to deliver the efficient project on time.

Things that went well

We worked very effiently. We first devided the tasks and did everything based on the contributing.md file plan. Team work, support learning, time management. Our zoom meetings were frequent and very productive. Our communication was clear and went well. The atmosphere is very enthusiastic and productive especially when trying to solve bugs in our codes as a group.

Things that went poorly

LaTex issues when building vignette to PDF with Windows, but we were able to solve this by using the MacOS of one of our team members.



evelynsugi/weatherapi documentation built on April 7, 2022, 12:43 p.m.