Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Improve GitHub Contributor Selection and Cutoff Controls

Aperta
  • Qualcosa non va?
#78 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 8 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
github, javascript
Ambito
tooling

Direzione di ricerca

The payload names no files, so start by searching the codebase for where GitHub contributors are fetched, ranked by commit count and trimmed to a list. Then check how fork status is read from the GitHub API. Done means a written evaluation and recommendation covering the four acceptance criteria, with trade-offs for configurable limits, date or commit cutoffs, and fork-based history detection. This is design work, so ask the maintainers to confirm scope before writing any code.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Improve GitHub Contributor Selection and Cutoff Controls

Description

OpenCite uses GitHub contributor information to supplement citation metadata, but the current contributor ranking and selection process may not always surface the most relevant people for a project.

Commit counts do not necessarily reflect authorship or the significance of someone's contributions. This becomes especially challenging when a repository is forked, cloned, or adapted from an existing project, since its history may include contributors who worked on the original project rather than the current one.

For example, a researcher may build on an existing repository while retaining some of its history, or a repository may no longer be recognized by GitHub as a fork. In these cases, it may be difficult to distinguish contributors to the original project from those who contributed to the current project.

Questions to Investigate

  • How should OpenCite determine which GitHub contributors to surface, and how many should be shown by default?
  • Could users configure the number of contributors or apply a cutoff to the contribution history?
  • Would a date cutoff or specific commit hash help distinguish relevant contributors from inherited project history?
  • Can GitHub's fork metadata or commit history help identify where independent development began?
  • How should OpenCite handle repositories that originated from another project but are no longer recognized as forks?
  • Could OpenCite provide more context about why a contributor was surfaced, rather than relying primarily on commit counts?

Potential Direction

Investigate configurable contributor selection and history-based cutoffs, including whether repository fork information can help identify the relevant contribution history.

The goal is to give users more control over which contributors are surfaced as potential authors, particularly for projects that build on existing repositories, without assuming that commit activity alone determines authorship.

Acceptance Criteria

  • Evaluate the limitations of the current contributor ranking and selection behavior.
  • Investigate the feasibility of configurable contributor limits and date/commit cutoffs.
  • Assess whether fork metadata and commit history can help distinguish inherited contributions from project-specific contributions.
  • Recommend an approach for improving contributor selection, including relevant trade-offs.
Lingua principale
JavaScript
Stelle
0
Fork
0
Merge medio
10g 7h
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Imageomics/OpenCite

Tutte le issue di Imageomics/OpenCite

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.