How to report issues to get a (reasonably) fast response

Scissors has been written by @tcr and is currently maintained by @cboulanger. We'd like Scissors to evolve and to get as many bugs squished as possible, but since we both don't have much time, we cannot guarantee to address your issues as fast as you would like.

Here are two ways you can ensure a speedy response:

1. Our all-time favourite: Fork the repo, address the issue in a separate branch, and submit a Pull Request. If you add a feature, do not forget to provide a test - that's a prerequisite for any new feature.
2. If you need us to look at the issue: create an virtual environment in which we can reproduce it easily.
   • For example, go to https://c9.io, create an account using your GitHub authentication, and create a public virtual machine ("workspace") with the "NodeJS" template.
   • In this workspace, if you use a Node version other than 6, install it using nvm install X (X being the major version number)
   • In the console, do sudo apt-get update && sudo apt-get install -y pdftk && npm install scissors
   • Set up a test case that shows your problem. You can upload problematic PDFs there.
   • Using the "Share" button on the top right, invite cboulanger to your workspace with "RW" privileges.
   • After the issue has been solved, you can delete the workspace.