Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

The project goal for outreachy

Offen
  • Stimmt etwas nicht?
#158 26 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@TimidRobot arbeitet bereits daran.

Seit 08.10.2025.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

✨ 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
Vorherrschende Sprache
Python
Sterne
48
Forks
75
Ø Merge
3 Std. 55 Min.
Gemergte PRs (30 T.)
6

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus creativecommons/quantifying

Alle Issues in creativecommons/quantifying

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.