Ken Winters wrote:
On Oct 15, 2009, at 9:17 AM, Eike Starkmann wrote:
Ken Winters wrote:
I was thinking along the same lines. Most of the Drupal development that I've seen is either:
A) Written by one person, then reviewed / improved asynchronously in the issue tracker rather than working at the same time B) Written by a team of people for a project in-house, in which case it would be the same as basically any other in-house PHP development
If you are working just like this perhaps Saros really doesn't make sense. But what is about the issue Cameron was thinking of? Working together with Saros and getting the patches in the core?
It might work in some cases, but I suspect it won't reach wide adoption. Time is very tight, so any delays messing with connection problems, etc. aren't really acceptable. So, both parties would need to have already used it in the past and frequently for it to be usable during crunch time.
That's true, you don't want people playing around with new tools while crunch time, but at some point you have to start, perhaps after the crunch time ;-) Greets, Eike -- Eike Starkmann This message is part of my Master thesis research. Feel free to contact my advisors in case of inappropriate behavior on my side: christopher.oezbek@fu-berlin.de and stephan.salinger@fu-berlin.de