I’ve hinted that there are plenty of things left to do before. Especially in my forum posts. Repeatedly. So in this post I’ll list some tasks I think should be done. Not all of them are programming either.

• Proofread the documentation — most it was written after midnight so suggest clarifications too
• Write testcases to cover more parts of the code — testing the python bindings is important too so only some scripting knowledge needed to help out with it
• Add override file support to VIVTC (good entry level programming task)
• Convert the EEDI3 port to pure C (simple if you know the difference between C and C++)
• Port your favorite function/plugin from Avisynth — there’s something for everyone here
• Port your favorite Avisynth script
• Make a nice editor with preview — think AvsP
• Write some simple getting started examples or maybe a quick introduction for Avisynth users
• Add support for more output formats in vfw — clean up the output code too a bit
• Write a good implementation of edge detection filters — canny, sobel and friends for higher depths would be nice
• Your own ideas here