1. P2P Bug Tracking with SD
http://syncwith.us
Jesse Vincent
Best Practical
jesse@bestpractical.com

2. Hi!

3. I’m Jesse (obra)

4. clkao and I own a small
software company

5. (Best Practical)

6. I’ve been making issue
trackers since 1995

7. Our software
has some bugs

8. All software
has some bugs

9. (All software
is made of bugs)

10. I spend a lot of time
on airplanes...

11. ...and at conferences
with bad wifi

12. I need to keep track of
our bugs and our work

13. I’m the boss

14. I have no excuse for
not doing my work

15. I need to keep track of
our bugs and our work
even when I don’t have
Internet access

16. I’ve tried everything

17. Text files

18. Text files in
version control

19. IMAP Servers

20. RSS Feeds

21. Running RT on
my laptop

22. Keeping browsers open

23. Nothing was quite right

24. So we built SD

25. SD is a P2P Bug Tracker

26. It syncs the way you do

27. Clone a project’s bug
database over HTTP

28. Work offline

29. Pull from anyone you
work with

30. Publish your database
replica with rsync

31. Topology doesn’t
matter...

32. Don’t worry

33. It won’t break

34. SD learns how to
resolve each conflict...

35. based on how everyone
else resolves it

36. But you already have a
bug tracker?

37. No Problem!

38. SD can talk to foreign
bug trackers

39. RT, Hiveminder and
Trac work today

40. Google Code is next

41. Want to help with
Bugzilla, Github or
something else?

42. Time to get SD
up and running

43. SD is in Perl

44. SD uses 45-90
CPAN modules

46. Are you afraid?

47. Are you afraid?

48. Don’t be

49. You’ll need:
curl, perl 5.8, C compiler

50. You won’t need:
CPAN

51. You won’t need:
to answer prompts

52. You won’t need:
to fix dependencies

53. curl http://fsck.com/sd|perl
export PATH=$PATH:~/sd/bin

54. curl http://17h.local/sd|perl
export PATH=$PATH:~/sd/bin

55. Using SD (CLI)

56. Getting Started

57. SD Shell
$ sd

58. ./

59. Getting help
$ sd help

61. Creating a new project
$ sd init

63. Project settings
$ sd settings

65. Config file
$ sd config

67. Mirroring a project
$ sd clone

70. Publishing
$ sd publish

72. Pulling
$ sd pull

74. Create a bug
$ sd ticket create

76. Listing bugs
$ sd ticket list

79. Show a bug
$ sd ticket show

81. Update a bug
$ sd ticket update

85. Log
$ sd log

88. Git Integration
$ git sd

90. Using SD (Web)

91. Web? Isn’t SD an
offline tool?

92. Local microserver

94. Home

96. Search

98. Show a bug

100. Update a bug

102. History

104. Create a ticket

106. Working with others

107. Working with others
(Using SD)

108. Any topology

109. It doesn’t matter who
you sync with

110. You get all the updates
eventually

111. Cloning
$ sd clone

112. Make a copy of
someone else’s
database

113. Pulling
$ sd pull

114. Grab unseen changes
from another database
replica

115. Publishing
$ sd publish

116. Write out your
database replica for
sharing

117. (As SD changesets
and static HTML)

118. Hackathon mode
(using Bonjour)

119. Publish your replica
$ sd server

120. Pull updates
$ sd pull --local

121. Working with others
(Using other systems)

122. What other systems?

123. Sync with RT

124. Sync with Trac

125. Sync with Hiveminder

126. Sync with lots more...

127. (If you help write code)

128. Star topology

129. One SD node acts as a
gateway

130. Clone
$ sd clone

131. SD reverse engineers a
database history

132. Pull
$ sd pull

133. SD reverse engineers
partial database history

134. Push
$ sd push

135. SD figures out local
updates and sends
them upstream

136. What’s wrong with SD?

137. $ sd clone http://fsck.com/~jesse/sd-bugs

138. You don’t want to
install SD?

139. Point your browser at
http://fsck.com/~jesse/sd-bugs

140. What’s next?

141. Push to Trac

142. Google Code support

143. Indexing

144. GPG-signed changesets

145. Actually releasing 1.0

146. Questions?
http://syncwith.us
jesse@bestpractical.com

147. Bonus Material

148. Perl and Dependencies

149. SD is in Perl

150. SD uses CPAN
modules.

151. This is a blessing.

152. This is a curse.

153. CPAN
=
Dependency Hell

155. 123 Dependencies

156. ...one hour later:

158. 95 Dependencies

