Currently, there is an issue template for this repo, but no issue form which will help users in contributing.

• I 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 👇

• and issue templates:

I would like to add scraping feature for scraping the schedules for contest of coding ninjas

Is your feature request related to a problem? Please describe.
Giving ease to users to add notes about how was there contest will help them evaluate there learnings.

Describe the solution you'd like
Making a note icon from the frontend side and defining a logic in the backend to save notes that user make per contest will be helpful.

Additional context
I am MENTOR for this Project under GSSOC'24 raising this issue for contributors.

Year need to update dynamic

i can add a sign - up page using MongoDB database. plz assign me this , I am a contributor under GSSoC 2024.

Hi @owner,

I hope this message finds you well. I am a participant in the GirlScript Summer of Code (GSSoC) event and I would like to contribute to this project.
Identified issues in ratingsController.js

• Inconsistent error handling/logging.
• Incorrect error handling in 'codeforcesRating'.
• Limited error differentiation in 'leetCodeRating'.
  Suggestion: Consistent logging, correct error access, enhanced error messages.
  Could you please assign this issue to me so I can start working on it and submit a pull request for your review?

Thank you for considering my request. I look forward to your response.

Is your feature request related to a problem? Please describe.
As a user it will be helpful for me to have a record of given contents to evaluate my over all learnings.

Describe the solution you'd like
We can maintain a checkbox in the list view of the contest list for the users to mark it as given.

Additional context
I am a MENTOR in this project under GSSOC'24 raising this issue for contributors.

Giving users an ease to login with there gmail in our web app will make UX better. One can achieve this using firebase oauth service of google to login or sign up.

I am a MENTOR in GSSOC'24 raising this issue for contributors to contribute.

As i went through the deployment link register and login are not working as there backend services are not there, This side Jatin here am a backend developer working with Node.js from past 3 years would like to add REST API's for authentication purpose.

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.

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

Onboarding Screens for New Users

Description:

I will add onboarding screens to the CrazyCoder app to enhance the user experience for new users. The onboarding process will provide a brief and clear introduction to the app’s features and benefits, helping users understand how to make the most out of the app. This feature is crucial as it sets the first impression and ensures that users are well-informed about the app’s capabilities from the start.

Purpose:

The onboarding screens will serve to:

1. Introduce new users to CrazyCoder and its purpose.
2. Highlight the key features and functionalities of the app.
3. Guide users through the initial setup and permissions required for the best experience.
4. Promote user engagement and retention by making users feel welcomed and informed.

Content for Onboarding Screens:

1. Welcome Screen:

   • Brief introduction to CrazyCoder.
   • Message: "Welcome to CrazyCoder - Your Ultimate Companion for Competitive Programming!"

2. Feature Highlights:

   • Overview of the app’s main features.
   • Messages:
     • "Stay Updated with All Coding Contests and Hackathons Across Multiple Platforms."
     • "Set Reminders, Never Miss a Contest!"
     • "Compare Ranks with Friends and Engage in Healthy Competition with Leaderboards."

3. Interview Preparation:

   • Highlight the SDE section for interview prep.
   • Message: "Prepare for Interviews with Content Recommended by MAANG Employees."

4. User Interaction:

   • Explain the social features.
   • Messages:
     • "Chat with Friends and Discuss Strategies."
     • "Track Your Progress and Visit Profile Pages Directly from the App."

5. Getting Started:

   • Guide users on how to start using the app.
   • Message: "Let’s Get Started! Set Up Your Profile and Explore CrazyCoder."

Steps to Implement:

1. Design the onboarding screens with appealing visuals and concise text.
2. Integrate the screens into the app’s launch sequence for new users.
3. Ensure the onboarding can be skipped or revisited from the settings menu.
4. Collect user feedback on the onboarding process to make improvements.

Expected Outcome:

New users will have a smooth introduction to CrazyCoder, leading to higher user satisfaction, better engagement, and increased retention rates.

.

