LOL, if you're suggesting I use Google to find instances of people who don't know how to do something, I'll be here all day. Try "I can't connect to SQL Server" or "I can't put on my own pants".
I know there are pros and cons for both methods. There are also many benefits to WSPs, even for real-life, professional, high-impact web apps. And 8 out of 10 of the issues people raise with WSPs are due to a cronic unfamiliarity with aspnet_compiler.exe .
I'm using YAF in two projects now, which are WAPs. I don't want YAF to be the application. I want YAF to be a set of controls that I plop into my application (which can be a WAP if I choose, or not). YAF's current packaging makes this easy. I have its core assemblies, and I have the UI, which I can customize or throw out altogether if I wish. When I build my application into a WAP, YAF's pages are included in the build just like my own pages. YAF becomes part of my WAP.
There's no "migrating to a WAP" involved at all; just a ./forum/ directory in my app containing YAF's UI-- no different from any of the other files I'm building.
The key thing is that those who want YAF to be a WAP can build it that way right now. 100% of users can use it. If Jaben changes to a WAP model, then 40% of users can use it. Migrating from a WAP to a WSP is much more difficult.