Getting help
PeckList is made by one person in their spare time, with help from anyone who joins in. There is no paid support; these are the places to ask, and what each is for.
| You want to | Go to |
|---|---|
| Fix something that is not working | First troubleshooting and the FAQ, then a bug report |
| Report a bug | A GitLab issue, as in reporting a bug |
| Ask for a feature | A feature request; check the roadmap first |
| Report a security problem | Privately, as a confidential issue: see the security policy. Never in public |
| Ask a question, show your setup | The community chat (below) |
| Help build it | Contributing and developing |
Community chat
Not open yet
A Discord server is planned for the 1.0 release, with a forum for support questions (one thread a question), channels for releases, the Android testers and people's setups. Until it opens, ask in a GitLab issue; questions are welcome there too.
What to expect
- Bug reports get a first answer within a few days, usually sooner. A report with the version and a debug dump gets fixed fastest.
- Fixes ship in the next release; only the latest release is supported, so the fix for an old version is to upgrade.
- Feature requests are read and labelled, and the ones that fit go on the roadmap. Not every one will: PeckList tries to stay small and easy to run.
Following releases
- The release page and the changelog.
- In the app: the server checks for releases twice a day and shows a notice
(
UPDATE_CHECK). - On GitLab: Notifications on the project page, set to Custom > New release.