1
00:00:00,000 --> 00:00:06,000
This podcast is brought to you by PodShow and GoDaddy.

2
00:00:06,000 --> 00:00:09,000
Want killer content with a badass domain name?

3
00:00:09,000 --> 00:00:14,000
This show will give you a special code to get great discounts at GoDaddy.com.

4
00:00:16,000 --> 00:00:19,000
Hey everybody, how you doing? Welcome to Devcast number four.

5
00:00:19,000 --> 00:00:24,000
My name's Adam, coming to you from the Curry Cottage in Guilford.

6
00:00:24,000 --> 00:00:28,000
It's been, uh, crikey. It's been almost two weeks now since the last Devcast

7
00:00:28,000 --> 00:00:30,000
and there are reasons for it.

8
00:00:30,000 --> 00:00:33,000
I can already, you know, see that there's grumblings and people not understanding

9
00:00:33,000 --> 00:00:36,000
why the radio silence and a lot has been going on.

10
00:00:36,000 --> 00:00:39,000
And it's really, it's actually kind of stupid stuff,

11
00:00:39,000 --> 00:00:42,000
a little bit beyond our control because we're so strapped with everything,

12
00:00:42,000 --> 00:00:44,000
but a couple of things went wrong.

13
00:00:44,000 --> 00:00:47,000
And it all has to do with, well, it's really all about the setup

14
00:00:47,000 --> 00:00:49,000
and we have a couple of comments that came in

15
00:00:49,000 --> 00:00:51,000
for the Devcast specifically.

16
00:00:51,000 --> 00:00:53,000
Let me start with this first one.

17
00:00:53,000 --> 00:00:55,000
It's kind of relative to what we're going to talk about,

18
00:00:55,000 --> 00:00:58,000
what the delay has been and how we're solving all that.

19
00:00:58,000 --> 00:01:01,000
Hi Adam, I was just listening to daily source code 367

20
00:01:01,000 --> 00:01:04,000
and you were talking about the developer APIs

21
00:01:04,000 --> 00:01:06,000
and a source control repository that you guys were putting up

22
00:01:06,000 --> 00:01:09,000
in order to share it with the developers.

23
00:01:09,000 --> 00:01:12,000
And this statement kind of concerned me.

24
00:01:12,000 --> 00:01:18,000
We're setting up a CVS, which is a revision system.

25
00:01:18,000 --> 00:01:22,000
CVS is a revision system, but it's a little out of date

26
00:01:22,000 --> 00:01:24,000
and you're going to find a lot of the maintenance

27
00:01:24,000 --> 00:01:26,000
of the repository to be rather difficult.

28
00:01:26,000 --> 00:01:30,000
Many large open source software projects such as KDE,

29
00:01:30,000 --> 00:01:34,000
GCC, Python and Samba are all moving to Subversion,

30
00:01:34,000 --> 00:01:37,000
which is a revision control system that was written

31
00:01:37,000 --> 00:01:39,000
specifically to replace CVS.

32
00:01:39,000 --> 00:01:43,000
And it supports a lot of things that CVS just doesn't support,

33
00:01:43,000 --> 00:01:46,000
like moving things around, easier authentication,

34
00:01:46,000 --> 00:01:49,000
running your source repository through Apache.

35
00:01:49,000 --> 00:01:51,000
A lot of people are moving toward this

36
00:01:51,000 --> 00:01:54,000
revision control system, so I know I'm geeking out

37
00:01:54,000 --> 00:01:56,000
a little bit here, but I just wanted to help out

38
00:01:56,000 --> 00:01:59,000
and don't want to see you actually bring up

39
00:01:59,000 --> 00:02:01,000
all your source code on such an antiquated system.

40
00:02:01,000 --> 00:02:03,000
I hope this helps. Thanks.

41
00:02:03,000 --> 00:02:05,000
Yeah, thank you very much.

42
00:02:05,000 --> 00:02:07,000
I know exactly what you're talking about.

43
00:02:07,000 --> 00:02:09,000
I'm not familiar with what you're talking about.

44
00:02:09,000 --> 00:02:11,000
I do get it and I do appreciate it

45
00:02:11,000 --> 00:02:13,000
and I know that the rest of the development team

46
00:02:13,000 --> 00:02:15,000
is listening to this.

47
00:02:15,000 --> 00:02:17,000
Well, what we decided to do actually,

48
00:02:17,000 --> 00:02:19,000
to make things what we thought would be really easy

49
00:02:19,000 --> 00:02:21,000
was to just bring up a SourceForge project

50
00:02:21,000 --> 00:02:23,000
and check all of the code in there

51
00:02:23,000 --> 00:02:25,000
because, you know, so much stuff is taking care

