It's good that there's plenty of support but there's not much organization yet. As I see it, there's 3 major branches of work to be done:

1) NES documentation
2) The emulator itself
3) Development tools ([dis]assembler, debugger, etc)

They shouldn't necessarily have to be worked on in any particular order, it would be best (IMHO) to establish procedures and structure things in a way such that people can immediately start contributing in areas they are most experienced in and not be waiting on someone else's work. If we don't see any results and people don't feel like they're contributing, they will lose interest quickly.

Documentation is probably the easiest part to get rolling. Make a decision on the format and work up a basic outline that we can start filling in with details, and it should take off from there.

The emulator.. I have mixed feelings about this. I'm not sure I agree about the original plan of starting completely from scratch. A lot of very good work has already been done between all the various emulators out there and shouldn't be wasted. Maybe pick one as a base and work from there?

Dev tools can be done individually at this point. Decide what tools we need and keep track of who's working on what, and leave things open so they can be integrated at some point in the future.

There's my $.02. Thoughts? Disagreements? Or just tell me to shut up and go away :)