1.6.0: monthly summaries in CSV. Nothing in your ledger files has to change.Changelog

Open source project
  • Overview
  • Install
  • Changelog
  • Community
  • Legal
  • Privacy
Repository

Community

Three people and an issue tracker

Ledgerline is maintained in spare time by three people who use it. It is MIT licensed, it takes no money, and it says no to most requests. What follows is all of the governance there is.

Maintainers

Who answers

  • A portrait of Rhona Elvert, parser and file format

    Rhona Elvert

    Parser and file format

    Wrote the first version for her own accounts in 2024. Has the veto on anything that changes how a ledger file is read.

  • A portrait of Marek Sandoval, reports and output

    Marek Sandoval

    Reports and output

    Maintains the four reports and the CSV writer. Answers most of what arrives on the mailing list.

  • A portrait of Ilse Bakenhus, builds and releases

    Ilse Bakenhus

    Builds and releases

    Signs the builds, keeps the Windows and arm64 machines running, and triages the tracker on Sundays.

Licence, contributing, conduct, decisions, money

Updated 2 September 20265 minutes

The licence

MIT. Use it at work, sell what you build with it, fork it, relicense your fork. Keep the copyright line and the permission notice in copies of the source, and accept that there is no warranty. The full text is in LICENSE at the root of the repository and it is twenty lines long.

Contributing

Open an issue before writing code. Most patches that arrive unannounced are refused, not because they are bad but because they add something the tool has decided not to do, and refusing work already done is worse for everybody than refusing an idea.

  • One change per pull request, with a test in tests/ when the change affects output.
  • make check passes before you open it.
  • Commit messages say what changed and why, in the imperative.
  • No new dependencies. A patch that adds one is refused on that ground alone.

Documentation fixes, fixture ledgers from real-world edge cases and reports of platforms where the build fails are more useful than features, and are merged faster.

Code of conduct

Be civil, assume the other person is trying, and keep the discussion about the code. Personal attacks, harassment and persistent bad faith get one warning and then a ban from the tracker and the chat room.

Reports go to conduct@example.com, which reaches two maintainers and nobody else. A report is answered within a week. The person reported is told what was reported and by whom only if the reporter agrees. Maintainers are held to the same rules and a report about a maintainer is handled by the other two.

How decisions are made

Three maintainers, one vote each, majority decides, and any of the three may block a change to the file format outright. Everything is decided in the open on the issue tracker; the chat room decides nothing.

Requests to add a feature are answered with yes or no, usually no, and the reasons are written in the issue rather than in a private message. Declined issues are kept open in a wontfix list so the same request can be pointed at an answer rather than argued again.

There is no governance document beyond these four paragraphs, and no plan to elect anybody.

Funding

There is none. Nobody is paid, there is no donation button, no sponsor tier, no company behind it and no foundation. The three of us maintain it in evenings we can spare, and in the weeks we cannot spare any, nothing happens and nobody is owed an explanation.

Costs are a domain name and a file host, about forty a year, split three ways. If that ever changes, this paragraph changes with it.

If you want to support the project, the useful currencies are a good bug report, a reproducible test case, and patience with an answer that takes a fortnight.

Where things happen

  • RepositorySource, LICENSE, CONTRIBUTING and the fixtures
  • Issue trackerBugs, proposals and the wontfix list
  • Good first issuesSmall, described, and nobody is holding them
  • Chat roomInformal, unlogged, decides nothing
  • Mailing listReleases and breaking changes, a week ahead
  • Package registrySigned builds and their checksums

Privately

Conduct reports and security

Anything that should not be in the open: a conduct report, or a bug that lets a ledger file do something it should not. Everything else belongs on the tracker, where other people can read the answer. Two maintainers see this; you get a reply within a week.

Open source project

Ledgerline turns a folder of plain-text ledger files into four reports. It does nothing else, and that is the point.

The tool

  • Overview
  • Install
  • Changelog

The project

  • Community
  • Issue tracker
  • Mailing list

Elsewhere

  • Repository
  • Package registry
  • Chat room

Legal

  • Legal notice
  • Privacy
Ledgerline is free software under the MIT licence. Copyright 2024-2026 the Ledgerline maintainers. No warranty of any kind.