saiyamtuteja/faculty_evaluation_system

Hi , I'm Saiyam Tuteja

I am currently a final Year student at COER Roorkee pursuing my BCA degree .Here to contribute in Open Source projects and learn new things on the go. Currently, I am focused on strengthening my programming skills, particularly in C++ and data structures. I possess a solid foundation in C , having mastered their basics. I believe that continuous learning in the ever-evolving field of technology is key to staying relevant and making a meaningful impact.

---

Talking about Technical Stuffs:

• 👨🏽‍💻 I’m a second year Enginnering student.
• 🌱 I’m currently learning DSA , C++ and Full Stack Development.
• 💬 Ask me about anything, I am happy to help.
• 👾 Fun fact:People who are using a computer blink 66% less than those who aren’t..
• 📝 Do checkout my [Resume]

My Absolute Favorites:

• 💻 I love exploring new tech stack and building cool stuffs.
• ⚡ Hackathons & tech events.
• 🎮 Playing Basketball.
• 🎵 Listening to Music.

---

Languages and Tools:

GSSOC(24) Badges

---

Get in Touch! 📬

       

✍️ Random Dev Quote

---

Credits: Saiyam Tuteja

Last Edited on: 24/07/2023

faculty_evaluation_system's Issues

Add Code of Conduct

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

Feat: Auto Commenting when an issue is closed by maintainer

Describe the feature

This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Undo and redo

Describe the feature

Option for undo and redo

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Auto Commenting when a PR is merged

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.

Feat: Workflow for closing old issues

Describe the feature

This feature aims to automate the process of managing old issues, ensuring that the repository remains organized and focused on relevant tasks. By automatically closing old issues, it reduces manual overhead for repository maintainers and helps keep the issue tracker tidy and up-to-date.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Automatic Comment on Pull Request Raised

Describe the feature

Often, when pull requests (PRs) are raised, reviewers may lack crucial context about the changes proposed. This can lead to delays in the review process and misunderstandings between contributors and reviewers.

Add ScreenShots

NA

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Changing the name of the project

What's wrong with the existing documentation

Update project title and headers in all documentation files.
Modify project descriptions to reflect the new name.
Perform a global search and replace for old project name (Faculty_Evaluation_System) to new project name.
Update README.md and other Markdown files.
Update configuration files with the new project name.
Modify comments and code documentation.
Review and test all changes.

Add ScreenShots

No response

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Add Topics

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

BUG: Not able to run evaluation_db queries - value of Avatar cannot be set to null

Is there an existing issue for this?

• I have searched the existing issues

What went down?

Modify the queries wherever "avatar" coloumn is present - change it to a datatype that can have the above default value

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: could you please provide your website link directly in repo

Describe the feature

user can easily access your website directly if you could provide the website link in repo to view and contribute

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Adding regex for input fields

Describe the feature

Add a regex for :

