A look at why geographically dispersed software development teams aren't using Free, Libre, and Open Source Software [FLOSS] for their collaboration needs - and what FLOSS developers can learn from it.

1. How OSS Failed
Dispersed Teams

2. Or...

3. Writing OSS that People Will Actually Use

4. Who I Am

5. Why you should care

6. Why you should care

7. I Love FLOSS

8. GNU/Linux Hippie

9. Emacs Fiend

10. Corporate Infiltrator

11. Creator/Contributor

12. http://github.com/avdi

13. Dispersed Teams

14. Geographically separated, working together

15. Sound Familiar?

16. We practically invented the dispersed team

17. Developers love FLOSS tools

18. FLOSS: It's not just cheaper, it's better

19. ...right?

20. So I have this website

21. http://wideteams.com

22. Interviews

23. Dispersed teams aren't using FLOSS (much)

24. Why not?

25. The remote toolkit

26. ●Voice/Video Chat
●Chat Rooms
●Screen Sharing
●Version Control

27. Voice/Video Chat

28. SIP/H.323

29. 1. Choose a
Protocol

30. 2. Host a Server

31. 3. Find clients

32. 4. Set up accounts

33. 5. Tell everyone how to
connect

34. 6. Maintain it

35. Skype

36. 1. Download it

37. 2. Create accounts

38. 3. Log in

39. (4. Complain about how annoying Skype is)

40. Chat Rooms

41. IRC/Jabber

42. 1. Host a server

43. 2. Set up a log
server

44. 4. Set up accounts

45. 5. Get everyone
connected

46. 6. Maintain It

47. Campfire

48. 1. Set up account

49. 2. Define Users

50. 3. Send a link

51. Screen Sharing

52. VNC

53. 1. Get [compatible] software

54. 2. Punch hole in firewall

55. 3. Figure out SSH tunneling

56. 4. Look up your IP address

57. 5. Connect

58. 6. Public wifi? Forget it.

59. TeamViewer

60. 1. Download it

61. 1. Download it

62. 2. Start it

63. 3. Send session ID

64. 4. Connect

65. Version Control

66. FLOSS!

67. GIT

68. ...hosted on GitHub

69. Most teams do centralized
version control

70. No one wants to host their own

71. Observations

72. Social Software

73. “How will it help to get
your users laid?” - JWZ

74. A Means to an End

75. Connecting people

76. The Distributed Mindset

77. Centralization is underrated

78. Jabber: Gtalk, GIT: GitHub

79. Everyone else is there

80. Small Teams

81. No DevOps

82. Lessons

83. 1. Do one thing well easily

85. 2. Lower the Barrier to Entry

86. Do the Web UI First

87. Services, not protocols

88. Clients will follow

89. 3. Release Early

90. But you knew that

91. Diaspora

92. 4. Host it

93. One Well-Known Host

94. Leave the distributed
architecture for 2.0

95. ...or forget it entirely

96. 5. Sell it

97. You need to pay for hosting

98. You need good feedback

99. You need an incentive

100. Your users need confidence

101. Projects

102. talkerapp.com

103. teambox.com

104. EtherPad

105. dimdim.com

106. Google Wave

107. Conclusion

108. We need more OSS

109. Fix It!

110. Thank You

111. Avdi Grimm
avdi@avdi.org
Twitter: @avdi / @wideteams
http://avdi.org/devblog
http://wideteams.com
http://shiprise.net