52
00:02:25,000 --> 00:02:27,000
of people already know the interface.

53
00:02:27,000 --> 00:02:29,000
And I think actually one of the names you mentioned

54
00:02:29,000 --> 00:02:31,000
is something that we're setting up.

55
00:02:31,000 --> 00:02:33,000
But what I did is, the problem has been

56
00:02:33,000 --> 00:02:35,000
that SourceForge, I think they had a major meltdown

57
00:02:35,000 --> 00:02:37,000
on their infrastructure.

58
00:02:37,000 --> 00:02:39,000
They haven't been able to start new projects.

59
00:02:39,000 --> 00:02:41,000
They haven't been able to create stuff for people.

60
00:02:41,000 --> 00:02:43,000
So we're somewhere in their queue waiting,

61
00:02:43,000 --> 00:02:45,000
literally waiting.

62
00:02:45,000 --> 00:02:47,000
I'm also finalizing the SDK

63
00:02:47,000 --> 00:02:49,000
and I asked Andrew Gromit

64
00:02:49,000 --> 00:02:51,000
to send me an audio comment with an update.

65
00:02:51,000 --> 00:02:53,000
Hi, Adam. It's Andrew here at PodShow HQ.

66
00:02:53,000 --> 00:02:55,000
I just wanted to give you an update

67
00:02:55,000 --> 00:02:57,000
on the modules SDK.

68
00:02:57,000 --> 00:02:59,000
Some great news.

69
00:02:59,000 --> 00:03:01,000
We've released a preview copy of the SDK

70
00:03:01,000 --> 00:03:03,000
to the first lucky developers

71
00:03:03,000 --> 00:03:05,000
and are starting to collect feedback.

72
00:03:05,000 --> 00:03:07,000
I've already seen some pretty cool stuff coming in.

73
00:03:07,000 --> 00:03:09,000
Modules

74
00:03:09,000 --> 00:03:11,000
that do searches

75
00:03:11,000 --> 00:03:13,000
and post-soap requests

76
00:03:13,000 --> 00:03:15,000
and the sky's really the limit.

77
00:03:15,000 --> 00:03:17,000
We can't wait to get this out there

78
00:03:17,000 --> 00:03:19,000
into the hands of more people.

79
00:03:19,000 --> 00:03:21,000
Some less great news

80
00:03:21,000 --> 00:03:23,000
is that SourceForge hasn't come through

81
00:03:23,000 --> 00:03:25,000
with our requested project.

82
00:03:25,000 --> 00:03:27,000
They're having some trouble with their CVS infrastructure.

83
00:03:27,000 --> 00:03:29,000
And even though we've requested

84
00:03:29,000 --> 00:03:31,000
Subversion support,

85
00:03:31,000 --> 00:03:33,000
the infrastructure problems have apparently brought

86
00:03:33,000 --> 00:03:35,000
new project creation to a grinding halt.

87
00:03:35,000 --> 00:03:37,000
So

88
00:03:37,000 --> 00:03:39,000
we're now in the process of setting up

89
00:03:39,000 --> 00:03:41,000
our own code development system

90
00:03:41,000 --> 00:03:43,000
that will be based on track and Subversion.

91
00:03:43,000 --> 00:03:45,000
Most of the software

92
00:03:45,000 --> 00:03:47,000
is already in place on the production servers.

93
00:03:47,000 --> 00:03:49,000
The team is finalizing that piece today.

94
00:03:49,000 --> 00:03:51,000
After that

95
00:03:51,000 --> 00:03:53,000
we have the first round of feedback

96
00:03:53,000 --> 00:03:55,000
to incorporate into the code base in docs

97
00:03:55,000 --> 00:03:57,000
and then we're good to go.

98
00:03:57,000 --> 00:03:59,000
If everything goes according to plan

99
00:03:59,000 --> 00:04:01,000
we should be ready by late Wednesday.

100
00:04:01,000 --> 00:04:03,000
So that's all for now

101
00:04:03,000 --> 00:04:05,000
and thanks everyone for your patience.

102
00:04:05,000 --> 00:04:07,000
We can't wait to get the modules SDK

103
00:04:07,000 --> 00:04:09,000
into your hands.

104
00:04:09,000 --> 00:04:11,000
They sound kind of like Q

105
00:04:11,000 --> 00:04:13,000
at HQ telling me what all my weaponry does.

106
00:04:15,000 --> 00:04:17,000
Excellent.

107
00:04:17,000 --> 00:04:19,000
So Wednesday then I guess

108
00:04:19,000 --> 00:04:21,000
is when we get everything kicking into high gear.

