For further development of the project, it would be great to have unit tests to ensure the project code does not break with further changes/improvements. The tests go under tests folder in 2.0 branch where Python 3+ porting is happening.
We should create man page documentation of some sort. Since we are not distributing an executable, other than example programs, there is some question as to how to name it.
I'm looking at ffmpeg's manpage documentation and it looks like they've created the following man pages, which follow the names of their libraries:
ffmpeg-scaler
ffmpeg-resample
ffmpeg-codecs
ffmpeg-devices
Build your own security cam and detect motion with a Raspberry Pi and the official camera board. This application saves 1080p videos of motion, has a live view and a webinterface to define areas which don't need to checked for motion.
A firmware application written in C++ using Arduino and Adafruit libraries. It sleeps in low power mode until, activated by the PIR motion sensor, it takes a picture. Images are posted to io.adafruit.com using the REST API.
For further development of the project, it would be great to have unit tests to ensure the project code does not break with further changes/improvements. The tests go under tests folder in 2.0 branch where Python 3+ porting is happening.