Distributed Teams and Eclipse: Developing Over the Miles Brian Fitzpatrick Sr. Software Engineer, JBoss at Red Hat  March ...
Welcome! <ul><li>During this talk we're going to talk a bit about: </li></ul><ul><ul><li>Distributed Teams </li></ul></ul>...
But first a brief introduction... <ul><li>Who am I? </li></ul><ul><li>What's my story? </li></ul><ul><li>Why talk about di...
What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul>
What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed”...
What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed”...
What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed”...
My Old View of Distributed Teams...
My NEW View of Distributed Teams...
What about you? Do any of you work in similar environments?
More than Space... Time is the major factor <ul><li>On a regular basis, conversations with multiple times and places: </li...
Beyond Time and Space... What are the other issues?
Beyond Time... Other Issues #1 - Language <ul><li>English is a great common language for technical conversations </li></ul...
Other Issues #2 - Screen sharing and OS limitations <ul><li>Screencasts </li></ul><ul><li>Screen captures </li></ul><ul><l...
Other Issues #3 - Patches and Code Reviews <ul><li>Bug Tracking </li></ul><ul><li>Code Reviews </li></ul>
What about you? What other issues do you encounter?
What we do today... <ul><li>JIRA </li></ul><ul><li>Mailing Lists and E-mail </li></ul><ul><li>IRC Chat </li></ul><ul><li>W...
Where we run into issues... <ul><li>Sharing issues </li></ul><ul><li>Multiple locations </li></ul><ul><li>Inconsistent  </...
What tools we use (mostly)... <ul><li>Pidgin (IM/IRC)‏ </li></ul><ul><li>Camstasia/Jing (Screencasts)‏ </li></ul><ul><li>I...
Where Eclipse can help... <ul><li>ECF </li></ul><ul><li>Bug System Integration </li></ul><ul><li>Code Reviews in the Tooli...
Where Eclipse needs some help... <ul><li>Improved ECF Contact/Connection Management </li></ul><ul><li>Built-in logging and...
Opportunities Exist for Improvement and Innovation <ul><li>Integrated and standalone tools for distributed teams </li></ul...
Bottom Line <ul><li>We're all over the world. </li></ul><ul><li>Eclipse is a good environment for a single developer, but ...
Tips for Distributed Teams <ul><li>Face to Face Meetings – Annual or more often if possible </li></ul><ul><li>Important to...
Thanks! <ul><li>Enjoy the rest of the conference! </li></ul>
Upcoming SlideShare
Loading in …5
×

Distributed Teams and Eclipse

979 views

Published on

Since joining Red Hat, I've been working with an amazingly distributed team scattered around the world. I work with engineers in Beijing, Ireland, Switzerland, the United States, and more. To simplify communication we use JIRA, e-mail, IRC, and instant messenger clients to keep in touch and on task.

This talk focuses on some of the Eclipse technologies we use and others we've looked into using to help us deal with the distributed nature of our environment - from using the Eclipse IDE for development and the JIRA connector for Mylyn, to potentially using ECF to manage our various chat-like communication channels, and other technologies that came to light.

Brian Fitzpatrick (aka "Fitz") is a software engineer with Red Hat, Inc., who has contributed to the Data Tools Project (DTP) since its inception. Until recently, Brian's focus has mainly been on Eclipse tooling development for Sybase. This past year he joined Red Hat and has been working on cool SOA tooling. He hopes to continue helping out with DTP and elsewhere in Eclipse for the forseeable future. Currently he serves on the DTP PMC as well as as being the Team Lead for both the Connectivity and Enablement sub-projects within DTP.

Published in: Technology
  • Be the first to comment

