DEV Community

zornade
zornade

Posted on Edited on

I will write about your open source project for free, and the link to your repo is a real link

Most open source projects don't fail at the code. They fail at being found.


You can spend a year on a tool that solves a real problem, write a decent README, publish a clean release — and still have twelve people know it exists. The repository is alive, the issues are answered, and nobody arrives. I've watched this happen to projects I use, and it happened to mine.

So I'm opening a channel: send me your open source project. If it convinces me, I write about it.

What you get

An article on zornade.com, in Italian, where I actually install the thing, run it, hit the rough edges, and write what works and what doesn't. The article links to your repository, your documentation and the people maintaining it.

Those links are normal links, not rel="nofollow". They pass value. That's deliberate: if I write that a project is worth looking at, the link should behave like the recommendation it is.

If I find a problem, I write it. If the problem is serious, I tell you before publishing so you can respond or fix it. You don't get copy approval, and I don't get a veto from you — that's the only way the piece is worth reading.

What I don't do

This matters more than what I offer:

  • No link selling. No packages, no rates, no invoice.
  • No link exchange. I don't want a link back. Not on your README, not on your site, not in a "partners" page.
  • No paid placement, no guest posts, no sponsored content.
  • No agreement to sign.

I've been on the other side of this: asking blogs and newsletters for a small space and being quoted a few hundred euros for it. I don't think that's how free content grows, and I'm not going to reproduce it in the other direction.

What I'm looking for

  • A declared free licence, OSI-approved or equivalent — MIT, Apache-2.0, GPL, AGPL, MPL. A repository without a licence is not open source, and I can't write that it is.
  • A public repository that is alive, with activity in the last twelve months. A project abandoned three years ago is hard to write about and useless to readers.
  • A real problem, explainable in one sentence without jargon.
  • Minimum documentation: a README that says how to install it and what it's for.

I'm especially interested in what's close to my own work — territorial data, GIS, maps, public APIs, Python, JavaScript, self-hosting, tools for technical offices and public administration — but that's not a requirement. If you maintain a synthesizer written by a musician, I'll read it gladly, as long as it's well kept.

What I won't publish: repositories without a licence, closed source, projects generated in bulk to farm search traffic, affiliate link collections, sponsored posts.

How to send it

Email hello@zornade.com with a subject starting with Open source, and include:

  • the repository link and the licence
  • two lines on what it does and who it's for, written like you'd explain it to a colleague
  • who maintains it — a name or an organisation, "it's just me" is fine
  • how old it is and how alive: last release, last meaningful commit
  • the docs site, if there is one
  • optionally: a similar project you don't like, and why yours is different. This helps me more than anything else in the list.

You can also send someone else's project — just tell the maintainer first, so they don't discover it from a published article.

How long it takes

Honest answer: not fast. Running software properly means setting up an environment, hitting the unclear parts, and understanding where the project struggles — and that's exactly the part worth writing about. Some projects take a week, some a month, and I'd rather publish nothing than publish a listicle.

I read everything. If I decide not to write about it, you get a short reply saying so, not silence.

Why I'm doing this

My own tools are open source: visura-api is AGPL-3.0 with 680 stars on GitHub, the MCP server is MIT, the QGIS plugin is GPL-2.0-or-later. I live off free software and I write about it.

There's also a self-interested reason, and I won't hide it: trying other people's software is the fastest way to see where the field is going, which problems are already solved and which aren't. And some of the people who read what I write are looking for exactly these tools.

The full call, with the same rules, is here in Italian. If you'd rather write to me in English, that's fine too.


If you've read this far and you maintain something, send it. The worst case is a short reply saying no.

Top comments (0)