Updated GSOC Ideas (markdown)

Alex Clark ☺ 2014-02-14 01:57:54 -08:00
parent bcb65a3469
commit 99c7cd4481

@ -1,5 +1,7 @@
Welcome to the Pillow wiki for GSOC Ideas! Welcome to the Pillow wiki for GSOC Ideas!
If selected, we plan to focus on improving the following:
## Documentation ## Documentation
_From Prashant Shrivastava, a potential GSOC participant who contacted Alex Clark re: Pillow participating in GSOC:_ _From Prashant Shrivastava, a potential GSOC participant who contacted Alex Clark re: Pillow participating in GSOC:_
@ -10,6 +12,6 @@ _From Prashant Shrivastava, a potential GSOC participant who contacted Alex Clar
Investigate speeding up core operations by vectorizing core functionality. This could be a combination of autovectorization in the compiler, manual recoding of tight loops in vector form, or writing kernels for OpenCL. Investigate speeding up core operations by vectorizing core functionality. This could be a combination of autovectorization in the compiler, manual recoding of tight loops in vector form, or writing kernels for OpenCL.
## Robustness ## Stability
Pillow decodes a lot of image formats, some of which are safer and better specified than others. Experience with [other projects](http://googleonlinesecurity.blogspot.com/2014/01/ffmpeg-and-thousand-fixes.html) has shown that there are many bugs lurking in otherwise functional code. Running a large corpus of valid, invalid, or otherwise fuzzed images while recording and investigating errors and crashes should improve the robustness of Pillow. Pillow decodes a lot of image formats, some of which are safer and better specified than others. Experience with [other projects](http://googleonlinesecurity.blogspot.com/2014/01/ffmpeg-and-thousand-fixes.html) has shown that there are many bugs lurking in otherwise functional code. Running a large corpus of valid, invalid, or otherwise fuzzed images while recording and investigating errors and crashes should improve the robustness of Pillow.