Updated GSOC Ideas (markdown)

Alex Clark ☺ 2014-02-19 16:06:28 -08:00
parent 8d4ba2c634
commit 12704e8f9c

@ -8,7 +8,7 @@ _Suggested by Prashant Shrivastava, a potential GSOC participant who contacted A
Evaluate the status of Pillow's fork of the [PIL handbook](http://pillow.readthedocs.org/en/latest/guides.html) and provide improvements: better flow, modernization, more examples.
**Students**: should have some technical writing experience and be prepared to write [reStructuredText](http://sphinx-doc.org/rest.html). Experience with Python and PIL a plus.
**Students** should have some technical writing experience and be prepared to write [reStructuredText](http://sphinx-doc.org/rest.html). Experience with Python and PIL a plus.
**Mentor**: Alex Clark
@ -18,7 +18,7 @@ _Suggested by Eric Soroos, Pillow core developer_
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.
**Students**: should have C and Python programming experience. Experience with PIL a plus.
**Students** should have C and Python programming experience. Experience with PIL a plus.
**Mentor**: Eric Soroos
@ -28,9 +28,9 @@ _Suggested by Eric Soroos, Pillow core developer_
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.
**Students**: should have C and Python programming experience. Experience with PIL a plus.
**Students** should have C and Python programming experience. Experience with PIL a plus.
**Mentor**: Eric Soroos
**Mentor** Eric Soroos
## Coverage