Add FAQ entry for #164. Update contributing page.

docs/contributing.md

@@ -15,7 +15,6 @@ All submitted code should be linted with pylint, and follow the [Google Python S
 
 Note that PySceneDetect is released under the BSD 3-Clause license, and submitted code should comply with this license (see [License & Copyright Information](copyright.md) for details).
 
-
 ## <span class="fa fa-cogs"></span>&nbsp; Features That Need Help
 
 The following is a "wishlist" of features which PySceneDetect eventually should have, but does not currently due to lack of resources.  Anyone who is able to contribute in any capacity to these items is encouraged to do so by starting a dialogue by opening a new issue on Github as per above.
@@ -37,3 +36,5 @@ Ideally, this would be something like `-threshold=auto` as a default.
 ### Advanced Detection Strategies
 
 Research into advanced scene detection for content detection would be most useful, perhaps in terms of histogram analysis or edge detection.  This could be integrated into the existing `detect-content` command, or be a separate command.  The real blocker here is achieving reasonable performance utilizing the current software architecture.
+
+There are many open issues on the issue tracker that contain reference implementations contributed by various community members.  There are already several concepts which are proven to be viable candidates for production, but still require some degree optimization.

docs/faq.md

@@ -25,12 +25,10 @@ Unlike calling `pip install opencv-python`, the above commands will download and
 To enable video splitting support, you will also need to have `mkvmerge` or `ffmpeg` installed on your system. See the documentation on [Video Splitting Support](https://pyscenedetect.readthedocs.io/en/latest/examples/video-splitting/) after installation for details.
 
 
-
 #### How can I get around the error `Cannot split video due to too many scenes`?
 
 This error occurs on Windows platforms specifically when the number of detected scenes is too large.  This is because PySceneDetect internally invokes other commands, such as those used for the `split-video` command.
 
 You can get around this issue by simply invoking those tools manually, using a smaller sub-set of scenes (or splitting the scene list into multiple parts).  You can obtain a comma-separated list of timecodes by using the `list-scenes` command.
 
 See [Issue #164](https://github.com/Breakthrough/PySceneDetect/issues/164) for details, or if you have any further questions.
-