Skip to content

[FEATURE] Multi-Objective Ranking System for Issue Recommendations #82

@MadhuTiwari-345

Description

@MadhuTiwari-345

Feature Description

Currently, IssueMatch ranks recommended open source issues primarily based on semantic relevance. This feature proposes a Multi-Objective Ranking System that evaluates issues across multiple meaningful dimensions (technical fit, growth potential, project health, and mentorship support) to produce more intelligent, human-like recommendations.

The goal is to move from a single-score relevance model to a composite, configurable ranking engine that better aligns issues with a developer’s skills, experience level, and growth goals.

Problem Statement

Semantic similarity alone is insufficient for high-quality recommendations. Developers often face:

  • Issues that are technically relevant but too easy or too difficult

  • Recommendations from inactive or low-maintenance repositories

  • Issues without mentor availability, increasing drop-off

  • No differentiation between low-impact vs high-impact contributions

This leads to poor matching quality, reduced contributor confidence, and lower long-term engagement.

Proposed Solution

Implement a multi-objective scoring and ranking pipeline where each issue is evaluated on multiple normalized dimensions:

Ranking Dimensions

  1. Semantic Relevance
  • Cosine similarity between user skill embeddings and issue text embeddings (FAISS-based)
  1. Issue Difficulty vs User Skill Level
  • Match issue difficulty labels (easy/medium/hard) against user skill assessment and contribution history
  1. Repository Activity Score
  • Recent commits

  • Issue closure rate

  • Maintainer activity

  1. Mentor Availability
  • Boost issues with available mentors for the relevant tech stack
  1. Contribution Impact Score
  • Issue type (bug, core feature, security)

  • Repository popularity and reach

  • Estimated user impact

Scoring & Aggregation

  • Each dimension outputs a normalized score (0–1)

  • Final score is computed using weighted aggregation:

    FinalScore = Σ (weight_i × score_i)

Configuration & Experimentation

  • Weights should be admin-configurable

  • Support multiple ranking strategies (A/B testing ready)

  • Ranking strategy version stored per user for analytics

Component

Backend

Alternative Solutions

  • Hard rule-based filtering (rejected due to lack of flexibility)

  • Pure ML black-box ranking (rejected due to lack of explainability and control)

  • Client-side ranking (rejected for scalability and security reasons)

The proposed hybrid, modular backend scoring system provides the best balance between intelligence, transparency, and maintainability.

Additional Context

  • This feature lays the foundation for:

  • Explainable recommendations

  • Personalized learning roadmaps

  • Long-term contributor analytics

  • Strong alignment with IssueMatch’s mission of intelligent open source matchmaking

  • Ideal for SWoC 2026 contributors interested in system design, ML, and backend architecture

Metadata

Metadata

Labels

HardAdvanced level taskSWOCPart of Social Winter of CodeSWoC26Social Winter of Code 2026enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions