Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE]: Centralized Weekly Progress Tracker & Contribution Matrix

Open
  • Is something wrong?
#130 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@AbiramiR-27 is already working on this.

Since Jul 30, 2026.

  • #131 by @AbiramiR-27 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, javascript
Domain
analytics, full-stack

Research direction

Start with FeatureWishlist.md, then inspect OrgExplorer's existing dashboard and GitHub API entry points. Clarify the date-range and week filters, contributor subsets, matrix metrics, and detail modal behavior before implementation; done means the described weekly tracker provides linked PR and issue details from the GitHub API.

Written by the indexing model from the issue text.

Description

enhancement
Feature and its Use Cases

Feature and its Use Cases
What is the feature?
An interactive "Weekly Progress Tracker" dashboard inside OrgExplorer. It will provide a matrix grid view showing a filtered subset of contributors along with a week-by-week chronological breakdown of their development activity (PRs opened, merged, closed, and issues raised).

How would users benefit from it?
Currently, organization mentors and GSoC contributors manually input and verify weekly contributions in a progress spreadsheet. Automating this within OrgExplorer will:

  1. Save significant administrative time for mentors and students alike.
  2. Provide a single, source-of-truth dashboard that reads directly from the GitHub API.
  3. Automatically compute weekly metrics without manual entry errors.

What scenarios would this feature address?

  • Mentor Evaluations: Mentors can easily check the week-by-week performance and velocity of all contributors in a single screen.
  • Student Milestone Checks: Contributors can track their weekly progress to ensure they are meeting their target timelines.
  • Sprint / Coding Window Audits: Allows checking activity patterns over standard weekly sprint intervals.
Additional Context

Proposed UI Design & Layout

  • Filters: Select date range, start week configuration, and filter contributor lists (with an option to save filtered subsets like "GSoC 2026 Cohort").
  • Matrix Grid:
    • Columns: Weeks (e.g., Week 1: May 18 - May 24, Week 2: May 25 - May 31).
    • Rows: Contributor usernames.
    • Cells: Aggregated badges showing active counts (e.g., 3 PRs / 1 Issue).
  • Details Modal: Clicking on any cell opens a modal detail pane showing the titles, status, and direct GitHub links of all PRs/Issues submitted in that specific week.

Project References
Addresses the open item outlined in
FeatureWishlist.md

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Dominant language
JavaScript
Stars
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.