159. ...another hour later

161. 82 Dependencies

162. Where we are today:

164. 42 Dependencies

165. Only one needs a
compiler.

166. Shipwright gives us
one-command install

167. curl http://fsck.com/sd|perl
export PATH=$PATH:~/sd/bin

168. What’s that do?

169. $ head /Library/WebServer/Documents/sd
open (my $tar,'|tar xz 2>/dev/null');
while (<DATA>) {
print $tar $_;
}
close $tar;
exec(quot;cd sd-build; bin/shipwright-builder
--install-base=$ENV{HOME}/sdquot;);
__DATA__
?I?Isd-build.tar?<is?F???_1?䀌yH?quot;#‫{$ۿ‬U???H?eH
...

170. Then it installs some
Perl modules...

171. ...in order

172. Array-Compare Params-Util
Module-Pluggable
Carp-Assert Params-Validate
Net-DNS
Class-Accessor Path-Class
Sub-Exporter
Class-Data-Inheritable Proc-InvokeEditor
Test-Exception
Class-Inspector Scalar-List-Utils
Test-HTTP-Server-Simple
Class-Singleton String-BufferStack
Test-LongString
Clone Sub-Install
Test-MockObject
Compress-Raw-Bzip2 Sub-Uplevel
Test-MockTime
Compress-Raw-Zlib TermReadKey
Test-Script-Run
DBI Test-Harness
Test-Warn
Data-UUID Test-Simple
libwww-perl
Devel-StackTrace Text-CSV
Carp-Assert-More
Digest-SHA Time-Piece
DateTime-Locale
Digest-SHA1 Time-Progress
DateTime-TimeZone
Email-Address Tree-DAG_Node
HTTP-Response-Encoding
Error UNIVERSAL-can
Mouse
Exception-Class UNIVERSAL-isa
Net-Bonjour
Exporter-Lite URI
RT-Client-REST
ExtUtils-CBuilder XML-Atom-SimpleFeed
Template-Declare
ExtUtils-ParseXS YAML
WWW-Mechanize
File-Temp YAML-Syck
Any-Moose
HTML-Tagset boolean
DateTime
Hash-Merge version
DateTime-Format-Natural
IO-Compress DBD-SQLite
Net-Jifty
IPC-Run3 Data-OptList
Net-Trac
JSON Digest-HMAC
Path-Dispatcher
JSON-XS File-ShareDir
Test-WWW-Mechanize
Lingua-EN-Inflect HTML-Parser
- prophet.git
List-MoreUtils HTML-Tree
- sd.git
Module-Refresh HTTP-Server-Simple
Net-IP Module-Build

173. I’m never offline. Why
do I care about P2P bug
tracking?

174. ...about cloud
computing ☔

175. Living in the cloud
=
sharecropping )

176. (That’s bad)

177. The bad old days:

178. Pic of sharecroppers

179. You farmed land you
didn’t own...

180. ...with tools you
couldn’t really afford

181. You paid for it with
part of your harvest...

182. It sounded like a
pretty sweet deal...

183. ...until things got bad

184. (Things always got bad)

186. (Internet)

187. (Cloud)
(Internet)

188. In a bad year, you got
further in debt to
the land owner

190. So, what does this have
to do with software?

191. The (more recent)
bad old days:

192. pic of mainframes

193. You ran code you didn’t
own on hardware you
didn’t own

194. Things started to get
better in the 1980s

196. Pic of PCs

197. Users started to be
able to make choices
about computing...

198. They weren’t all rosy

199. Pic of BSOD

200. Sometimes new
versions of software
broke things...

201. ...leaving you locked in
to old versions

202. pic of win 31?

203. Things got ‘better’

204. rms
che

205. Now, things are getting
worse again...

207. What happens when
your favorite service
goes down?

208. pic of twitter being
down

209. ...or stops accepting
new signups?

211. ...or starts making
arbitrary choices about
what’s ‘safe’ content?

213. ...or breaks

215. You don’t own the
services you use

216. You probably don’t
even have a contract

217. When a service
provider cuts you off,
you lose

218. Not so secret shame:
I still need the cloud

219. My calendar lives at
google.com

221. I make a Web 2.0 todo
list service called
Hiveminder.com

222. pic of hiveminder

223. ☣ Using hosted apps
is going to hurt you! ☣

224. What about Google
Gears, Adobe Air, etc?

225. Great. now you can use
your word processer
while you’re offline!

226. Pic of wordperfect

227. Real offline apps
should not need servers

228. Real offline apps
should sync like you do