The project goal for outreachy
@TimidRobot 已经在做这个了。
开始于 2025年10月8日。
评估
这个 Issue 还没有评估数据。
描述
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
- 主要语言
- Python
- 星标
- 48
- 派生
- 74
- 平均合并
- 3 小时 39 分钟
- 30 天内合并 PR
- 5
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
creativecommons/quantifying 的其他 Issue
-
🏁 status: ready for work 💻 aspect: code 🛠 goal: fix help wanted 🟩 priority: low
难度 2/5 1-3 小时 新手友好度 78/100
creativecommons/quantifying#300 · 1 条评论 · 1 个 reaction ·
-
GCS free full web search ending 2026-12-31可能重新可做 @TimidRobot 于 153 天前认领，目前没有进行中的 PR。 未关闭🏁 status: ready for work 💻 aspect: code 🔒 staff only 🛠 goal: fix 🟧 priority: high
creativecommons/quantifying#293 · 1 条评论 · 已指派 1 人 ·
-
✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
难度 4/5 3-5 天 新手友好度 38/100
creativecommons/quantifying#288 ·
-
Add a stacked horizontal bar plot可能重新可做 @oree-xx 于 250 天前认领，目前没有进行中的 PR。 未关闭✨ goal: improvement 💻 aspect: code 🚦 status: awaiting triage 🟩 priority: low
creativecommons/quantifying#274 · 已指派 1 人 ·
-
✨ goal: improvement 🏁 status: ready for work 💻 aspect: code help wanted 🟩 priority: low
难度 5/5 一周以上 新手友好度 35/100
creativecommons/quantifying#249 ·
查看 creativecommons/quantifying 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
Juniper/ansible-junos-stdlib#904 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
pollen-robotics/reachy_mini#1457 ·
维护者通常 1 天内回复
-
area:runtime good first issue
难度 2/5 1-3 小时 新手友好度 72/100
WATonomous/wato_f1tenth#39 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
FireDynamics/fdsreader#123 ·
-
难度 1/5 1 小时以内 新手友好度 85/100