[wsf-c-dev] APIs cannot be left to the last minute

[James Clark]

> However, I should also mention that we knew exactly one month back, who 
> is going to do what and I expected the API related discussions would 
> have been initiated by the relevant assignees well before this. (Even 
> now this is happening because I happen to pull them out - but the pull 
> model does not simply work and scale in this case)

In the future, maybe we should use Jira to manage the process.

For example, if nandika is assigned to do dynamic client support, then
there should be a corresponding issue in jira assigned to nandika.  The
assignee may them create some sub-issues (such as "Design the API").
Then the assignee should do an initial API design, attach it to the
relevant jira and send a message to this list requesting review.
Anybody who has comments should attach them to the jira.  The assignee
will then rev the API design until consensus is reached.  At that point
the documentation for the API should be checked in and the Jira closed.

James