109
00:04:21,000 --> 00:04:23,000
Golden ticket still being handed out.

110
00:04:23,000 --> 00:04:25,000
We've handed out quite a number of them actually

111
00:04:25,000 --> 00:04:27,000
although not everyone has received a golden ticket.

112
00:04:27,000 --> 00:04:29,000
Eventually

113
00:04:29,000 --> 00:04:31,000
we'll just turn it on and make sure

114
00:04:31,000 --> 00:04:33,000
that every single person has one.

115
00:04:33,000 --> 00:04:35,000
We're just trying to slip stream stuff in there

116
00:04:35,000 --> 00:04:37,000
and so far so good.

117
00:04:37,000 --> 00:04:39,000
Because the people who are already in on the system

118
00:04:39,000 --> 00:04:41,000
are actually using PodShow Plus

119
00:04:41,000 --> 00:04:43,000
and the podcast delivery network.

120
00:04:43,000 --> 00:04:45,000
Hey Adam, Nick Starr.

121
00:04:45,000 --> 00:04:47,000
Just got my ticket to the

122
00:04:47,000 --> 00:04:49,000
PodShow Plus

123
00:04:49,000 --> 00:04:51,000
and I have to say I'm really digging it.

124
00:04:51,000 --> 00:04:53,000
It's really cool.

125
00:04:53,000 --> 00:04:55,000
I think there's so many features on there

126
00:04:55,000 --> 00:04:57,000
that no one even expected.

127
00:04:57,000 --> 00:04:59,000
I have to say

128
00:04:59,000 --> 00:05:01,000
for everyone out there

129
00:05:01,000 --> 00:05:03,000
when this thing comes out it's going to be huge.

130
00:05:03,000 --> 00:05:05,000
If you guys like my space

131
00:05:05,000 --> 00:05:07,000
this thing blows

132
00:05:07,000 --> 00:05:09,000
anything out there away.

133
00:05:09,000 --> 00:05:11,000
It's great for publishing a podcast.

134
00:05:11,000 --> 00:05:13,000
It's great for everything.

135
00:05:13,000 --> 00:05:15,000
Just the PodShow Plus

136
00:05:15,000 --> 00:05:17,000
is awesome.

137
00:05:17,000 --> 00:05:19,000
Keep up the great work there at PodShow Guys.

138
00:05:19,000 --> 00:05:21,000
Take care.

139
00:05:21,000 --> 00:05:23,000
So obviously since I don't know what the hell I'm talking about

140
00:05:23,000 --> 00:05:25,000
we're going to keep this devcast

141
00:05:25,000 --> 00:05:27,000
relatively short.

142
00:05:27,000 --> 00:05:29,000
But then maybe Wednesday

143
00:05:29,000 --> 00:05:31,000
end of my day here in the UK

144
00:05:31,000 --> 00:05:33,000
beginning of the San Francisco day

145
00:05:33,000 --> 00:05:35,000
with a Skype call or something.

146
00:05:35,000 --> 00:05:37,000
I'm going to be

147
00:05:37,000 --> 00:05:39,000
in the British Telecom offices

148
00:05:39,000 --> 00:05:41,000
meeting with the CEO

149
00:05:41,000 --> 00:05:43,000
on Wednesday.

150
00:05:43,000 --> 00:05:45,000
So it may be a little bit later on in the day

151
00:05:45,000 --> 00:05:47,000
but I'll definitely try and get that up.

152
00:05:47,000 --> 00:05:49,000
I'm going to leave you with the song.

153
00:05:49,000 --> 00:05:51,000
I've been looking around for cool songs for developers

154
00:05:51,000 --> 00:05:53,000
if possible

155
00:05:53,000 --> 00:05:55,000
at all. Of course PodSafe

156
00:05:55,000 --> 00:05:57,000
from the PodSafe Music Network

157
00:05:57,000 --> 00:05:59,000
and something I played on the source code the other day

158
00:05:59,000 --> 00:06:01,000
was MC++

159
00:06:01,000 --> 00:06:03,000
and I think I've played this one on the source code before

160
00:06:03,000 --> 00:06:05,000
but it's

161
00:06:05,000 --> 00:06:07,000
something for all you code jockeys out there.

162
00:06:08,750 --> 00:08:52,800
[ Music ]

163
00:08:52,800 --> 00:08:55,800
Cold Monkey very simple man

164
00:08:55,800 --> 00:08:58,800
Big, warm, fuzzy, secret mark

165
00:08:58,800 --> 00:09:01,800
Cold Monkey like you

166
00:09:18,800 --> 00:09:22,800
Podcast delivery network from PodShow and Limelight Networks

167
00:09:22,800 --> 00:09:24,800
I love it