We can mention options like latest first or earliest first kind of filters according to time stamps in the home section where all the contests are display for each coding platform.

By doing so, user will be able to sort the data according to which contest is latest upcoming or will be available in the next week or will it be today etc.

Please assign this to me under GSSoC, for making enhancement to the project.

👆 can add filter/ sorting options here.

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.

@Yash-Parsana where we can add I'd of 2 or more people we create a code room
Where we can select questions and the questions are show with the choosen
Platform and set a time . And after time period we can fetch the details.
And show the winner.

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.

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, Girlscript, good first issue etc.
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 pull request template for this repository. I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.

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

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

There is a spelling mistake in Footer .
It is written Keep Coding, Keep improwing but it should be Keep Coding, Keep improving.

Also there is a problem during signup/login. If someone open login/signup tab and then want to check other tab, there is no way to change it without going back.

Please look into these issues.

Thanks

You need to expose new route for gfg contests data.

Subtasks :
Find out if gfg provides api for contests data, otherwise you can use web scrapping to get data.

Make sure response must be in below format.

{
"name": "contest name",
"start_time": timestamp (integer) (eg 1715434800000) ,
"end_time": same format as start time ,
"status": "upcoming or ongoing"
},

Ask doubts in this thread, if you have any.

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

@Yash-Parsana
Issue:
The current implementation of the signup and signin functionality on our platform is encountering issues, preventing users from successfully registering and logging in. This hampers user experience and obstructs access to our services.
Proposed Solution:
I propose to address this issue by thoroughly investigating the root cause and implementing necessary fixes to ensure seamless signup and signin experiences for our users. Additionally, upon successful login, users should be redirected to the homepage to enhance user engagement and navigation.
I would like to work on this issue and contribute to the rapid solution. Apart from my expertise in session management debugging and user authentication, I have written both frontend and backend programs.

I can navbar in the project and also add links of social media so that user can go and follow you on social media.
Moreover i can improve navbar and can add dark mode feature

We can add feature of accessing the home page even on clicking Crazy Coder .Currently only on clicking on logo we can go to home page.

You need to expose new route for gfg profile data.

Subtasks :
Find out if gfg provides api for contests data, otherwise you can use web scrapping to get data.

Follow below response format.

{
"status": "success or failure",
"handle": string,
"over_all_coding_score": integer,
"total_problem_solved": integer,
"monthly_coding_score": integer,
"over_all_article_published": integer,
}

Ask doubts in this thread, if you have any.

I would like to add Scraping function to scrape the coding ninjas profile data

This repository has no Code of Conduct & Contribution.md file. any open-source project needs to set clear standards for behavior. It promotes inclusivity, prevents misconduct, fosters accountability, and maintains a positive environment.

Please assign this issue to me.

I would like to add a issue template for documentation issues 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.

I would like to work on this,
Redirecting to leetcode contests, could you please assign this to me?

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.

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

Alignment needs to be done for home page

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

You need to improve code quality by cleaning the code and adding proper formatting.

Subtasks:
Remove unnecessary white space comments and code.
Add proper formatting you may use linting tools.

Issue Description

Currently, when a user logs in or signs up, there is no feedback message indicating the success or failure of the action. To improve user experience, a toast message should be added to provide immediate feedback on these actions.

Task

• Add a toast message for successful login.
• Add a toast message for unsuccessful login, indicating the reason (e.g., incorrect password).
• Add a toast message for successful signup.
• Add a toast message for unsuccessful signup, indicating the reason (e.g., email already in use).

Expected Outcome

• Users should receive a toast message indicating the result of their login or signup attempt, enhancing the overall user experience by providing clear and immediate feedback.

Label and assignment

If you consider this a valid issue, please add the appropriate label indicating the level of the issue and assign it to me.

Hi there, I am Ram👋
Give me the website work so i can add some animations in the website
which looks good and attractive.
Librery to be used
-ityped.js
-aos.js

👋 Hi @Yash-Parsana
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

• #6
• #5
• #4
• #3
• #2

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.