Segregate PRs based on project on leaderboard

[vansh-codes]

Segregating PRs by Project: A Potential Update

Concept:

• On the leaderboard, instead of listing all merged PRs together, segregate them based on the project or repository.
• Create individual tabs for each project a contributor has worked on. Within each tab, display the PRs merged for that specific project, making it easier to find and access contributions related to specific projects.

Impact:

• Improved Navigation: For contributors with a high number of PRs, locating specific PRs related to a project becomes easier with this implementation.
• Enhanced Clarity: Provides a clear overview of where contributions have been made, showcasing the diversity of a contributor’s work.
• Simplified Project Counting: Users and managers can quickly determine the number of projects a contributor has worked on by counting the listed projects, rather than searching through PRs manually.
• Easier Verification: In cases where there are discrepancies, such as PRs not updating correctly or contributors needing to reference old PRs, segregating PRs by project simplifies the verification process for Project Assistants (PAs) and Project Managers (PMs).

This update addresses challenges related to high PR volumes and helps streamline the management and verification of contributions.
I dont know how the backend scripts are working to update the leaderboard, but I believe if implemented this, it would be easier for contibutors as well as PM and would definitely enhance the user experience

[sanjay-kv]

https://gssoc.devxprite.tech/user/hars-21

something like this isnt it?

[vansh-codes]

Yes exactly! This one looks perfect💥

[Meetjain1]

https://gssoc.devxprite.tech/user/hars-21

something like this isnt it?

"It's looking great, @sanjay-kv sir, especially that activity graph at the bottom! I have a few suggestions that could further enhance the platform's functionality and efficiency:

1. Ranking Section: We could introduce a Ranking section that not only displays the current ranking but also tracks previous rankings with each leaderboard update. This feature would allow contributors to monitor their progress over time, motivating continuous improvement.

2. Issues Section: Adding an Issues section where contributors can view issues they've raised across different repositories would be valuable. This section could include columns for issue raised date, whether the issue is assigned, issue closed date, issue level assigned, whether a pull request was raised, and whether it was merged. Additionally, a repository-wise stats section for issues raised could be included. This would give contributors a clear overview of their issue management and progress.

3. Roman Numerals in Pull Requests Section: In the List of Pull Requests section, we could replace the repeated "Level 1, Level 2, Level 3" text with Roman numerals (I, II, III). Additionally, adding columns for PR raised date, assigned or not status, and the number of files changed would help in assessing whether the current assigned level of a PR is justified.

4. GitHub Link on Username Click: Implementing a feature where clicking on a contributor's username redirects to their GitHub profile would improve navigation and allow users to easily review the contributions of their peers.

These enhancements would significantly aid in evaluating contributors' overall performance, making it easier to detect any spammy behavior, and reducing the time required for review. By implementing these changes, we can create a more streamlined and transparent system for both contributors and reviewers."