The difference between contributing and taking

There's a line in open source between contributing and taking, and it's thinner than people think. Both can look identical in the git log. The difference shows up in behaviour — and maintainers can smell it in one interaction.

What taking looks like

Demand disguised as an issue. "This is broken, fix it urgently" — with no repro, no versions, no investigation. The tracker is a workshop, not a complaint desk.

Free-labour framing. Opening detailed "requests" that are really specs for the contributor to implement, then disappearing when asked a question.

Drive-by pressure. "Any update?" on a week-old issue from a volunteer who owes you nothing.

The vanish. Getting feedback on a PR, never responding, leaving the branch stale forever. The maintainer's review time evaporates.

What contributing looks like

The same requests, reshaped: investigate first, bring evidence, ask instead of demand, respond to questions, close your own loops. Take a bug from report to repro to fix. Answer someone else's question on the way out.

Why the line matters

Projects die of maintenance exhaustion more often than technical failure. The takers burn the fuel; the contributors refill it. Every project's tracker shows which kind of community it has — and every one of us chooses, interaction by interaction, which side we're adding to.