Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Improve GitHub Contributor Selection and Cutoff Controls

Abierto
  • ¿Algo no está bien?
#78 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 8 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github, javascript
Área
tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
JavaScript
Estrellas
0
Forks
0
Merge medio
10 d 7 h
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Imageomics/OpenCite

Todos los issues de Imageomics/OpenCite

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.