There are three main solutions to this efficiency problem:

1) form intra-project teams (group of people working in a tightly coordinated fashion on one system)

2) form inter-project teams (group of people working in a loosely-coordinated fashion on multiple systems)

3) some combination of both 1 and 2

The key here is COORDINATION. Identify the stakeholders, discuss and plan with them, straighten out the specs and the interop, promote and test each other's implementations, make joint announcements, discuss problems, etc.

That's the sort of work @elsat has been doing and I'm trying to do, and I think there needs to be more focus on this. The NIPs repo is now too large in size and scope, to have everyone just hanging out in every discussion. We have to actually put effort in, to selecting where to hang out, now.

All the people working on relays: form a team

All the people working on books: form a team

All the people working on teleconferencing: form a team.

All the people working on AI: form a team.

All the people working on blogging: form a team.

And so on.