A curated list of open technology projects to sustain a stable climate, energy supply, biodiversity and natural resources.

Petari

An initiative by an organization aiming to redistribute excess food from various events to those in need.
https://github.com/sahil1786/petari

Category: Consumption
Sub Category: Agriculture and Nutrition

Last synced: about 14 hours ago
JSON representation

Repository metadata

Food donate Web App

README.md

Petari - The Food Donation Management System

    **Please follow me and give a star to my repository 

🏆 Featured in:

Introduction


PETARI, The Food Donate WebApp, is an initiative by an organization aiming to redistribute excess food from various events to those in need. The project aligns with India's Sustainable Development Goals to achieve a hunger-free world and zero food waste. By leveraging technology, PETARI seeks to bridge the gap between surplus food and hunger, thereby benefiting society and the environment.

GitHub issues
GitHub forks
GitHub pull requests
GitHub Repo stars
GitHub contributors

Tech Stack

Frontend

Backend






Features

Contribution Guidelines


Thank you for considering contributing to PETARI! We appreciate your efforts to make a positive impact on society through food redistribution and combating hunger. By contributing to PETARI, you are helping us move closer to our goal of creating a hunger-free world and reducing food waste. Please go through Contributing Guidelines.

How Can You Contribute?


There are several ways you can contribute to PETARI:

  1. Code Contributions: Help improve the PETARI codebase by fixing bugs, adding new features, or enhancing existing functionalities.

  2. Documentation: Improve the project's documentation to make it more comprehensive and user-friendly.

  3. Testing: Test the application and report any bugs or issues you encounter. You can also contribute by writing and running test cases.

  4. Design: If you have design skills, you can contribute by creating or improving the user interface and experience of PETARI.

  5. Feedback: Provide feedback on the existing features, suggest new ideas, or share your thoughts on how PETARI can be further improved.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Getting Started


