🫶🏽 One Commitment a Day

This repository tracks my commitment to contributing to open source projects every day for one year, and also a template repository for other developers to help contribute consistently.

A “contribution” is defined as any action that helps move a project forward or deepens my involvement — including code, documentation, issue, discussions, reviews, or learning-related engagement in public repositories.

The goal is not perfection, but consistency.

By showing up daily, even in small ways, I aim to:

• build real experience in open source collaboration
• develop technical and communication skills
• grow into a long-term contributor within the community

Each entry below represents one step in that journey.

📜 Contribution Level and Definition

Level 1: Lightweight (On busy days)

• Comment on an Issue (ask, clarify, suggest)
• Review someone’s PR (even small feedback)
• Improve README / fix typo
• Work on private repositories

Level 2: Standard (My default target)

• Submit an Issue
• Prepare or edit a PR for submission
• Submit a PR (bug fix, doc improvement)
• Reproduce a bug + document it
• Add example usage / test case
• Improve documentation clarity
• Work on my own repository + Contribute 5+ times

Level 3: High Value (1-2 times/week)

• Implement a new feature or significant improvement
• Refactor a complex code section
• Write a detailed tutorial or guide
• Lead a discussion or proposal for a new design or feature
• Create and setup a new repository

👉 Rule:

Every day = at least Level 1

1-2 days a week = Level 2

1-2 days a month = Level 3

🪫 Recovery Mode / Fallback

Sometime life gets busy (work, travel, unexpected events). To maintain consistency without burnout, a fallback option is installed.

Recovery Mode (Level 1 — Last Resort Only):

• Read an issue or PR and leave a thoughtful comment
• Review a repository’s structure or contribution guidelines
• Read code and write at least one insight in the daily log
• Star a useful project and explore it briefly
• (Optional) Work on a private repository

Rules:

• Use only when time or energy is very limited
• Still log the activity (non-negotiable)

🧠 Daily Execution System

Here is a simple daily loop:

⏰ 30–60 min routine

1. Open a developer platform, such as GitHub
2. Pick ONE:
   • continue yesterday's work
   • find a small issue or documentation
3. Do something (Level 1-3)
4. Log it (non-negotiable)

That's all.

🎯 Strategy for High-Level Open Source Project Acceptance

The goal is to be accepted into competitive open source projects/programs (e.g. GSoC-level) by becoming a consistent and trusted contributor.

Phase 1 — Explore (0–2 months)

• Contribute to multiple projects
• Identify projects with active maintainers and clear contribution paths
• Find areas where I can understand and add value

Phase 2 — Focus (2–6 months)

• Choose 1–2 main projects
• Contribute consistently (issues, PRs, discussions)
• Build familiarity with the codebase and community

Phase 3 — Contribute Deeply (6–12 months)

• Take on more complex issues
• Support other contributors
• Propose improvements or features

Goal: Move from a one-time contributor → a recognized and reliable contributor within a project.

🔥 Key Mindset Shift

Most people think:

I need to contribute something big and valuable.

But the real open source world is about:

I need to be consistently present.

Because in open source:

• Consistency builds reputation over time.
• Repeated interaction builds trust with maintainers.
• Engagement and presence matter as much as code.
• Long-term involvement predicts becoming a core contributor.