6

I’ve been experimenting with building very small personal tools to help myself stay focused. Recently I wrote a minimal terminal‑based Pomodoro timer because I was struggling to start my side projects and wanted something simple that just works.

While building it, I realized I also need to learn how to distribute small projects properly. Right now I’m trying a simple approach: closed‑source, pay‑what‑you‑want, no DRM, and users just get the right to use the tool.

Since I’m still learning how licensing, expectations and “fairness” work for tiny solo projects, I’m curious how other developers see this model. Is this a reasonable way to distribute small tools? What would you expect as a user or developer?

For context, here’s the project I’m experimenting with.

GitHub: https://github.com/Mietkiewski/MPomidoro

you are viewing a single comment's thread
view the rest of the comments
[-] mietkiewski_dev@lemmy.ml 1 points 7 hours ago

For me the closed‑source vs source‑available vs open-source choice is mainly about learning distribution models, not about AI‑authored code. I wrote and understand the code — I just wanted to test a model that allows distribution and PWYW, which open‑source doesn’t really support.

this post was submitted on 29 Apr 2026
6 points (100.0% liked)

General Programming Discussion

9880 readers
2 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 7 years ago
MODERATORS