-
Notifications
You must be signed in to change notification settings - Fork 148
Contact
Your problems or your questions may interest other people. Please, do not contact me (Jflesch) by private message. Please use the mailing-list or the bug tracker.
Beware: By default, Google groups set your subscription to "no email".
You can sign up via the web at: *https://groups.google.com/forum/#!forum/paperwork-gui/join
To subscribe without a Google account, send an email to [email protected]
This is the place to go if:
- you have any questions regarding Paperwork, Pyocr, or Pyinsane, etc
- you want to discuss a new functionality for Paperwork, Pyocr or Pyinsane, etc
- stay up-to-date regarding major changes on Paperwork (dependencies, etc)
- get the release announcements first hand
Please write your emails in English.
- Paperwork's bug tracker
- Paperwork-backend's bug tracker: Please use Paperwork's bug tracker
- Pyinsane's bug tracker
- PyOcr's bug tracker
- Libpillowfight's bug tracker
This is the place to go if Paperwork (or Pyinsane or PyOcr) doesn't act as expected. This includes:
- Uncatched exceptions
- Crashes
- Unexpected or confusing behaviors from the GUI
- Feature requests (please make it as specific, clear and detailed as possible)
If you don't know which bug tracker is the most appropriate, please use Paperwork's bug tracker. I'll create others tickets in other bug trackers if required.
Please write bug reports or feature requests in English.
Here is some information usually useful in a good bug report:
- How to reproduce the problem ?
- What is the expected behavior ?
- What behavior did you get ?
- What version of Paperwork are you using ? (stable / testing / unstable)
- When run in a terminal, is there any uncatched Python exception raised ?
- How did you install Paperwork ? (virtualenv / setup.py / distribution package)
- What GNU/Linux distribution are you using ?
Additionally, the output of Paperwork in a terminal may be useful.