• CUID as an email (with a helper text telling it must contain an @ symbol
• Password (generic strong password rules)

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

DOC: Addition of Contributor's logo's

What's wrong with the existing documentation

Ntg , addition of Contributor's logo's.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

BUG: No changes made to account details but still get a "username already exists"

Is there an existing issue for this?

• I have searched the existing issues

What went down?

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

BUG: Facing issue of "Invalid email" in faculty login

• I have searched the existing issues

What went down?

I have seen that, user with faculty permission is not able to login. It is giving "Invalid email" error.
I am attaching the screenshot.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Avoiding SQL injections using prepared statements of MySQLi (Open for contribution)

Describe the feature

In the current implementation , we are directly passing the POST data with session variables into the query string which can expose the application to SQL injection. Re-factor the SQL statements in admin_class.php file to mitigate this.

Add ScreenShots

Refactor items like these into:

Prepared statements like these:

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Auto comment when a pr is raised

Describe the feature

This will add a feature to give instant comment to user after raising a PR

Add ScreenShots

When we get comments on pull requests right after they're submitted, it shows us contributors that the admins are paying attention and appreciating our hard work. This helps create a friendly atmosphere where teamwork thrives, making everyone more likely to keep pitching in and staying involved.
This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs
Could you please assign me this issue under GSSOC'24 and appropriate level too

Thank You

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

DOC: Add GitHub Desktop Contribution Instructions

What's wrong with the existing documentation

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.

Add ScreenShots

No response

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

adding contributors page

Describe the feature

Mention all the contributors

Add ScreenShots

.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

BUG: Deleting old profile photo while adding new

Is there an existing issue for this?

• I have searched the existing issues

What went down?

When the user updates his profile and changes the profile photo, new photo will get updated successfully.
It is necessary to delete the old image from the server as unused assets will increase the memory usage.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Adding a readme

As a GSSOC'24 contributor, I want to contribute to the project by updating a proper readme file of the project as a readme file is your project's description and first look. So I hope you can assign me this task

BUG: Absence of an SQL query for storing faculty sign-ups

Describe

here as you can see in the code there no logic written for storing the data if user type is set to faculty

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

[FEAT]: Create Issue forms and make the issue options more visually appealing

Describe the Feature you want to end

Currently, the issue template for this repo seems to be basic also it is less visually appealing.👇

Changes I will make

Expected behavior

Screenshots (optional)

Additional context (optional )
Will add issue forms to the respective issues to make it easier for the contributor to raise it.
Here is an example of how a Bug Issue Form will look like 👇

Add PR template

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

[FEAT] : sign up

Describe

Inside the Sign Up page the Form submission was not done 

improving readme file

What's wrong with the existing documentation

In the readme file there is no way to understand how to run the project after forking. Kindly assign this issue to me for Gssoc '24

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Adding Dark Theme

Describe the feature

I would like to add dark theme button to the header to reduce eye strain and provide preferences to the users. Please assign me this issue. Thank you!

Add ScreenShots

None

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

"Username or password is incorrect" Error

Is there an existing issue for this?

• I have searched the existing issues

What went down?

I have encountered an issue of "Username or password is incorrect" while user is entering correct credentials as well!
I am attaching some of the screen shots regarding the issues!

I have registered on the platform!

The database has been updated successfully!

While I am trying to login!

I would like to work on this issue!

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Workflow for closing old PRs

Describe the feature

This feature aims to automate the management of open PRs in a repository, ensuring that outdated or abandoned PRs are closed in a timely manner. By doing so, it helps maintain repository hygiene, improves workflow efficiency, and provides a better experience for both maintainers and contributors.

Girlscript Summer of Code Introduction/Tracking

👋 Hi @SaiyamTuteja ,

I am Sanjay, program Manager 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 on 10th May.

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

• #1
• #2
• #3
• #4
• #5

Missing CONTRIBUTING.md File in Repository

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.

DOC: Adding All Contributors Profile Photos in Readme.md file

What's wrong with the existing documentation

• It lacks Contributors Profiles in Readme.md
• It should be Like the image that I have shared

Hey! @aswinikalyan30 I have already fixed it. Can you assign me this issue under GSSoC so that I can raise a PR.

Little about me: I am an experienced contributor as I have successfully completed Hacktoberfest-2020 and Hacktoberfest-2023

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Give a unique name for the project and create a logo for the same

Describe the feature

The current system is built for a specific college - make it as a generalised project with which any college can integrate

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Add issues

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 can add the tag GSSoC'24, good first issue etc.
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

Feat: stylize the navbar

Describe the feature

the navbar looks pretty simple so going to update it and stylize it to make it visually appealing

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Add templates for issues

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.

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

Feat: Filter genuine email

Describe the feature

Security Feature

In your application anyone can enter using temporary or disposable email.
I will add a feature so that no one could create an account using temporary or disposable email.
It will allow only genuine users in your database.
It will help to avoid any bot.
Assign me this work under GSSoC24, I will implement it.

Add ScreenShots

.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Change the UI Icons on signup page

Is there an existing issue for this?

• I have searched the existing issues

What went down?

UI Elements plays an important role for user interaction.
On signup page there are various input fields.
I have seen that most of them have the same icon which may be bit confusing for the user.
I would like to change some icons on signup page to make it user friendly.
Assign this issue to me.

Record

• I'm a GSSOC'24 contributor
• I agree to follow this project's Code of Conduct
• I want to work on this issue

Add Reset Password

Describe the feature

ADD FORGOT PASSWORD AND PROVIDE OPTION FOR LOGGING OR SIGNIN WITH GOOGLE

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Adding the Remember me feature

Describe the feature

Adding remember me feature in the login of system.
This will help user to be logged in even after restarting the browser.
Assign this issue to me!

Add ScreenShots

Screenshot of the login page.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

BUG: Contributor Avatar Image is mismached

Is there an existing issue for this?

• I have searched the existing issues

What went down?

I have seen the profile of contributors and the avatar image is not properly matched

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat: Toggle View for Password field during signup and login

Describe the feature

The field currently shows as password field which can be modified to have a show/hide toggle

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Automated Greeting Workflow

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."

Please assign this issue to me.

BUG: Not able to create student as class_id parameter of student_list is missing from the form

Is there an existing issue for this?

• I have searched the existing issues

What went down?

The class_id is in the schema of the database in the student_list table (can find it in evaluation_db) but while inserting the record during signup it is not taken from the user
Hence, add it to the form and read the value from the form

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

To make the authentication system stronger, I make students and faculty to enter only the emails provided by the university. In addition to that I'll make this project available to many universities

          To make the authentication system stronger, I make students and faculty to enter only the emails provided by the university. In addition to that I'll make this project available to many universities

@SaiyamTuteja please assign this project for me.

Originally posted by @Gayathri-Pavuluri in #4 (comment)

Learn.md

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

Adding a Pull Request Template 🚀

What's wrong with the existing documentation

Similar to the Issue template - Create one while someone raises a PR which describes

• Is this a bug fix/enhancement/documentation change
• What are the changes made?
• Checklist for - part of gssoc, tested for any breaking changes and other relevant checks
• Issue for which you are raising a PR for

Add ScreenShots

No response

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

updating README file

What's wrong with the existing documentation

Adding contributors profile in readme file

Add ScreenShots

No response

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Feat:cForgot Passowrd in login page

Describe the feature

Use the signup details for forgotten password for changing the password

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Implementation of contact us page

Describe the feature

The website currently lacks a "Contact Us" page. This page is crucial for providing users with a direct means to reach out for support, feedback, or inquiries.

Solution: Implement a "Contact Us" Page

Create a New Page:
Develop a dedicated "Contact Us" page that can be easily accessed from the main navigation menu. This page should include:

A contact form for users to submit their inquiries directly through the website.
Relevant contact information such as email addresses, phone numbers, and physical addresses.
Links to social media profiles for additional means of contact.
Design the Contact Form:
Name
Email Address
Subject
Message
User Experience Enhancements:
Include a confirmation message to inform users that their message has been received.
Ensure that the "Contact Us" page is responsive and accessible on all devices.

Add ScreenShots

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue