https://github.com/ajinkyataranekar/pr424_revengers
https://github.com/ajinkyataranekar/pr424_revengers
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/ajinkyataranekar/pr424_revengers
- Owner: AjinkyaTaranekar
- Created: 2020-07-31T14:28:29.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2023-01-06T13:00:19.000Z (over 2 years ago)
- Last Synced: 2025-02-03T10:34:22.922Z (4 months ago)
- Language: JavaScript
- Size: 20.5 MB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 16
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# PR424_Team_Revengers_AgriSmart
# AgriSmart
AgriSmart is an app which connects farmer and transporters on a common platform. Where farmers can get connected with Transporters.
It features quick booking, pooling feature and push notifications and much more!!!
Have a look at these presentation to get started with the idea:
https://drive.google.com/drive/u/0/folders/1U-_Xh8mOxMBwlV6p2VZJNW5IHAzDoCh-
## Goals
## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
## Requirements
* Any operating system (i.e. Linux, Windows, MacOS X)
* A little knowledge of React Native. Don't worry if you are new to it, you just need knack to learn.
* Any IDE with React Native installed (i.e. VSCode, Android Studio, etc)
## Development Setup
- Install node, npm.
- add Android Studio
- Install react native
## To start
- move to AgriSmart folder
- npm i
- react-native run-android
## Contribution Guidelines
Please raise a feature request or issue before sending PR for the same.
Follow the below guidelines for proper coding practices:
- Always [create a new branch](https://confluence.atlassian.com/bitbucket/branching-a-repository-223217999.html) for your changes and make PR from it ONLY.
- Write neat code with proper comments.
- Follow PEP8 coding style.
- Write descriptive commit messages. Please [read this](https://github.com/erlang/otp/wiki/writing-good-commit-messages) for more information.
- Write detailed PR messages and include `fixes #ISSUE_NUMBER` it if closes an issue, otherwise use `concerns #ISSUE_NUMBER` to tag the related issues. Please [refer here](https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/) for more PR guidelines.
- It is recommended to have a single commit for a task.
- Use [DRY principles](https://thealphadollar.github.io/learning/2019/05/13/go-dry.html) to create maintainable code.
## Authors
* **Ajinkya Taranekar**
* **Abhishek Singh Baghel**
* **Deeksha Soni**
* **Mahak Mandelecha**
* **Ritik Gandhi**
* **Ritik Nandwal**
## License
This project is licensed under the SGSITS.
[]
[]
[](http://ForTheBadge.com)