README.md

OpenCode20-Collaborative-TheApp

This is the official app for OpenCode'20 that fetches you contest details on the go..

Why OpenCode app

In the present scenario there where each and every device is online, there was a need for a one stop place for all information regarding OpenCode'20.

Communicate

Chat with us on Slack and Like us on Facebook

Requirements

Basic Git and Github. (Feel free to contact any mentor if you have any issue regarding Git or Github)

Getting Started

To get this project up and running on your local machine, all you need to do is clone or download this project, Open this project in android studio and run it on any android device or emulator.

Installation and Contributing

1. Fork the project

2. In gitbash or terminal, use the following commands -

   2.1 git clone {url of the forked repo (the one in your account)}

   2.2 git remote add original {url of original repo.} (You can use this remote to sync your repo with the original project) Syncing a fork

3. After you have solved the issue in your local system, you need to commit the changes, push them to your repository, and send a pull request. Refer: 1. Making changes and commits 2. Pull Request

Claim an issue

To claim an issue please comment on the issue. In case of no activity on the issue even after 2 days, the issue will be reassigned.

Guidelines

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.

1. Project specific guidelines.

   0.a We will not entertain any hard coded strings or colors etc. Please add the resource in the corrosponding xml.

   0.b Attach Screenshots or video (whichever applicable) with the PR.

2. 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.

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

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

5. Make a note to add relevent Screen Shots when you make a PR.

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

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

8. 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.

9. Be polite: Be polite to other community members.

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

See also the list of contributors who participated in the project.