stepping back from open source (but not leaving)

func Capacity(energy, lifeStuff int) int {
    return energy - lifeStuff*100 // math stopped working
}

i used to commit every single day.

from 2014 to may 2023 - nine years of daily commits. not “most days” - every single day. and not just one commit per day - between 2k and 8k commits per year. the green squares don’t lie. i was addicted.

then i stopped.

here’s why:

life happened. family. loved ones.

focus shifted. helping teammates. mentoring. delegating. building with people instead of alone.

open source shaped my career, my skills, my network. contributions beat resumes - i lived that. but i can’t keep up with everything.

what’s changing

most repos stay exactly as they are. open. forkable. discussions enabled.

the only difference: a disclaimer in the readme linking here. so you know what to expect.

i won’t archive much. archiving makes repos read-only and kills discussions. i want people to keep using them, learning from them.

the few cases where i’ll actually archive:

• when an active fork becomes the better option (i’ll point to it, close issues, then archive)
• when a project is truly “done” and only useful as reference code

for everything else: the repo stays alive, i just can’t promise fast responses.

what i’d love

co-maintainers. if you use something and want to keep it active, reach out. i’ll share commit access.

forks with backlinks. fork it, improve it, then PR a link to your fork in my readme. i’ll merge it. let people find the active versions. this is how forkability should work.

the long game

i’m not disappearing. some projects i’ll keep maintaining. some i’ll come back to later. coding for fun isn’t dead - just reprioritized.

if my repos helped you: fork them. improve them. your turn to build.

the code stays. the streak ends. life continues.