Daily Log
Capture what you worked on, what you learned, and what comes next.
Explore the practical side
A closer look at the logs, journals, and templates that help turn small daily actions into meaningful long-term reflection.
Each year provides a ready-to-use structure for recording activities, learning, and progress. The system is organized into smaller, manageable parts that work together throughout the year.
logs/
βββ 2027/
βββ README.md
βββ calendar.md
βββ daily/
βββ weekly/
βββ monthly/
Each component serves a different purpose:
The yearly calendar provides a visual record of your journey. It is more than a contribution tracker: it captures different aspects of your growth.
A simple calendar can capture activities, milestones, learning moments, and personal progress.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 π | 2 π» | 3 | 4 β¨ | |||
| 5 β | 6 π₯ | 7 π» | 8 | 9 β | 10 | 11 |
| 12 | 13 π± | 14 | 15 π | 16 | 17 | 18 |
| 19 π» | 20 | 21 β | 22 | 23 π | 24 | 25 β¨ |
| 26 | 27 π₯ | 28 | 29 π» | 30 π± | 31 β |
Use indicators to capture what made a particular day or period meaningful. They are optional visual reminders, not measures of productivity or requirements for participation.
The journal section helps you think beyond daily activities and explore the kind of technical person you want to become.
journal/
βββ technical-to-be.md
βββ ai-and-technology.md
βββ technical-practice.md
These journals are living documents. Revisit and update them as your interests, knowledge, and goals evolve.
Templates provide lightweight starting points so you don't have to create a format every time. Use them as they are or adapt them to your needs.
templates/
βββ daily.md
βββ weekly.md
βββ monthly.md
βββ project.md
βββ experiment.md
Capture what you worked on, what you learned, and what comes next.
Review your contributions, challenges, and progress.
Look for patterns, recognize milestones, and consider future direction.
Document project goals, development, decisions, and lessons learned.
Record ideas, experiments, observations, and outcomes.
Choose a format that fits your time and the kind of contribution you want to record.
A structured format for capturing contributions, projects, and reflections.
# Daily Log (Starter)
## YYYY-MM-DD
- **Level:** 1 / 2 / 3
- **Project / Repo:** [Repo Name](URL)
- **Action:** Short description of contribution
- **PR / Issue / Link:** URL if applicable
- **Notes / Reflection:** Optional, 1β2 lines
For days when a short record is enough, use a single-line format.
# π
Daily Log (Simplified Version)
**Format:**
YYYY-MM-DD | Level | Project / Repo | Action |
PR/Issue Link (optional) | Notes (optional)
# August 5, 2026
- **Level:** 2
- **Project / Repo:** One Commit a Day
- **Action:** Improved the examples page.
- **PR / Issue / Link:** GitHub repository link
- **Notes / Reflection:** Made the framework easier
for new contributors to understand.
Both formats serve the same purpose: record meaningful progress without making documentation a burden.
For projects that span multiple days or months, a project log helps preserve development context, document progress, and capture lessons learned.
Project logs can be added to the weekly or monthly folder under the relevant year's logs directory.
# π οΈ Project Log
## Project Tracking
| Field | Notes |
| --- | --- |
| **Project** | |
| **Started** | |
| **Status** | |
| **Goal** | |
| **Current Focus** | |
| **Repository** | |
| **Links** | |
## Progress
| Date | What I Did | Notes |
| --- | --- | --- |
| YYYY-MM-DD | | |
| YYYY-MM-DD | | |
| YYYY-MM-DD | | |
## Learnings
| Date | What I Learned |
| --- | --- |
| YYYY-MM-DD | |
| YYYY-MM-DD | |
## Reflection
- What is/was going well?
- What do I want to try next?
One Commit a Day also includes practical resources to make participating in open source easier. Whether you're preparing your environment, making your first contribution, or exploring new learning opportunities, these guides provide useful starting points.
Set up Git and prepare your development environment for contributing.
Explore guide βFollow a practical workflow for making and submitting open-source contributions.
Explore guide βExplore the broader process of participating in open-source communities and projects.
Explore guide βDiscover learning materials and useful references for continued development.
Explore resources βBrowse the complete collection of practical guides and supporting materials.
Browse resources βThese components are designed to complement one another rather than create more work.
You don't need to use every template or complete every journal. Start with what is useful and let your system evolve naturally.
Take what works, adapt what doesn't, and build a practice that supports your journey.
Explore the Philosophy β