Distributed Teams and Eclipse

  1. 1. Distributed Teams and Eclipse: Developing Over the Miles Brian Fitzpatrick Sr. Software Engineer, JBoss at Red Hat March 25, 2010
  2. 2. Welcome! <ul><li>During this talk we're going to talk a bit about: </li></ul><ul><ul><li>Distributed Teams </li></ul></ul><ul><ul><li>Our Scenario at Red Hat </li></ul></ul><ul><ul><li>Current solutions </li></ul></ul><ul><ul><li>And a few common sense tips... </li></ul></ul>
  3. 3. But first a brief introduction... <ul><li>Who am I? </li></ul><ul><li>What's my story? </li></ul><ul><li>Why talk about distributed teams? </li></ul>
  4. 4. What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul>
  5. 5. What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed” across time or space </li></ul>
  6. 6. What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed” across time or space </li></ul><ul><li>Typically focused on a single task or supporting a single product/project </li></ul>
  7. 7. What is a distributed team? <ul><li>Sometimes called “virtual” teams </li></ul><ul><li>Distributed times are “distributed” across time or space </li></ul><ul><li>Typically focused on a single task or supporting a single product/project </li></ul><ul><li>In theory anyway... </li></ul>
  8. 8. My Old View of Distributed Teams...
  9. 9. My NEW View of Distributed Teams...
  10. 10. What about you? Do any of you work in similar environments?
  11. 11. More than Space... Time is the major factor <ul><li>On a regular basis, conversations with multiple times and places: </li></ul><ul><ul><li>California [GMT -8] </li></ul></ul><ul><ul><li>Denver [GMT -7] </li></ul></ul><ul><ul><li>Atlanta [GMT -6] </li></ul></ul><ul><ul><li>Boston [GMT -5] </li></ul></ul><ul><ul><li>Ontario [GMT -5] </li></ul></ul><ul><ul><li>Dublin [GMT] </li></ul></ul><ul><ul><li>Switzerland [GMT +1] </li></ul></ul><ul><ul><li>Brno [GMT +1] </li></ul></ul><ul><ul><li>Minsk [GMT +2] </li></ul></ul><ul><ul><li>Beijing [GMT +8] </li></ul></ul><ul><ul><li>Tokyo [GMT +9] </li></ul></ul>
  12. 12. Beyond Time and Space... What are the other issues?
  13. 13. Beyond Time... Other Issues #1 - Language <ul><li>English is a great common language for technical conversations </li></ul><ul><li>But... it's not without its challenges. </li></ul><ul><li>Accents, grammatical differences, transmission issues </li></ul>
  14. 14. Other Issues #2 - Screen sharing and OS limitations <ul><li>Screencasts </li></ul><ul><li>Screen captures </li></ul><ul><li>Wikis, Documents, PDFs </li></ul>
  15. 15. Other Issues #3 - Patches and Code Reviews <ul><li>Bug Tracking </li></ul><ul><li>Code Reviews </li></ul>
  16. 16. What about you? What other issues do you encounter?
  17. 17. What we do today... <ul><li>JIRA </li></ul><ul><li>Mailing Lists and E-mail </li></ul><ul><li>IRC Chat </li></ul><ul><li>Wikis </li></ul><ul><li>Screencasts </li></ul><ul><li>Patches </li></ul><ul><li>Log files </li></ul><ul><li>Console Output... </li></ul>
  18. 18. Where we run into issues... <ul><li>Sharing issues </li></ul><ul><li>Multiple locations </li></ul><ul><li>Inconsistent </li></ul><ul><li>Reproducing issues </li></ul>
  19. 19. What tools we use (mostly)... <ul><li>Pidgin (IM/IRC)‏ </li></ul><ul><li>Camstasia/Jing (Screencasts)‏ </li></ul><ul><li>IE/Firefox/Chrome for Wiki editing </li></ul><ul><li>Eclipse JIRA & SVN integration </li></ul><ul><li>Mylyn </li></ul>
  20. 20. Where Eclipse can help... <ul><li>ECF </li></ul><ul><li>Bug System Integration </li></ul><ul><li>Code Reviews in the Tooling </li></ul><ul><li>More source code control options... </li></ul>
  21. 21. Where Eclipse needs some help... <ul><li>Improved ECF Contact/Connection Management </li></ul><ul><li>Built-in logging and log management for ECF chats </li></ul><ul><li>More screen capture options </li></ul><ul><li>Something like Google Buzz or Google Wave (See Bugzilla 280347) </li></ul>
  22. 22. Opportunities Exist for Improvement and Innovation <ul><li>Integrated and standalone tools for distributed teams </li></ul><ul><li>More resources for integrators trying to create such tools </li></ul><ul><li>People to test drive and provide feedback for early versions of such tools </li></ul>
  23. 23. Bottom Line <ul><li>We're all over the world. </li></ul><ul><li>Eclipse is a good environment for a single developer, but could be great with more multiple developer use cases. </li></ul><ul><li>And there are many opportunities to make things better. </li></ul>
  24. 24. Tips for Distributed Teams <ul><li>Face to Face Meetings – Annual or more often if possible </li></ul><ul><li>Important to have a “Glue” person to keep things on task </li></ul><ul><li>Settle on consistent technology </li></ul><ul><li>TDD and Continuous Integration </li></ul>
  25. 25. Thanks! <ul><li>Enjoy the rest of the conference! </li></ul>

×