I suggest pick one problem where the OWASP community can help and make a real difference, and focus on doing something about it. The number one problem that developers (including me) identified is the lack of secure development frameworks. It makes sense to me to start with what people have said is most important.
Jim Manico has some ideas on how OWASP can help with this, and knows about people who are working on making frameworks more secure. As Jim explained at the SANS Appsec conference this year, it's not necessary to secure every framework to make a difference. There are a small number of common frameworks; making them more safe to use will make a big difference - and hopefully create a snowball effect, as more people get involved and start understanding the problems and trying to solve them.
Rohit Sethi and his team are working on helping to helping to secure Django and he has some good ideas on what can be done on secure frameworks.
http://labs.securitycompass.com/index.php/2011/03/11/closing-the-secure-web-application-framework-manifesto-project/
I am sure there are other people doing good work like this.
My suggestion is to start by setting up something in the Builders section to track and publicize who is doing what to help make which frameworks secure by default - or at least safer to use.Create some buzz, see who is interested and who is already involved, and build some momentum. And show how OWASP is helping the community, attract more developers to the cause.
I am sure other people will have more concrete ideas of what to do next.
Jim Bird