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

The project goal for outreachy

Aperta
  • Qualcosa non va?
#158 26 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@TimidRobot ci sta già lavorando.

Dal 8/10/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

✨ 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
Lingua principale
Python
Stelle
48
Fork
75
Merge medio
3h 55m
PR unite (30g)
6

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 creativecommons/quantifying

Tutte le issue di creativecommons/quantifying

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.