Also, many of these roles require expertise, but not in-depth technical knowledge about the project. These can conceivably be had on a consulting basis: platform expertise, interaction expertise.

The roles that require persistence, include: coordination, programming, documentation, and art. If you’re going to have these things, you really need someone who’s going to really carry it forward by themselves.

Many of these are similar to roles that one would find in a ProcessNetwork?. The only thing that I might add is that it could be useful to have some kind of PeerReviewTrustMetric system, that will allow users to build up a reputation as to their capability to fill the role in question. This can be potentially important if time is critical in a project or process.

However, this is no always the case of course. There could also potentially be times and situations where a complete novice could take on a task and learn while they go, for instance. This type of assessment should probably be done by the project initiators and coordinators. But then again, people might very well just dive in and do whatever they have their sites set on, and that could very well work, depending on the application. I like the idea of tying this to the InternetExchange.