Skip to content

Commit 8b2752f

Browse files
committed
updating files
1 parent dc1e8c4 commit 8b2752f

File tree

471 files changed

+49337
-18582
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

471 files changed

+49337
-18582
lines changed

CODE_OF_CONDUCT.md

+128
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

+92
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
# Contributing to Enatega Multi Vendor Food Delivery System
2+
3+
First off, thank you for considering contributing to our project! Your help is greatly appreciated.
4+
5+
## How Can I Contribute?
6+
7+
### Reporting Bugs
8+
9+
If you find a bug in the project, please submit an issue. When reporting a bug, please include:
10+
11+
- A clear and descriptive title.
12+
- A detailed description of the problem, including steps to reproduce.
13+
- Any relevant logs, screenshots, or other information that could help diagnose the problem.
14+
15+
### Suggesting Enhancements
16+
17+
We welcome suggestions for improvements and new features. When suggesting an enhancement, please include:
18+
19+
- A clear and descriptive title.
20+
- A detailed description of the proposed change.
21+
- Any relevant context or reasoning for the enhancement.
22+
23+
### Pull Requests
24+
25+
If you would like to contribute code, follow these steps:
26+
27+
1. **Fork the repository**: Create a fork of the repository on GitHub.
28+
2. **Clone your fork**: Clone your fork to your local machine.
29+
```bash
30+
git clone https://github.com/<your-username>/food-delivery-multivendor.git
31+
cd food-delivery-multivendor
32+
```
33+
3. **Create a new branch**: Create a new branch for your feature or bugfix.
34+
```bash
35+
git checkout -b feature-or-bugfix-description
36+
```
37+
4. **Make your changes**: Make your changes to the code.
38+
5. **Test your changes**: Ensure your changes work as expected and do not introduce any issues.
39+
6. **Commit your changes**: Commit your changes with a descriptive commit message.
40+
```bash
41+
git add .
42+
git commit -m "Description of the feature or bugfix"
43+
```
44+
7. **Push your changes**: Push your changes to your fork.
45+
```bash
46+
git push origin feature-or-bugfix-description
47+
```
48+
8. **Submit a pull request**: Create a pull request from your fork to the main repository. Include a detailed description of your changes.
49+
50+
### Coding Guidelines
51+
52+
To ensure consistency in the codebase, please follow these guidelines:
53+
54+
- **Code Style**: Follow the existing code style in the project.
55+
- **Comments**: Write clear and concise comments for complex code sections.
56+
- **Tests**: Write tests for new features and bug fixes.
57+
58+
### Code of Conduct
59+
60+
By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).
61+
62+
## Getting Started
63+
64+
### Prerequisites
65+
66+
Ensure you have the following installed:
67+
68+
- Node.js (version 14.0 to 16.0)
69+
- npm or yarn
70+
71+
### Setting Up
72+
73+
1. **Clone the repository**:
74+
```bash
75+
git clone https://github.com/enatega/food-delivery-multivendor.git
76+
cd food-delivery-multivendor
77+
```
78+
79+
2. **Install dependencies**:
80+
```bash
81+
npm install
82+
# or
83+
yarn install
84+
```
85+
86+
3. **Run the development server**:
87+
```bash
88+
npm start
89+
# or
90+
yarn start
91+
```
92+

0 commit comments

Comments
 (0)