If you're new to contributing to open-source projects, don't worry! Here's how you can get started:

  1. Fork the Repository: Fork the PETARI repository to your GitHub account.

  2. Clone the Repository: Clone the forked repository to your local machine using Git.

    git clone https://github.com/your-username/Petari.git
    
  3. Open project: Open the project directory.

    cd Petari
    
  4. Create a new branch: To create a new branch for your profile, run the following command:

    git checkout -b add-profile
    
  5. Setting up Project: Once you are in the Project directory, run this command to install all necessary npm modules

    npm install
    
  6. Setting up dotenv file: In the Project directory, create a file named ".env". Now add the following data to it

    PORT=3000
    ACCESS_TOKEN_SECRET = youraccesstokensecret
    MAIL_ID = yourmailid
    PASS_ID = your gamil app password 
    
  7. Database: If MongoDB is not installed on your local machine, install it. Once you run the project, databases and collections will be automatically created. For installation, you can follow the installation manual given on the MongoDB website for your respective operating system:

    MongoDB Installation Manual

    Once installation is done, open your terminal:

    • If you have installed MongoDB as a service, run this command to open the MongoDB Shell:

      mongosh  
      
    • Otherwise, you can run MongoDB Community Edition from the Windows command prompt instead of as a service. Open the command prompt, navigate to the MongoDB directory (e.g., C:\Program Files\MongoDB\Server\<version>\bin), and run this command:

      mongod
      

      This will start the MongoDB service. Don't close this terminal window while you are working on the project. Now run this command to open the MongoDB Shell in a new command prompt window/tab:

      mongosh  
      

    Once MongoDB is running as a service, proceed to the next step.

  8. Running The Project On Local Machine: To run the project, navigate to the project directory. Now run the command:

    nodemon app.js 
    

    If the above command gives an error, run this command:

    npx nodemon app.js
    

    Once the server starts listening, to render the webpage, go to:

    http://localhost:${PORT_MENTIONED_IN_DOTENV} or http://localhost:3000
    
  9. Checking Database: After running the project for the first time, databases and collections will be automatically created. To check if they are properly made, open the MongoDB Shell and run these commands:

    show dbs
    

    You will find a database named PetariDB. Now, run this command in the MongoDB Shell to use that database:

    use PetariDB
    

    To check collections inside the PetariDB, run this command in the MongoDB Shell:

    show collections
    

    You will see 4 collections inside the PetariDB: admins, ngos, queries, users.

  10. Make Changes: Make your desired changes to the codebase or documentation.

  11. Test Your Changes: Test your changes locally to ensure everything works as expected.

  12. Add your changed files: Add changed files to the stage by running the following command:

    git add .
    
  13. Commit Your Changes: Commit your changes with descriptive commit messages.

    git commit -m "message"
    
  14. Push Changes: Push your changes to your forked repository.

    git push
    
  15. Create a Pull Request: Open a pull request from your forked repository to the main PETARI repository. Provide a clear description of your changes in the pull request. Follow these steps

    • Add the issue number, that you have been assigned[Formate:- Isuue number #(your issue number)]
    • Brief description of the changes

Code Style Guidelines


To maintain consistency and readability, please follow these code style guidelines:

  • Use meaningful variable and function names.
  • Follow indentation and formatting conventions used in the existing codebase.
  • Write clear and concise comments to explain complex logic or algorithms.

Code Review Process


All contributions to PETARI will go through a code review process to ensure code quality, consistency, and adherence to project standards. Your contributions are valuable, and we appreciate your patience during the review process.

Community Guidelines


PETARI is committed to fostering an inclusive and welcoming community. We encourage respectful and constructive communication among contributors. Please refer to our [Code of Conduct]-(https://github.com/Sahil1786/Petari/blob/dffa12d5f33b3227ec287af602762ef1f7bc3f89/Code_of_conduct.md) for more information.

Output Screenshot

1. Index Page

The index page serves as the main landing page for PETARI. It showcases the mission and purpose of the organization, along with relevant information about its activities.

Index Page

2. Contact Page

This page allows users to get in touch with PETARI for inquiries, collaborations, or any other relevant communication. It provides contact information and possibly a contact form for convenience.

Contact Page

3. User Login

Users can log in to their accounts on PETARI's platform. This feature enables users to access personalized services, such as tracking their donations, managing their profiles, and more.

User Login Page

4. Admin Login

Admins have special privileges and access to manage the platform. The admin login page provides authentication for authorized personnel to perform administrative tasks, such as managing user accounts, overseeing donations, and maintaining the system.

Admin Login Page

License

This project is under LICENSE

  • This project thanking all the contributors for having your valuable contribution to our project
  • Make sure you show some love by giving ⭐ to our repository

Owner metadata


GitHub Events

Total
Last Year

Committers metadata

Last synced: 7 days ago

Total Commits: 111
Total Committers: 29
Avg Commits per committer: 3.828
Development Distribution Score (DDS): 0.604

Commits in past year: 80
Committers in past year: 29
Avg Commits per committer in past year: 2.759
Development Distribution Score (DDS) in past year: 0.825

Name Email Commits
SAHIL HOSSAIN 1****6 44
Pankaj Kumar Bind 7****d 8
RamakrushnaBiswal r****y@g****m 7
Prateek579 p****6@g****m 6
Ananya Gupta 1****9 5
Debmalya Kuila d****2@g****m 4
Suhani Singh Paliwal 1****l 4
Heli Detroja p****7@g****m 3
Prutha p****7@g****m 3
dhananjaysingh10 i****4@g****m 3
Laxmi Pal l****7@g****m 2
Samani Humaira s****r@g****m 2
Samarth s****1@g****m 2
Vijay Shanker Sharma v****3@g****m 2
Aditya Kumar Sen 1****5 2
Abhigna Arsam 1****m 1
Anjaliavv51 1****1 1
Meet Jain 1****1 1
Naman Parashar n****5@g****m 1
Pradnya Gaitonde 1****e 1
Praveenkumar5048 p****r@g****m 1
Shadyx6 s****x@g****m 1
Sibam Paul 1****l 1
dakshsinghrathore d****9@g****m 1
harikavaleti911 1****1 1
mahek0620 1****0 1
nipun1234 n****5@g****m 1
Sanskriti Lal s****i@S****l 1
sharmi4590 b****a@g****m 1

Committer domains:


Issue and Pull Request metadata

Last synced: 1 day ago

Total issues: 174
Total pull requests: 152
Average time to close issues: 8 days
Average time to close pull requests: 3 days
Total issue authors: 48
Total pull request authors: 35
Average comments per issue: 3.56
Average comments per pull request: 2.2
Merged pull request: 59
Bot issues: 0
Bot pull requests: 0

Past year issues: 174
Past year pull requests: 150
Past year average time to close issues: 8 days
Past year average time to close pull requests: 3 days
Past year issue authors: 48
Past year pull request authors: 34
Past year average comments per issue: 3.56
Past year average comments per pull request: 2.23
Past year merged pull request: 57
Past year bot issues: 0
Past year bot pull requests: 0

More stats: https://issues.ecosyste.ms/repositories/lookup?url=https://github.com/sahil1786/petari

Top Issue Authors

  • Sahil1786 (20)
  • Princegupta101 (13)
  • Pruthaa17 (7)
  • ayann07 (6)
  • harshnayangithub (6)
  • Tarunag03 (6)
  • harshmishra19 (6)
  • Prateek579 (6)
  • nipun1234 (6)
  • thevijayshankersharma (6)
  • Soumya6Tiwari (5)
  • DebmalyaKuila (5)
  • RamakrushnaBiswal (4)
  • shreyabagade (3)
  • palayushi293 (3)

Top Pull Request Authors

  • dhananjaysingh10 (18)
  • alishasingh06 (12)
  • yeerekarsneha (9)
  • Prateek579 (9)
  • suhanipaliwal (6)
  • RamakrushnaBiswal (6)
  • Pruthaa17 (6)
  • thevijayshankersharma (6)
  • Prachiii8287 (6)
  • DebmalyaKuila (6)
  • nipun1234 (6)
  • Srishtiii19 (6)
  • Sahil1786 (3)
  • harikavaleti911 (3)
  • pankaj-bind (3)

Top Issue Labels

  • gssoc (143)
  • GSSOC'2024 (133)
  • GSSOC'24 (99)
  • good first issue (82)
  • level2 (82)
  • level1 (47)
  • enhancement (26)
  • level3 (22)
  • documentation (19)
  • bug (15)
  • help wanted (11)

Top Pull Request Labels

  • gssoc (134)
  • level2 (123)
  • GSSOC'2024 (70)
  • GSSOC'24 (67)
  • duplicate (15)
  • level1 (13)
  • good first issue (5)
  • invalid (3)
  • documentation (1)

Score: 8.203577736937952