Built in the open, with people who keep real books
Questions, reviews and contributions all happen in public. The repository, the discussions and the release notes are on GitHub; announcements are mirrored on the project's social channels. Here is where to find each of them, and how to help the project reach a reviewed 1.0.
Where the conversation happens
Everything runs through the project's GitHub repository, with announcements mirrored on the social channels, so there is one source of truth and several ways to hear about it.
GitHub Discussions
Questions and answers, ideas, show and tell, announcements and accounting review each have their own category. Ask how to record something, propose an idea, or show how you run your books.
Issues
Bugs and planned work are tracked as public issues. A report of wrong behaviour starts here, and fixes land in public releases with the issue referenced, so you can see exactly which release closed it.
News feed
Release notes and project announcements are published on this site and as an RSS feed you can follow in any feed reader, without an account anywhere.
Help us reach a reviewed 1.0
Version 1.0.0 is released, but independent accounting review, independent security review and supervised pilots have not happened yet. If you can help with any of them, the maintainer wants to hear from you, and the work is credited in public.
Accounting reviewers
Review the chart of accounts packages, the journals and the financial reports for accounting correctness. Point out where the treatment of a transaction is wrong or unclear. Findings are tracked in public once they are safe to publish.
Security reviewers
Review authentication, sessions, database access and file handling on your own installation. Report problems privately through the security policy first, so a fix can land before details are public. Credit in the release notes is yours to take or decline.
Pilot businesses
Run your books through PHP Ledger alongside your current process for an agreed period. The maintainer supports the pilot, and the checkpoints are agreed in writing before it starts. A supervised month-end close is the goal.
Contribute
Code, documentation and bug reports are all contributions. Start with the guide, then pick an issue; accounting changes come with a worked example that can be checked by hand.
Good first issues
Small, well-scoped tasks to start on the code or the documentation.
OpenContributing guide
How to set up a development copy and send a pull request.
OpenCode of conduct
What is expected of everyone taking part in the project.
OpenSecurity policy
How to report a security problem privately, and what happens next.
OpenPublic issues and discussions use made-up figures only. Never post real figures from your books.
Stay informed
Three ways to follow the project, from release notes to the social channels, none of which need an account on this site.
Release notes
Every release is published on GitHub with a note on what changed and what it fixes, and the same note appears on the news page here.
Release notifications
Watch the repository on GitHub and choose Releases only, so you hear about a release without the rest of the activity.
Social channels
Announcements and shorter notes appear on the project's social accounts. Follow the one you already use.
Questions about taking part
Where do I ask a question?
GitHub Discussions is the place for questions, ideas and show-and-tell. It is public, so use made-up figures. The maintainer reads every thread, and answers that turn out to be generally useful become documentation.
Should I report a security problem in public?
No. Report it privately through the security policy first, so a fix can land before details are public. Credit in the release notes is yours to take or decline once the fix is out.
Do you accept pull requests?
Yes. Start with the contributing guide, pick a good first issue or open a discussion about a larger change, and send the pull request with a test. Accounting changes need a worked example with figures that can be checked by hand.