What I (we) experienced during the development of !!HELP!! over 6 years now is that it is essential to have some kind of code control / versioning system and a common development server.
We havn't had either a control system nor a common server. And we ended up in inconsitency ...
I do not know, how many mails with a new version of the template were sent back and forth. Countless. So a common development server is first on my whishlist.

And we really should encourage even new developers with little skill to contribute even to bigger projects like !!HELP!!. Even a small code snippet could help to make the project better.
Sometimes they provide a much easier solution to a certain problem than a "senior" developer.
We can learn from them what we might have forgotten over the years.

+1 on the shared development server. Also the automatic certification of development IDs to go along with that server would be nice.

Something not on your list but may fall within the developers directory would be a way to ask for help. While all of these things are nice, if a developer can't get some help what's the point?

As for the set of services (Forum, wiki, build system, project blog), How about including ideaJam on a project level? With the upcoming release of the API that should be possible. Also, I think that these services would start bringing OpenNTF on par with something like SourceForge.

Keep up the good work

Most of my needs seem to be nailed in the presentation. In order of importance to me...

1) Shared development server
2) Mechanisms to manage IDs of project participation and access to databases etc.
3) Code control and version control
4) Forum (e.g. Connections) to collaborate on project
5) IdeaJam space for project to receive feedback on ideas for project

Finally> I would suggest we should be at the forefront of the evolution of Project Vulcan and use the concepts it encapsulates to make openNTF the true "Kick arse" open source development community. i.e. OpenNTF Knows how to do collaborative development.

As an Admin my role for Openntf is about recommending other people's snippets of code or solutions as the case may warrant.
However, since the apps are not mine many times I have become confused by the apps documentation (if there was any) on what needs to be done to make the app work.
Signing it is but a small piece of the puzzle.
Does it need agents enabled? Different access for roles or users?
New document buttons that do not work because of some other setting I was unaware.
Those are some basic items I have found.

All the owners of the apps have been excellent at supporting their apps when we needed questions or issues resolved but still documentation that makes sense to a non-developer helps too, especially if there is anything on the design side we must change or update.

What makes a project usable is if it will work and meet a requirement.

Slide 7 the top is a given and everyone should be 100% on board with that.

What do we need, just documentation, not just how to get it installed or running but how it is built in case we want to change anything. Like what should we NEVER touch for instance.

In general I would give it to a developer to edit it but in some clients with little or no lotus knowledge they want to know some documentation exists for compliance and DRP situations.

I believe some of the documentation issues have been more enforced with recent projects and thanks for that it does help a lot.

I'd like to see every project online in a way that we can demo it or at least see how it will act.