- 2 Posts
- 4 Comments
mietkiewski_dev@lemmy.mlOPto
Open Source@lemmy.ml•Closed‑source vs source‑available vs open‑source — which model makes the most sense for small tools?
1·4 hours agoI’m not trying to prove which license is better — too many variables, like you said. I’m just testing how different models change user behavior: who clicks, who downloads, who ignores. It’s more about distribution patterns than software quality.
mietkiewski_dev@lemmy.mlOPto
Open Source@lemmy.ml•Closed‑source vs source‑available vs open‑source — which model makes the most sense for small tools?
2·1 day agoFor this project I’m mainly testing distribution models. My only restriction is redistribution — people can read and modify the code for personal use. I’m also cautious about someone copying or commercializing it, so this is mostly a learning exercise for me.
mietkiewski_dev@lemmy.mlOPto
Open Source@lemmy.ml•Closed‑source vs source‑available vs open‑source — which model makes the most sense for small tools?
1·1 day agoSource‑available still lets people read and modify the code for personal use — they just can’t redistribute it. For me that’s a reasonable model for small tools, even if there’s always a risk someone will copy it. This project is mainly a distribution experiment.

Right — that’s why I’m calling it source‑available. I’m mainly testing user behavior around distribution, not trying to define what’s ‘open’ or not.