Longer or more meetings?

john.loughney@nokia.com john.loughney@nokia.com
Mon, 9 Dec 2002 09:04:07 +0200


Hi Jari,

> Making people aware of how they are doing in terms of their goals is
> normally used for boosting productivity, not getting them fired or
> their WGs shut down... and we need to know better how we are doing
> and not just in terms of "we are not done yet". Early input from the
> IESG and IAB will save *their* time when they don't have to complain,
> discuss, and defend their position later. Version control tools could
> help authors and RFC editor to reduce the amount of time they spend
> figuring out changes. Base protocols that concentrate only on key
> features get through the faster. Interim meetings and teleconferences
> increase amount of work but don't take away anyone's possibility for
> list discussion or main meeting participation. Etc.

I think this would be a good start and probably help many things.  Also,
some tools to enable folks to file issues would be useful as well.  Many
WGs (MIP, AAA, etc.) have found a great deal of success by assigning =
tickets
to issues for WG to move more quickly on resolving open issues.

br,
John