In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

I added these to requirements.txt as these are imported.

• discord-webhook (StartPageGUI.py)
• pymongo (MongoDB.py, LoginPage.py)
• colorama (StartPageGUI.py)

under GsSOC'24

For importing the utts, as there are many sql files in the DatabaseFiles directory , it would be handy and useful to add an all_files.sql file, to make the importing process easier. @HartzFrequency please assign me this issue, I am an gssoc'24 contributor and I want to work on this issue.

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

What's missing in this repository
Code of Conduct
A Code of Conduct is crucial for maintaining a respectful and inclusive community. It sets clear expectations for behavior and outlines the steps for reporting and addressing unacceptable behavior. Here’s why it’s important:

-Sets Behavioral Expectations: It clearly defines acceptable and unacceptable behavior, helping to create a welcoming and inclusive environment for all participants.
-Promotes Respect and Inclusivity: It encourages respect and inclusivity, ensuring that everyone feels safe and valued within the community.
-Conflict Resolution: It provides guidelines on how to handle conflicts and what actions will be taken in response to violations, promoting fairness and transparency.

Contributing File
The Contributing file provides guidelines for how to contribute to the project. This includes everything from coding standards and style guides to how to submit pull requests and report issues. Here’s why it’s essential:

-Encourages Contributions: It provides clear instructions on how to get involved, making it easier for newcomers to start contributing.
-Maintains Quality: It sets standards for contributions, ensuring that new code and documentation meet the project's quality requirements.
-Streamlines the Process: It outlines the process for submitting contributions, reducing friction and confusion for contributors and maintainers alike.

Kindly assign this issue to me under GSSoC'24

👋 Hi @HartzFrequency,

I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

• #41
• #42
• #43
• #44
• #45

Update project dependencies and exclude unnecessary files in "requirements.txt" and ".gitignore" for streamlined development and version control.

The README has a brief contribution section but lacks detailed guidelines. I will add a CONTRIBUTING.md file with detailed instructions on how to contribute to the project.

Assign this issue to me.

I will add all the missing dependencies.
Could you assign me this for GSSoC'24

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.

The current README for our project serves as the first point of contact for users and potential contributors. However, it could benefit from enhancements to better communicate the project's purpose, functionality, and how to effectively engage with it.

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

Our current SQL-based static database might be experiencing limitations in accommodating the growing volume and complexity of data. MongoDB's document-oriented data model provides a more natural representation for certain types of data, eliminating the need for complex joins and offering better horizontal scalability.

I would like to add a pull request template for this repository. Please assign me this issue under GSSOC'24.

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

Could you please assign me this issue under GSSOC'24.

Improve error handling, file checks, and versatility in FileHandling.py.

The registration form have no submit button for registering a new user.

Dear HartzFrequency,

I hope you're doing well. I wanted to discuss the addition of some crucial database files to this unified traveling and transport system. These additions will significantly enhance our system's functionality and improve user experience.

1. Payments:
   Database File: payments.sql
   Description: This file will handle payment transactions, including storing payment details, transaction IDs, and related information.
   Bookings History:

2.Database File: bookings_history.sql
Description: This file will track the history of bookings made by users, providing insights into past travel patterns and preferences.
Feedback and Reviews:

3.Database File: feedback_reviews.sql
Description: This file will manage user feedback and reviews for different transportation modes and routes, helping improve service quality and user experience.
Assign me this issue I surely work on it.
Thank You

Issue: GUI_module files lack documentation such as inline comments, DocStrings for better code readability

About project: The project is about Unified Travelling and Transport system which provide features such as real time tracking, payment options and fare estimation.
My understanding about the project: I could relate it to the system which already exists in today's systtem UPI, I think that could be part where the idea could be generated. Able to document the code would make it easier to contributors to contribute much easier.

I believe I could work on this issue. Please consider my request to be assigned to this issue Thank you.

The requirements.txt file seems to be missing some required libraries. Packages like pymongo, discord_webhook, and colorama are not listed, but they might be necessary for the application to function properly. It would be helpful to add them to the file for a smoother setup process.

I'm interested in contributing to this project and would be happy to assist in implementing these improvements or any other areas that require attention.

Thanks,

Anjali Priya

Hii, I m a GSSOC'24 contributor
A code of conduct file is necessary to ensure smoother contribution and collaboration abiding by the rules and no dissent and make everyone aware about the actions which can take place on not abiding. So please allow me to add it and assign the issue under GSSOC'24.

Dear Harsh Shrivastava,

I hope this message finds you well. I've been following the development of the Unified Travelling and Transport System (UTTS) project with great interest. After reviewing the project's goals and current status, I'm excited to do my contributions to the backend development efforts.

Here's a brief overview of my proposed contributions:

Backend Development: I specialize in backend development using Flask, and I'm keen to assist in enhancing the backend functionalities for UTTS.
Feature Additions: I can help implement new features such as route optimization algorithms, user authentication, and API integrations with external services.
Code Review and Optimization: I'm proficient in code review practices and can provide valuable feedback to improve code quality and performance.
Thank You

The theme or appearance mode chosen by the user doesn't seem to persist across different windows within the application. Implementing a mechanism to maintain the user's preference throughout the application would enhance consistency.

Hii, I m a GSSOC'24 contributor
to maintain the codeQuality and Code - reusability, it is necessary to add CodeQL in this repo.
So please allow me to add it and assign this issue under GSSOC'24.

Assign this issue to me

I will add details for setting up the virtual environment & installing the required dependencies.

current Requirements.txt is wrong and not in proper format it should get updated asap

tk
customtkinter
pillow
mysql-connector-python

this is not correct format

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

Could you please assign me this issue under GSSOC'24.

I would like an automated feature that posts a predefined comment on an issue as soon as it is created. This feature aims to address the problem of delayed and inconsistent communication following the creation of issues. By automatically commenting on issues as soon as they are created, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

Could you please assign me this issue under GSSOC'24.

A README file is essential in any given repository because it serves as the primary source of information about the project. It provides an overview of the project's purpose, how to install and use it, and any necessary prerequisites. Additionally, the README often includes guidelines for contributing, links to documentation, and contact information for the maintainers. By consolidating all critical information in one place, a README file significantly improves the user experience and facilitates effective project management.
It's important to represent/add more enhanced readme file for creating user interest in the given repository .

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

I would like to add a issues template for in this repository. I believe that having a standardised template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review issues.

Could you please assign this issue to me under GSSOC'24.

The pixel track travel project aims to track movement on a pixel grid, counting visited pixels to avoid revisiting them. This optimization reduces costs. The solution involves developing a pixel tracking algorithm, using efficient data structures for pixel storage, implementing optimization techniques, optimizing code for performance, testing thoroughly.

The solution comprises developing a pixel tracking algorithm, using efficient data structures, implementing optimization techniques, optimizing code for performance, thorough testing.It includes filtering the image,taking links in multiple numbers,trajectory,track of visited/unvisited,etc.

I would like to take this task under GSSOC'24.

Hope I make it to your sight..

Thanks.

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.