The nice thing about this being a community project and not a corporate addendum is that it also retains the ability to evolve at any time. It would be nice to have it set in stone pre-anything gets coded, but as long as you have the basis, if you decide a few weeks in that something needs to be different, the ability is there to make changes.

I think you need to get some people coding. There's some ansy folk out there that were right into this project from the start that are starting to lose a lot of interest. Is there even a generic generic outline of what you guys want? It is an image gallery right? If you can't get people working on the core of the project, assign a few side projects getting them doing some functions you can tie into it at a later date.

Is SVN set up? Is there documentation on how you want the project members to access SVN?

Even if there's no outline of the project yet, do you have teams set up? Does everybody know what area they're going to be working in, or are they just 'coders' at this point?

Is there middle-management? You may want to make sure you assign some middle-management, otherwise this project could become wildly successfully and take over the open source community, and we don't want that. Form a committee or something.

In the words of the immortal Larry/Mater,

GIT-R-DONE!