[Meta] Ways to Contribute
@TimidRobot ya está trabajando en esto.
Desde el 3/3/2023.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Overview
⚠️ This meta-issue should not be worked on itself. Instead it is a place for me (@TimidRobot) to document ways to engage with this project.
First
- Read the documentation on Welcome — Creative Commons Open Source
Ways to Contribute
- Pull Requests (PRs)
- Contribute a PR for an existing issue per Contribution Guidelines — Creative Commons Open Source
- Help review PRs
- Issues
- Create a new issue recommending a data source that should be included. Include information like:
- quantity of records
- types of metadata available
- API documentation link
- API requirements and limitations
- Also see
sources.md- Sources | Openverse (any of the listed sources are potential sources for this project)
pre-automation/
- Create a new issue related to a single script or data source:
- Scripts should be using
.env(theskumar/python-dotenv) and notquery_secrets.pyor similar - Scripts mustn't be monolithic--they should be limited to a single phase (ex. query, process, report. See #22)
- Scripts must be designed to be run from the repository root via pipenv (ex.
pipenv run PATH/SCRIPT.PY)- Script should determine its own path and set appropriate global variables (ex.
DIR_ROOT,DIR_SCRIPT)
- Script should determine its own path and set appropriate global variables (ex.
- Scripts have a lot of duplication between them. Begin a shared library (remember to keep issues as small and descrete as possible--limit each issue/PR to a single script or data source).
- Scripts should be using retries with exponential backoff (ex. #2)
- Scripts should be using
- Create a new issue recommending a data source that should be included. Include information like:
Tips
Conventions and best practices
- Always sort data and lists (both implicit and explicit) naturally (Natural sort order - Wikipedia)
- Example: sorted constants
https://github.com/creativecommons/quantifying/blob/46dcd3ff9d66e172b87d79b097adcb9b348c6f2c/scripts/1-fetch/wikipedia_fetch.py#L32-L44 - Example: sorted data
from operator import itemgetterdata.sort(key=itemgetter("TOOL_IDENTIFIER", "CATEGORY_CODE"))
- Example: sorted constants
- #2
- #217
Plot process data
Any plots in phase 3-report should graph data without significantly modifying it. This means that development of phase 2-process and phase 3-report usually needs to be done at the same time.
Put another way, there should be a 1:1 relationship between phase 3-report plots and phase 2-process CSV files.
- Lenguaje dominante
- Python
- Estrellas
- 48
- Forks
- 74
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de creativecommons/quantifying
-
🏁 status: ready for work 💻 aspect: code 🛠 goal: fix help wanted 🟩 priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
creativecommons/quantifying#300 · 1 reacción ·
-
GCS free full web search ending 2026-12-31Quizá libre de nuevo @TimidRobot la tomó hace 143 días y no hay ningún pull request abierto. Abierto🏁 status: ready for work 💻 aspect: code 🔒 staff only 🛠 goal: fix 🟧 priority: high
creativecommons/quantifying#293 · 1 comentario · 1 asignado ·
-
Consolidate completion checkAbierto✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
creativecommons/quantifying#288 ·
-
Add a stacked horizontal bar plotQuizá libre de nuevo @oree-xx la tomó hace 240 días y no hay ningún pull request abierto. Abierto✨ goal: improvement 💻 aspect: code 🚦 status: awaiting triage 🟩 priority: low
creativecommons/quantifying#274 · 1 asignado ·
-
✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
creativecommons/quantifying#249 ·
Todos los issues de creativecommons/quantifying
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
solana-foundation/pay-kit#341 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nasa/python_cmr#123 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
EleutherAI/lm-evaluation-harness#4243 ·
Los mantenedores suelen responder en 1 día
-
area: dashboard bug perceived difficulty: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Nitjsefnie-Harness-Commons/daedalus#1179 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
cusp-ai-oss/tojax#17 ·