I was just looking for something like this! I'll be using this very soon on another project of mine =D<br><br>As far as Drupal goes, I think that something like this would be particularly useful for core in a time like...oh,say....now. With code freeze ~38 hours away, efficiency is key to getting the patches from the exception list into core. If more than one person is working on a patch, it really makes sense to use something like this and have everyone looking at the same code at the same time so that it's not a constant string of upload to the issue queue, have a minor bug pointed out, reroll with bug fixes. Two sets of eyes on any of those patches at any one time would be awesome, and I think it would help get them ready to be committed.<br clear="all">
-----<br>Cameron Eagans<br>Owner, Black Storms Studios, LLC<br><a href="http://www.blackstormsstudios.com">http://www.blackstormsstudios.com</a><br>
<br><br><div class="gmail_quote">On Wed, Oct 14, 2009 at 10:17 AM, Ken Winters <span dir="ltr"><<a href="mailto:kwinters@coalmarch.com">kwinters@coalmarch.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I was thinking along the same lines. Most of the Drupal development that I've seen is either:<br>
<br>
A) Written by one person, then reviewed / improved asynchronously in the issue tracker rather than working at the same time<br>
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<br>
<br>
I use Eclipse for all of my PHP development (and know some others who do as well), but I probably won't ever use something like Saros unless I got a tele-working position somewhere.<br>
<br>
Some other module / core contributors might find it useful for those tasks, but it doesn't seem like a common need.<br><font color="#888888">
<br>
- Ken Winters</font><div><div></div><div class="h5"><br>
<br>
On Oct 14, 2009, at 12:08 PM, <a href="mailto:larry@garfieldtech.com" target="_blank">larry@garfieldtech.com</a> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just one point to clarify, there is no "Drupal Team" that could decide en masse to use a tool like this. Drupal is so distributed that we all have our own development workflows using a variety of tools, often in our basements rather than our offices (although there, too). So "Could use and Drupal benefit" is really the wrong question to ask.<br>
<br>
That said, I'm sure such a tool would prove useful to certain developers if they choose to use it.<br>
<br>
Is it language-dependent? Vis, most Eclipse devs work on Java, not PHP, so I am always wary of tools that may end up being centric to one particular language's development idiosyncrasies.<br>
<br>
--Larry Garfield<br>
<br>
Eike Starkmann wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear Drupal Team,<br>
My name is Eike Starkmann and I'm working working as part of the Saros Team at the Freie University in Berlin.<br>
Saros is an Eclipse plugin for collaborative text editing and distributed pair programming, i.e. it allows two or more developers to work together in real-time on the same files. It is similar to Gobby, SubEthaEdit or Google Docs but focuses on programming in Eclipse.<br>
It is my master thesis to figure out whether Saros is useful when developing Free/Open Source Software. I already was in contact with to other projects, for example Typo3 and got some good response.<br>
In my opinion Drupal can benefit from Saros because I think it brings many advantages to Open Source Software development:<br>
* Distributed Pair Programming is like a live peer review. This should help with finding good design, get rid of bugs, increase readability, etc.<br>
* Transferring knowledge should be easier to do when more than one person look at and work with the same code. This should also help to give new developers an introduction to the code.<br>
* In contrast to screen sharing, Saros only shares your actions inside of Eclipse with regards to the project you are both working on (think privacy) and you are still independent to explore the project on your own.<br>
Saros can be useful in the following contexts:<br>
* Working on complicated problems in the code<br>
* Performing code reviews<br>
* Debugging<br>
* Code presentation<br>
* Code sprints<br>
* Introducing new developers to the project<br>
* ...<br>
What do you think? Could you and Drupal benefit from doing pair programming using Saros?<br>
If you are interested in Saros but still curious about how it works please visit our website or feel free to contact me.<br>
I hope you will find Saros useful and give me feedback.<br>
Kind regards, Eike Starkmann<br>
Website: <a href="https://www.inf.fu-berlin.de/w/SE/DPP" target="_blank">https://www.inf.fu-berlin.de/w/SE/DPP</a><br>
Update Site: <a href="http://dpp.sf.net/update" target="_blank">http://dpp.sf.net/update</a><br>
Saros @ SF: <a href="http://sourceforge.net/projects/dpp/" target="_blank">http://sourceforge.net/projects/dpp/</a><br>
Programming Languages Supported by Saros : <a href="https://www.inf.fu-berlin.de/w/SE/DPPCompatiblePlugin" target="_blank">https://www.inf.fu-berlin.de/w/SE/DPPCompatiblePlugin</a><br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br>