OpenCode22

Fitezo

A Flutter based fitness app solely focused on fitness related solutions.

Tech Stack

• Flutter
• Firebase

Getting Started

• Setup Git
• Set up flutter and Android Studio
• Or setting up VS code for flutter

Note: Recommend using the latest version so as to avoid any issues related to depreciated methods/widgets.

Local Setup

• Fork the repo.
• Clone it to your local setup by using the command git clone <repo link>
• Open the project with Android Studio or VS code

Directly cloning from Android Studio (Alternate method):-

• Go to FILE -> NEW -> PROJECT FROM VERSION CONTROL
• Copy and paste the url of FORKED repo in the URL field and click clone.

Before cloning the project make sure you have set up the IDE correctly according to the resources given in the getting started section.

Claim an issue

Comment on the issue. In case of no activity on the issue even after 2 days, the issue will be reassigned. If you have difficulty approaching the issue, feel free to ask on our discord channel.

Communication

Whether you are working on a new feature or facing a doubt please feel free to ask us on our discord channel. We will be happy to help you out.

Guidlines

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.

• People before code: If any of the following rules are violated, the pull-requests must not be rejected. This is to create an easy and joyful onboarding process for new programmers and first-time contributors.

• Single commit per pull request and name the commit as something meaningful, example: Adding <-your-name-> in students/mentors section.

• Reference the issue numbers in the commit message if it resolves an open issue. Follow the pattern Fixes #

• Provide the link to live gh-pages from your forked repository or relevant screenshot for easier review.

• Pull Request older than 3 days with no response from the contributor shall be marked closed.

• Do not make PR which is not related to any issues. You can create an issue and solve it once we approve them.

• Avoid duplicate PRs, if need be comment on the older PR with the PR number of the follow-up (new PR) and close the obsolete PR yourself.

• Be polite: Be polite to other community members.