Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

The project goal for outreachy

Ouverte
  • Quelque chose ne va pas ?
#158 26 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@TimidRobot y travaille déjà.

Depuis le 8/10/2025.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

✨ goal: improvement ❓ talk: question 🏁 status: ready for work 📖 aspect: docs 🟨 priority: medium

Description

I have studied the documentation for the codebase written by the 2024 GSOC contributor and I quite undertand the workflow of the software especially when fetching data using APIs. While I was reading her article I saw that she talked about the pre automation code which I also see in the codebase. In this section of the codebase, there are code implementation for other data sources. She also mentioned that the pre automation code was written by previous developers, but I am guessing I have to focus on the the part she had worked on which is the lastest. I can find that part under the scripts section and it only has code for GCS and Github.

Looking at the project goal, we want to add new data sources to the project. My question is are we looking to add other sources like wikipedia, youtube ... like the ones in the pre automation code or entirely different data sources that I might have to make research on. Or start with the wikipedia, youtube, like the ones in the pre automation code.

Then when I run the 1-fetch script, am I in the dev environment? I also don't get any option to select, it just runs and I don't see any dataset. This is what it look like:

PS C:\Users\User\Documents\creative\quantifying> python scripts\1-fetch\gcs_fetch.py

2025-10-07 22:53:41,975 - INFO - gcs_fetch - Script execution started.
2025-10-07 22:53:41,975 - INFO - gcs_fetch - Parsing command-line options
2025-10-07 22:53:41,977 - INFO - shared - PATHS:
    repo: C:\Users\User\Documents\creative\quantifying
        dotenv:         .\.env
        data:           .\data
        data_1-fetch:   .\data\2025Q4\1-fetch
        data_2-process: .\data\2025Q4\2-process
        data_3-report:  .\data\2025Q4\3-report
        data_phase:     .\data\2025Q4\1-fetch
        data_2-process: .\data\2025Q4\2-process
        data_3-report:  .\data\2025Q4\3-report
        data_phase:     .\data\2025Q4\1-fetch
        data_quarter:   .\data\2025Q4
2025-10-07 22:53:41,977 - INFO - gcs_fetch - Getting Google Custom Search API Service.
2025-10-07 22:53:42,029 - INFO - gcs_fetch - Last completed plan index: 0
2025-10-07 22:53:42,057 - INFO - gcs_fetch - Beginning to fetch results from Google Custom Search (GCS) API
2025-10-07 22:53:42,057 - INFO - gcs_fetch - Query: index: 1, tool: CC BY 4.0
Langage dominant
Python
Étoiles
48
Forks
75
Merge moyen
3 h 55 min
PR mergées (30 j)
6

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de creativecommons/quantifying

Toutes les issues de creativecommons/quantifying

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.