Sure, I know there is a feedback loop, but this is all about
(engineering) tradeoffs.
Two large concentrations of GF developers are in the West Coast of the
US and in India. Asynchronous mail-based coordination between those two
sites is very hard. A common symptom is the "nothing happens while I'm
awake; I went to sleep and whole conversations started, flamed and
ended". Or the "two-email exchanges, 10hrs pause, two email exchanges...".
It's different when everybody is in the US or even US+Europe (& geos in
close TZs, see [1]); then you can have a real conversation by email.
Blogs help with the TZ and synchronous/asynchonous issues, see [2], but
there is a limit to what can be done that way.
Jerome would know, but I think a key part of the engineering meeting is
to address these problems.
[1]
http://weblogs.java.net/blog/pelegri/archive/2003/08/distance_in_the.html
[2]
http://weblogs.java.net/blog/pelegri/archive/2006/02/time_zones_dont_1.html
Processes evolve to track communities needs. Over time we have added
wikis, twitters, ustream, etc. If you want to contribute we can figure
out how to make it easier for you to participate.
- eduard/o
Markus Karg wrote:
>> Apache only uses asynchronous - just email afaik - tools. Given their
>> goals that seems right. I think our use of both types of tools is the
>> right for our goals and our size... and the level of external
> interest.
>> If we had many external contributors wanting to participate in the
>> larger architectural decisions, we would lean more on synchronous
>> tools.
>
> Eduardo, ever thought about the fact that external participation is low,
> DUE TO the synchronous tools...?
>
> Regards
> Markus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>