WEBVTT

1
00:00:01.080 --> 00:00:02.960
<v Speaker 1>How'd you like to listen to dot net rocks with

2
00:00:03.040 --> 00:00:07.879
<v Speaker 1>no ads? Easy? Become a patron for just five dollars

3
00:00:07.919 --> 00:00:10.800
<v Speaker 1>a month. You get access to a private RSS feed

4
00:00:10.800 --> 00:00:14.240
<v Speaker 1>where all the shows have no ads. Twenty dollars a month,

5
00:00:14.279 --> 00:00:16.879
<v Speaker 1>we'll get you that and a special dot net Rocks

6
00:00:16.960 --> 00:00:20.960
<v Speaker 1>patron mug. Sign up now at Patreon dot dot NetRocks

7
00:00:21.120 --> 00:00:37.200
<v Speaker 1>dot com. Hey, welcome back to dot net Rocks episode

8
00:00:37.280 --> 00:00:41.079
<v Speaker 1>twenty ten. I'm Carl Franklin, that Chard Campbell, and we're

9
00:00:41.079 --> 00:00:43.960
<v Speaker 1>talking to Rob Menschin today. But we'll be talking to

10
00:00:44.039 --> 00:00:47.039
<v Speaker 1>him in just a minute. But first, how are you, Richard?

11
00:00:47.119 --> 00:00:49.600
<v Speaker 2>I'm great, dude. I've been you know, home for a

12
00:00:49.600 --> 00:00:50.920
<v Speaker 2>few weeks and that's always fun.

13
00:00:51.039 --> 00:00:54.880
<v Speaker 1>Yeah, always fun. Well, let's start it off right because

14
00:00:54.960 --> 00:00:57.840
<v Speaker 1>you know, we got to get through this intro stuff.

15
00:00:57.880 --> 00:00:58.960
<v Speaker 1>It's going to be weird today.

16
00:00:59.119 --> 00:01:02.000
<v Speaker 2>I point out there's only to be sixteen more of these, right,

17
00:01:02.759 --> 00:01:03.960
<v Speaker 2>eventually we reach time.

18
00:01:04.120 --> 00:01:08.359
<v Speaker 1>We do these sort of weekly mini geek outs and

19
00:01:08.480 --> 00:01:12.359
<v Speaker 1>Rob feel free to join in anytime. All right, this

20
00:01:12.439 --> 00:01:16.280
<v Speaker 1>being episode twenty ten, let's talk about what happened that year. Yeah,

21
00:01:16.319 --> 00:01:18.840
<v Speaker 1>first of all, there was a terrible earthquake in Haiti

22
00:01:19.400 --> 00:01:24.120
<v Speaker 1>seven point zero bigin devastated Haiti, killing an estimated get this,

23
00:01:24.879 --> 00:01:28.959
<v Speaker 1>almost three hundred thousand people. It's crazy, and leaving more

24
00:01:28.959 --> 00:01:33.599
<v Speaker 1>than one point five million homeless. Just absolutely devastating.

25
00:01:33.680 --> 00:01:38.040
<v Speaker 2>Because there was there was a seven earthquake in christ

26
00:01:38.159 --> 00:01:40.120
<v Speaker 2>Church that same year that killed.

27
00:01:40.079 --> 00:01:41.040
<v Speaker 1>I think two people.

28
00:01:41.159 --> 00:01:45.079
<v Speaker 2>Yeah, like construction matters, although Church will go through a lot.

29
00:01:45.239 --> 00:01:46.920
<v Speaker 1>Chile also had an earthquake. Yeah.

30
00:01:46.959 --> 00:01:49.640
<v Speaker 2>Yeah, it's funny because as we're recording this in June,

31
00:01:49.640 --> 00:01:52.239
<v Speaker 2>there's just been a whole string of earthquakes around the

32
00:01:52.239 --> 00:01:54.359
<v Speaker 2>Pacific rim that's right, and in Venezuela.

33
00:01:54.560 --> 00:01:56.760
<v Speaker 1>Yeah, so Venezuela was just yesterday.

34
00:01:56.879 --> 00:01:57.760
<v Speaker 2>Yeah, it's crazy.

35
00:01:57.879 --> 00:02:03.040
<v Speaker 1>Yeah. The deep Waters an oil spill which gave dawn

36
00:02:03.200 --> 00:02:05.599
<v Speaker 1>dishwasher detergent a new identity.

37
00:02:05.680 --> 00:02:08.360
<v Speaker 2>I'm pretty sure that happened back in the Mesonvaldis.

38
00:02:08.439 --> 00:02:11.919
<v Speaker 1>But okay, oh yeah, you're right, that's right. Yeah, the

39
00:02:12.919 --> 00:02:16.319
<v Speaker 1>little duck on the down bottle. That was excellent Valdis.

40
00:02:16.400 --> 00:02:16.680
<v Speaker 3>Yeah.

41
00:02:16.680 --> 00:02:19.560
<v Speaker 1>But anyway, so this was an explosion of an offshore

42
00:02:19.639 --> 00:02:20.400
<v Speaker 1>drilling rig.

43
00:02:20.280 --> 00:02:22.400
<v Speaker 2>VP killed a bunch of people, yeah.

44
00:02:22.360 --> 00:02:26.560
<v Speaker 1>Eleven workers. Gulf of Mexico caused the largest marine oil

45
00:02:26.599 --> 00:02:30.879
<v Speaker 1>spill in US history. Millions of barrels because it was.

46
00:02:30.919 --> 00:02:33.400
<v Speaker 2>Running deep underwater, right, and it took a long time

47
00:02:33.400 --> 00:02:34.919
<v Speaker 2>to get down there and lock it down. It was

48
00:02:34.960 --> 00:02:35.360
<v Speaker 2>hard to do.

49
00:02:35.639 --> 00:02:39.240
<v Speaker 1>Yeah, in New Orleans, they weren't selling so many shrimp.

50
00:02:39.360 --> 00:02:40.039
<v Speaker 1>Let's just say that.

51
00:02:40.199 --> 00:02:42.319
<v Speaker 2>Oh, well they're still finding that.

52
00:02:42.439 --> 00:02:42.599
<v Speaker 4>Well.

53
00:02:42.840 --> 00:02:45.039
<v Speaker 2>Yeah, fifteen sixteen years later.

54
00:02:45.319 --> 00:02:49.080
<v Speaker 1>The Wiki leaks Document Leaks Julian Massage, of course, published

55
00:02:49.240 --> 00:02:54.879
<v Speaker 1>hundreds of thousands of classified US military reports and then

56
00:02:54.960 --> 00:02:56.319
<v Speaker 1>scooted to Russia.

57
00:02:56.639 --> 00:02:58.719
<v Speaker 2>Yeah, ultimately ended up in England and stayed in the

58
00:02:58.759 --> 00:03:06.000
<v Speaker 2>Ecuadorian a consulate for a decade. Like that's tough, but yeah. Yeah.

59
00:03:06.080 --> 00:03:10.680
<v Speaker 1>The Arab spring began in twenty ten. In December, Mohammed Bozazi, Yeah,

60
00:03:10.759 --> 00:03:15.439
<v Speaker 1>self immolated after harassment by local authorities and that started it.

61
00:03:15.560 --> 00:03:18.599
<v Speaker 2>Yeah, that was the beginning of a tremendous change.

62
00:03:19.639 --> 00:03:26.319
<v Speaker 1>European debt crisis intensifies Greece. Remember that Greece basically went broke.

63
00:03:26.800 --> 00:03:30.240
<v Speaker 2>This is when the challenge of the EU infrastructure really

64
00:03:30.240 --> 00:03:33.759
<v Speaker 2>took a hold, where Greek euros aren't the same as

65
00:03:33.800 --> 00:03:36.919
<v Speaker 2>German euros, right, and that's the reality they had to

66
00:03:37.000 --> 00:03:40.479
<v Speaker 2>contend with all byproducts of the subprime crisis.

67
00:03:40.599 --> 00:03:43.960
<v Speaker 1>North Korea's military aggression. They were blamed for sinking the

68
00:03:44.000 --> 00:03:49.879
<v Speaker 1>South Korean naval ship Chionin, killing forty six sailors. And yeah,

69
00:03:50.479 --> 00:03:55.240
<v Speaker 1>that wasn't good. Another natural disaster in Iceland, the volcanic eruption.

70
00:03:55.400 --> 00:03:57.080
<v Speaker 2>Yeah, you're going to say that name. Go ahead, say

71
00:03:57.080 --> 00:04:01.000
<v Speaker 2>that name, Carl. I'll say it's got three j's in it.

72
00:04:01.000 --> 00:04:01.840
<v Speaker 2>It must be easy.

73
00:04:01.960 --> 00:04:09.240
<v Speaker 1>I falcol something like that, something like that. I actually

74
00:04:09.280 --> 00:04:12.919
<v Speaker 1>have a bottle of the ash from that's amazing. Yeah.

75
00:04:12.919 --> 00:04:16.160
<v Speaker 1>I bought it at the Rekuvik airport and I brought

76
00:04:16.160 --> 00:04:17.920
<v Speaker 1>it home and I thought my kids would appreciate it,

77
00:04:17.959 --> 00:04:23.680
<v Speaker 1>and they just left it here. That what the hell, dad, whatever? Whatever, Okay,

78
00:04:23.759 --> 00:04:29.839
<v Speaker 1>I like it. It's on my minicle. Polish presidential plane crashed.

79
00:04:31.959 --> 00:04:35.800
<v Speaker 1>Ninety five others, including the president died when they are aircraft

80
00:04:35.720 --> 00:04:38.920
<v Speaker 1>crashed near Smolensk, Russia.

81
00:04:39.079 --> 00:04:39.639
<v Speaker 2>Slensk.

82
00:04:39.920 --> 00:04:47.480
<v Speaker 1>Yeah, Smolensk, Iran's nuclear program ambitions intensified. New sanctions were imposed.

83
00:04:50.160 --> 00:04:52.600
<v Speaker 1>We don't know how that's going to end. Nice. The

84
00:04:52.720 --> 00:04:58.560
<v Speaker 1>US Affordable Care Act takes effect in March, became the

85
00:04:58.639 --> 00:05:02.439
<v Speaker 1>largest overhaul of the uslthcare system in decades and dominated

86
00:05:02.519 --> 00:05:06.480
<v Speaker 1>American politics for years afterwards, including this day. They're still

87
00:05:06.480 --> 00:05:10.279
<v Speaker 1>fighting over it still. Yeah, and the FIFA World Cup

88
00:05:10.360 --> 00:05:11.240
<v Speaker 1>in South Africa.

89
00:05:12.399 --> 00:05:16.160
<v Speaker 2>Don't forget about the Winter Olympics in Vancouver. Oh yeah, okay, yeah,

90
00:05:16.199 --> 00:05:18.399
<v Speaker 2>and that was and that was the silver Light Olympics.

91
00:05:18.600 --> 00:05:22.279
<v Speaker 2>Our friend Scott Stanfield had the contract to do silver

92
00:05:22.360 --> 00:05:23.120
<v Speaker 2>Light for NBC.

93
00:05:23.240 --> 00:05:28.120
<v Speaker 1>Yeah, that's right. Scott basically had a streaming video platform

94
00:05:28.199 --> 00:05:31.519
<v Speaker 1>on silver Light and sold it to Major League Baseball eventually.

95
00:05:31.639 --> 00:05:33.879
<v Speaker 2>Eventually by that time he was doing it for NBC

96
00:05:34.000 --> 00:05:36.680
<v Speaker 2>and we were we were watching it, and I realized

97
00:05:36.759 --> 00:05:38.519
<v Speaker 2>we were talking about it as he was working on it.

98
00:05:38.639 --> 00:05:40.240
<v Speaker 2>He had no plans to come to the games, and like,

99
00:05:40.240 --> 00:05:42.240
<v Speaker 2>what are you doing? Yeah, get on a plane, get

100
00:05:42.319 --> 00:05:44.079
<v Speaker 2>up here. And we ended up going to a lot

101
00:05:44.120 --> 00:05:44.560
<v Speaker 2>of currently.

102
00:05:44.720 --> 00:05:49.519
<v Speaker 1>Yeah, so, oh, should I tell that story about Scott

103
00:05:49.600 --> 00:05:54.040
<v Speaker 1>Stanfield We had after he sold to Major League Baseball.

104
00:05:55.480 --> 00:05:58.000
<v Speaker 1>We were at an MVP summit. I think we were

105
00:05:58.040 --> 00:06:03.519
<v Speaker 1>at Daniel's restaurant. Michelle was there and you were there,

106
00:06:03.560 --> 00:06:06.480
<v Speaker 1>and Kelly was with me and we had to Kelly

107
00:06:06.480 --> 00:06:08.519
<v Speaker 1>and I had to leave early. So we offered to

108
00:06:08.920 --> 00:06:11.279
<v Speaker 1>you know, chip in and pay for stuff, right, And

109
00:06:11.319 --> 00:06:15.519
<v Speaker 1>he says he's drunk. He goes, you're not paying and

110
00:06:15.600 --> 00:06:18.079
<v Speaker 1>I said, come on, let's just you know, we can

111
00:06:18.120 --> 00:06:21.639
<v Speaker 1>pay our way. He goes, look, I'm really really rich

112
00:06:22.600 --> 00:06:27.079
<v Speaker 1>and I'm really really drunk, so fuck off or something

113
00:06:27.199 --> 00:06:35.759
<v Speaker 1>like that. Yeah, good on, Scott, just honorable mentions. He

114
00:06:35.800 --> 00:06:41.560
<v Speaker 1>attempted Times Square car bombing, record flooding in Pakistan, the

115
00:06:41.720 --> 00:06:46.879
<v Speaker 1>UK election resulting in the Conservative Liberal Democrat coalition government

116
00:06:47.360 --> 00:06:51.279
<v Speaker 1>in the end of the N one influenza pandemic. So

117
00:06:51.399 --> 00:06:55.279
<v Speaker 1>it was a disastrous year for global events except for those,

118
00:06:55.439 --> 00:06:58.720
<v Speaker 1>you know, sporting events. A right, Yeah they did, okay, Richard,

119
00:06:59.000 --> 00:07:01.199
<v Speaker 1>tell us about space tech, the spacey stuff.

120
00:07:01.279 --> 00:07:03.879
<v Speaker 2>There are three shuttle flights, all early in the year.

121
00:07:03.959 --> 00:07:07.000
<v Speaker 2>February Endeavor brings No. Three in the couple up to

122
00:07:07.000 --> 00:07:11.800
<v Speaker 2>the Space station, and April Discovery brings the Leonardo cargo carrier,

123
00:07:12.560 --> 00:07:16.040
<v Speaker 2>and in May Atlantis brings a Russian research module, the

124
00:07:16.040 --> 00:07:20.959
<v Speaker 2>Mini Research Module. And that's it for shuttles that year, amazingly,

125
00:07:21.240 --> 00:07:23.079
<v Speaker 2>and this is almost it right. Next year will bee

126
00:07:23.160 --> 00:07:26.920
<v Speaker 2>a last of the shuttle flights. Much more activity though.

127
00:07:27.000 --> 00:07:32.800
<v Speaker 2>In May, the Japanese Space program launches Akatsuki, which is

128
00:07:32.839 --> 00:07:36.839
<v Speaker 2>their Venus climate orbiter to Venus later that year, in December,

129
00:07:36.839 --> 00:07:40.079
<v Speaker 2>it's supposed to do a twelve minute burn to go

130
00:07:40.240 --> 00:07:44.079
<v Speaker 2>into orbit around Venus, and something goes wrong. The problem

131
00:07:44.120 --> 00:07:46.720
<v Speaker 2>is that because it's trying to go into orbit around Venus,

132
00:07:46.759 --> 00:07:48.879
<v Speaker 2>as the burn that starts, they can see the burn starts,

133
00:07:48.920 --> 00:07:51.680
<v Speaker 2>and then the spacecraft she goes behind Venus relative to

134
00:07:51.720 --> 00:07:54.480
<v Speaker 2>the Earth, so they have no communication with it, and

135
00:07:54.560 --> 00:07:59.000
<v Speaker 2>then too long goes by, and when they finally get

136
00:07:59.040 --> 00:08:01.279
<v Speaker 2>a hold of it, it's in safe mode and tumbling,

137
00:08:02.079 --> 00:08:06.160
<v Speaker 2>and they managed to get it, communicating with it again

138
00:08:06.199 --> 00:08:08.199
<v Speaker 2>and get it recover realized it only ran that burn

139
00:08:08.240 --> 00:08:09.920
<v Speaker 2>only went for three minutes, so it's not in orbit,

140
00:08:09.959 --> 00:08:12.480
<v Speaker 2>it's going to miss, it's going to fly by. It

141
00:08:12.519 --> 00:08:14.319
<v Speaker 2>takes them a few weeks to figure out that the

142
00:08:14.360 --> 00:08:16.759
<v Speaker 2>main engines badly damaged, that there was actually a kind

143
00:08:16.759 --> 00:08:19.240
<v Speaker 2>of an explosion on board. Really, what had happened was

144
00:08:19.279 --> 00:08:21.160
<v Speaker 2>there was a leak in the fuel system and too

145
00:08:21.199 --> 00:08:22.959
<v Speaker 2>much oxtars that went to the engine and burned the

146
00:08:23.000 --> 00:08:26.480
<v Speaker 2>engine up. This is the same thing that likely happened

147
00:08:26.480 --> 00:08:28.720
<v Speaker 2>to Mars Observer and resulted in a total loss of

148
00:08:28.759 --> 00:08:30.959
<v Speaker 2>Mars Observer a number of years before. So they got

149
00:08:31.040 --> 00:08:33.759
<v Speaker 2>lucky here here's the crazy part. They still have a

150
00:08:33.759 --> 00:08:36.759
<v Speaker 2>spacecraft and they're still trying to figure out what to

151
00:08:36.759 --> 00:08:38.759
<v Speaker 2>do with it. So they managed to figure out a

152
00:08:38.799 --> 00:08:41.960
<v Speaker 2>new orbit so that five years later, in twenty fifteen,

153
00:08:42.240 --> 00:08:44.799
<v Speaker 2>they'll get close enough to Venus to attempt to go

154
00:08:44.799 --> 00:08:48.120
<v Speaker 2>into orbit again, but they don't have the main engine. Also,

155
00:08:48.159 --> 00:08:50.240
<v Speaker 2>the vehicle was only supposed to survive for four years,

156
00:08:50.639 --> 00:08:53.799
<v Speaker 2>so they designed a hibernate mode for it that it

157
00:08:53.799 --> 00:08:57.320
<v Speaker 2>didn't have, upload it, shut it down for three and

158
00:08:57.360 --> 00:09:01.519
<v Speaker 2>a half years, and then work out all the equations

159
00:09:01.519 --> 00:09:04.480
<v Speaker 2>for using the maneuvering thrusters to actually put it into orbit.

160
00:09:04.600 --> 00:09:07.200
<v Speaker 2>Realize they're carrying too much fuel, so they turn it

161
00:09:07.240 --> 00:09:09.799
<v Speaker 2>on and dump the excess oxidizer, not going to need

162
00:09:09.799 --> 00:09:13.080
<v Speaker 2>to lower its weight enough, and in twenty fifteen managed

163
00:09:13.120 --> 00:09:16.679
<v Speaker 2>to get it into an odd elliptical orbit around Venus

164
00:09:16.720 --> 00:09:19.240
<v Speaker 2>so it can actually do its science and it'll operate

165
00:09:19.320 --> 00:09:22.240
<v Speaker 2>up there till twenty twenty four. Very cool, very cool. Indeed,

166
00:09:22.559 --> 00:09:28.080
<v Speaker 2>another amazing Japanese satellite mission, the Hyabusa, that was the

167
00:09:28.080 --> 00:09:34.200
<v Speaker 2>one that actually touched down on Iakawa asteroid. You've seen

168
00:09:34.240 --> 00:09:36.639
<v Speaker 2>the video of the spray of rock. Because it's like

169
00:09:36.720 --> 00:09:40.039
<v Speaker 2>most asteroids. We've now realized their rubber piles. So this

170
00:09:40.080 --> 00:09:43.279
<v Speaker 2>little arm touched down to grab some parts and actually

171
00:09:43.320 --> 00:09:46.159
<v Speaker 2>jammed it because there was so much debris. But they

172
00:09:46.159 --> 00:09:47.840
<v Speaker 2>managed to get it closed up. They got it into

173
00:09:47.879 --> 00:09:51.039
<v Speaker 2>its container, and in twenty ten it done the rendezvous

174
00:09:51.080 --> 00:09:53.279
<v Speaker 2>in two thousand and five. In twenty ten it actually

175
00:09:53.320 --> 00:09:59.039
<v Speaker 2>returns part in debris from an asteroid to Earth successfully,

176
00:09:59.279 --> 00:09:59.879
<v Speaker 2>first time we ever.

177
00:09:59.879 --> 00:10:00.720
<v Speaker 1>Ha that wow.

178
00:10:00.799 --> 00:10:04.279
<v Speaker 2>Also in June, SpaceX launches the very first Falcon nine

179
00:10:04.720 --> 00:10:09.120
<v Speaker 2>with a Dragon qualification unit on board, just a test flight,

180
00:10:09.279 --> 00:10:11.600
<v Speaker 2>and that will lead to the later flight in December,

181
00:10:11.679 --> 00:10:13.879
<v Speaker 2>the second flight, what they call the Cotts demo flight.

182
00:10:13.879 --> 00:10:16.120
<v Speaker 2>Once this is doing resupply to the International Space Station.

183
00:10:16.159 --> 00:10:17.919
<v Speaker 2>All this one doesn't actually do resupply. It does go

184
00:10:17.919 --> 00:10:21.000
<v Speaker 2>into orbit proof as it can, does carry a few microsatellites.

185
00:10:21.039 --> 00:10:23.679
<v Speaker 2>Also a wheel of cheese because it needed some kind

186
00:10:23.679 --> 00:10:27.679
<v Speaker 2>of payload, so they put an entire wheel of libourriere

187
00:10:27.919 --> 00:10:29.879
<v Speaker 2>cheese and then brought it back. It was the first

188
00:10:29.879 --> 00:10:33.840
<v Speaker 2>time that a private company put something into orbit and

189
00:10:34.039 --> 00:10:35.440
<v Speaker 2>returned it successfully.

190
00:10:35.519 --> 00:10:37.080
<v Speaker 1>I wonder if that improved the flavor.

191
00:10:37.320 --> 00:10:40.240
<v Speaker 2>I don't know. It certainly photed around a little it's

192
00:10:40.279 --> 00:10:45.480
<v Speaker 2>a great question. Also in October, Chinese launch the Change two,

193
00:10:45.879 --> 00:10:49.200
<v Speaker 2>which goes into orbit around the Moon later that same month.

194
00:10:49.720 --> 00:10:51.320
<v Speaker 2>It'll hang out there for a year or so. In

195
00:10:51.360 --> 00:10:53.320
<v Speaker 2>twenty eleven, it will leave orbit of the Moon and

196
00:10:53.360 --> 00:10:56.120
<v Speaker 2>actually go to lagrange point two, which will make the

197
00:10:56.159 --> 00:10:59.440
<v Speaker 2>only third nation besides NASA and NISSA ever go there.

198
00:11:00.039 --> 00:11:02.960
<v Speaker 2>And then we'll fly on from there to intercept an

199
00:11:03.000 --> 00:11:06.720
<v Speaker 2>asteroid called it Tutatus in twenty twelve. Wow, that was

200
00:11:06.960 --> 00:11:09.960
<v Speaker 2>an amazing mission. And again the Chinese are quite accomplishment

201
00:11:10.000 --> 00:11:13.480
<v Speaker 2>space even by twenty ten. On the computing side, we'll

202
00:11:13.559 --> 00:11:18.440
<v Speaker 2>lead in February with the Windows Phone seven announcement running

203
00:11:18.440 --> 00:11:20.960
<v Speaker 2>a modified version of Civilite, and it will ship in

204
00:11:21.000 --> 00:11:22.159
<v Speaker 2>the US in November.

205
00:11:22.279 --> 00:11:24.559
<v Speaker 1>It's almost like a eulogy, isn't it.

206
00:11:24.720 --> 00:11:28.080
<v Speaker 2>I mean, you know, you know, the funny thing is

207
00:11:28.120 --> 00:11:29.960
<v Speaker 2>when you like to have that phone now, with the

208
00:11:29.960 --> 00:11:31.840
<v Speaker 2>way phones are at the moment, like I kind of

209
00:11:31.840 --> 00:11:32.279
<v Speaker 2>miss them.

210
00:11:32.320 --> 00:11:33.639
<v Speaker 1>I do too.

211
00:11:33.759 --> 00:11:36.480
<v Speaker 2>Also, and in March we have the Mixed twenty ten,

212
00:11:36.559 --> 00:11:38.639
<v Speaker 2>which is when we get NBC two point zero and

213
00:11:38.679 --> 00:11:41.879
<v Speaker 2>a bunch of other cool announcements. March is also when

214
00:11:42.799 --> 00:11:46.039
<v Speaker 2>Apple announces a thing they call the iPad a really

215
00:11:46.039 --> 00:11:51.279
<v Speaker 2>big iPhone and freak everybody out, which then is followed

216
00:11:51.279 --> 00:11:54.600
<v Speaker 2>in March by an open letter published by Steve Jobs

217
00:11:54.639 --> 00:11:59.360
<v Speaker 2>called thoughts on Flash. Right now, what did Steve say

218
00:11:59.360 --> 00:12:02.000
<v Speaker 2>in his Thoughts on Flash? Well, he he didn't say

219
00:12:02.159 --> 00:12:04.720
<v Speaker 2>was the truth, which is Flash was murdering the battery

220
00:12:04.759 --> 00:12:07.480
<v Speaker 2>of his iPad, Yeah, because that was his Flash was

221
00:12:07.519 --> 00:12:10.240
<v Speaker 2>never made for mobile devices, right, it was for PCs

222
00:12:10.919 --> 00:12:11.840
<v Speaker 2>and so but it was.

223
00:12:11.759 --> 00:12:14.840
<v Speaker 1>Bigger than that. It was about the security of plugins,

224
00:12:14.879 --> 00:12:16.480
<v Speaker 1>or the lack of security of plugins.

225
00:12:16.519 --> 00:12:18.840
<v Speaker 2>Oh, you're absolutely right. Yeah, that the real issue here.

226
00:12:18.919 --> 00:12:21.240
<v Speaker 2>And the thing I whenever I talk about this is

227
00:12:21.279 --> 00:12:25.000
<v Speaker 2>I do fairly often doing the history talks. We all

228
00:12:25.639 --> 00:12:30.360
<v Speaker 2>in you know, the two thousands. Every Christmas going to family,

229
00:12:31.120 --> 00:12:33.960
<v Speaker 2>we're replacing people's address bars because over the course of

230
00:12:33.960 --> 00:12:36.120
<v Speaker 2>the year, inevitably they downloaded something that swapped out their

231
00:12:36.120 --> 00:12:38.320
<v Speaker 2>address bar with some kind of spyware, right, And so

232
00:12:38.399 --> 00:12:40.639
<v Speaker 2>you were always fixing that because that was the nature

233
00:12:40.639 --> 00:12:43.240
<v Speaker 2>of plugins at the time. And so Steve wasn't wrong.

234
00:12:43.519 --> 00:12:45.480
<v Speaker 2>Plugins are a huge risk and he was going to

235
00:12:45.519 --> 00:12:48.399
<v Speaker 2>eliminate and he said, Safari's never going to run plugins

236
00:12:48.559 --> 00:12:49.200
<v Speaker 2>like this, is it?

237
00:12:49.360 --> 00:12:52.559
<v Speaker 1>And that was kind of a death knell for for

238
00:12:53.240 --> 00:12:57.039
<v Speaker 1>silver Light, but also just the lack of plugins is

239
00:12:57.080 --> 00:12:59.200
<v Speaker 1>the death knell for silver Light. You know, if you

240
00:12:59.200 --> 00:13:01.720
<v Speaker 1>don't silver used to plug in technology and if you

241
00:13:01.759 --> 00:13:03.600
<v Speaker 1>don't have that, you know it's well.

242
00:13:03.679 --> 00:13:06.120
<v Speaker 2>The problem, of course is that in April is also

243
00:13:06.159 --> 00:13:09.480
<v Speaker 2>the launch of Visual Studio twenty ten. I helped run

244
00:13:09.519 --> 00:13:09.919
<v Speaker 2>that event.

245
00:13:10.000 --> 00:13:10.559
<v Speaker 1>Yeah, me too.

246
00:13:10.639 --> 00:13:13.639
<v Speaker 2>And this is framework four. Oh, this is the WPF

247
00:13:13.759 --> 00:13:16.480
<v Speaker 2>version of Studio. This is the release of f sharp,

248
00:13:16.840 --> 00:13:20.080
<v Speaker 2>this is j Query and open source library bundling the box,

249
00:13:20.840 --> 00:13:24.519
<v Speaker 2>you know, with its regular license still attached to it.

250
00:13:24.759 --> 00:13:27.279
<v Speaker 2>And of course silver Light four the first version of

251
00:13:27.279 --> 00:13:30.440
<v Speaker 2>support chrome and out of browser and was pitched in

252
00:13:30.480 --> 00:13:34.600
<v Speaker 2>April as this is the way that enterprises do cross

253
00:13:34.600 --> 00:13:35.639
<v Speaker 2>platform development.

254
00:13:35.799 --> 00:13:39.639
<v Speaker 1>Internally, I believe my band played at the launch party,

255
00:13:39.799 --> 00:13:42.919
<v Speaker 1>yeah in Las Vegas at the Mirage when we were there.

256
00:13:43.039 --> 00:13:46.840
<v Speaker 2>Yeah, we also have Windows Azure shipped with sql Azure,

257
00:13:46.879 --> 00:13:50.759
<v Speaker 2>php support for Phpjava dot Net with webrolls and approles.

258
00:13:50.919 --> 00:13:53.120
<v Speaker 2>If you remember, most of us didn't understand it. We

259
00:13:53.120 --> 00:13:54.919
<v Speaker 2>were trying to do shows about it and noverybody was confused.

260
00:13:57.000 --> 00:13:59.960
<v Speaker 2>And then we fast forward to the fall till October

261
00:14:00.080 --> 00:14:03.600
<v Speaker 2>with the Larry last PDC on the campus in Redmond,

262
00:14:03.679 --> 00:14:06.279
<v Speaker 2>Rained the whole time. It's only about a thousand people

263
00:14:06.320 --> 00:14:10.039
<v Speaker 2>there because there's not a lot of space and exactly

264
00:14:10.279 --> 00:14:15.559
<v Speaker 2>no silver light sessions, which is an amazing transformation from

265
00:14:16.279 --> 00:14:21.240
<v Speaker 2>April six months later Microsoft Premier Conference. No civilight sessions. Now,

266
00:14:21.879 --> 00:14:24.279
<v Speaker 2>I subsequentely discovered just by asking around, like why a

267
00:14:24.279 --> 00:14:25.840
<v Speaker 2>there are no civil light sessions because there was no

268
00:14:25.840 --> 00:14:29.039
<v Speaker 2>silver light team left. They'd essentially been dismantled. A bunch

269
00:14:29.080 --> 00:14:31.840
<v Speaker 2>of them had gone over to win Phone seven, and

270
00:14:31.879 --> 00:14:34.200
<v Speaker 2>a bunch of them had gone to the new version

271
00:14:34.240 --> 00:14:36.120
<v Speaker 2>of Windows that was going to react to the iPad,

272
00:14:36.559 --> 00:14:40.039
<v Speaker 2>and so they didn't submit any sessions. And famously, again

273
00:14:40.200 --> 00:14:44.480
<v Speaker 2>we're talking about our history. Mary Joe Foley asked Bob

274
00:14:44.559 --> 00:14:47.120
<v Speaker 2>Mugli at that point, the president of Server and Tools

275
00:14:47.120 --> 00:14:50.519
<v Speaker 2>he owns Azure and oll of DEVNIV, why there was

276
00:14:50.559 --> 00:14:53.279
<v Speaker 2>no mention of silver light, and Bob looks vaguely confused

277
00:14:53.279 --> 00:14:56.360
<v Speaker 2>and says, well, our strategy has shifted. What Bob doesn't

278
00:14:56.440 --> 00:15:00.679
<v Speaker 2>know is that there's been no public announcements about the

279
00:15:00.759 --> 00:15:03.320
<v Speaker 2>impact of thoughts on flash, on silverlight and so forth,

280
00:15:03.639 --> 00:15:05.759
<v Speaker 2>because for the most at that point when the iPad

281
00:15:05.840 --> 00:15:09.399
<v Speaker 2>came out, there was a real lockdown in talking about

282
00:15:09.399 --> 00:15:11.679
<v Speaker 2>how Microsoft was going to respond to the iPad. There

283
00:15:11.720 --> 00:15:13.679
<v Speaker 2>was a lot more fear about the iPad then when

284
00:15:13.720 --> 00:15:16.240
<v Speaker 2>it was still a mythological product than the way we

285
00:15:16.240 --> 00:15:19.960
<v Speaker 2>feel about tablets today. And so you know, I've subsequently

286
00:15:19.960 --> 00:15:22.919
<v Speaker 2>interviewed Bob Mugley about this and he said, point blankly,

287
00:15:22.960 --> 00:15:24.320
<v Speaker 2>I didn't know. I was the first person to talk

288
00:15:24.320 --> 00:15:27.759
<v Speaker 2>about it. And to MJ's credit, all she said was

289
00:15:27.799 --> 00:15:31.320
<v Speaker 2>what Bob said, our strategy has shifted. Yeah, it was

290
00:15:31.360 --> 00:15:35.000
<v Speaker 2>everybody else who said silverlight is dead and Microsoft really

291
00:15:35.039 --> 00:15:38.679
<v Speaker 2>said nothing, and that upset a lot of people. Like

292
00:15:38.720 --> 00:15:40.600
<v Speaker 2>there's lots of folks that are still not over that.

293
00:15:40.759 --> 00:15:44.080
<v Speaker 2>Like that's that was a tough day and a tough

294
00:15:44.120 --> 00:15:48.000
<v Speaker 2>situation to be in October, when our friend Phil Hack

295
00:15:48.240 --> 00:15:51.519
<v Speaker 2>leads the project that becomes the first version of New Get.

296
00:15:52.279 --> 00:15:54.720
<v Speaker 2>All these things in the same year, and then in

297
00:15:54.759 --> 00:15:57.600
<v Speaker 2>November the Xbox Connect not the same thing at all,

298
00:15:59.240 --> 00:16:01.360
<v Speaker 2>and I'll mention too other products. Then we wrap this up.

299
00:16:01.639 --> 00:16:05.279
<v Speaker 2>Instagram ships this year, Kevin Seistrom and Micah Krieger, and

300
00:16:05.639 --> 00:16:07.000
<v Speaker 2>also Facebook Messenger.

301
00:16:07.120 --> 00:16:10.679
<v Speaker 1>I have some things to add because twenty ten marked

302
00:16:10.679 --> 00:16:15.519
<v Speaker 1>the beginning of the streaming era in audio, streaming subscriptions

303
00:16:15.559 --> 00:16:20.000
<v Speaker 1>became commercially viable. Spotify established the business model that most

304
00:16:20.000 --> 00:16:24.519
<v Speaker 1>competitors would follow. Pandora familiarized millions of listeners with streaming.

305
00:16:25.000 --> 00:16:28.960
<v Speaker 1>Smartphones made streaming convenient enough for mainstream adoption, and the

306
00:16:29.039 --> 00:16:33.200
<v Speaker 1>music industry began shifting away from ownership towards access. And

307
00:16:34.159 --> 00:16:38.039
<v Speaker 1>this also kind of is a death noell for musicians

308
00:16:38.159 --> 00:16:39.320
<v Speaker 1>and recording artists.

309
00:16:39.360 --> 00:16:40.279
<v Speaker 2>It's the final straw.

310
00:16:40.360 --> 00:16:42.480
<v Speaker 1>It was the Yeah, it was the beginning of the

311
00:16:42.600 --> 00:16:45.679
<v Speaker 1>end for the for the music business as far as

312
00:16:47.120 --> 00:16:50.240
<v Speaker 1>artists being compensated for their work goes were. You know,

313
00:16:50.360 --> 00:16:56.679
<v Speaker 1>record sales continued, you know, digital downloads continued, but really

314
00:16:57.200 --> 00:17:01.360
<v Speaker 1>people stopped buying CDs and map and it was all

315
00:17:01.399 --> 00:17:04.079
<v Speaker 1>about the MP three and your stream and all of

316
00:17:04.119 --> 00:17:08.880
<v Speaker 1>that kind of stuff. Download still dominated revenue, but streaming

317
00:17:09.000 --> 00:17:12.759
<v Speaker 1>was started on his way, on its way. So twenty

318
00:17:12.839 --> 00:17:16.079
<v Speaker 1>ten marks the the end of the music business as we.

319
00:17:16.039 --> 00:17:18.319
<v Speaker 2>Know it, well, at least the beginning of the end anyway,

320
00:17:18.319 --> 00:17:21.039
<v Speaker 2>the beginning of the end. Right, So there you go. Okay,

321
00:17:21.160 --> 00:17:24.359
<v Speaker 2>so I guess we should get onto better no framework awesome,

322
00:17:33.160 --> 00:17:36.680
<v Speaker 2>So our friend Simon Kropi, Simon, you're us. He's the

323
00:17:36.720 --> 00:17:38.839
<v Speaker 2>guy who said, you guys should get Rob Menching back

324
00:17:38.920 --> 00:17:43.319
<v Speaker 2>for you know, a one year update on open source monetization,

325
00:17:44.039 --> 00:17:46.359
<v Speaker 2>and we said sure, so that's why he's here. But

326
00:17:46.519 --> 00:17:49.920
<v Speaker 2>he also says, hey, have you seen geo convert And

327
00:17:49.960 --> 00:17:54.720
<v Speaker 2>I said, no, what's g convert? Geoconvert maps between gjson, topo,

328
00:17:54.880 --> 00:18:01.640
<v Speaker 2>json flat, g O buff kml, kmz, gpx, wkt, wkb CSV,

329
00:18:01.799 --> 00:18:09.839
<v Speaker 2>and gopark mousc entirely in your browser. So all of

330
00:18:09.880 --> 00:18:13.160
<v Speaker 2>the formats for geographical data.

331
00:18:13.480 --> 00:18:16.599
<v Speaker 1>Yeah, okay, yeah, all in the browser. So you basically

332
00:18:16.960 --> 00:18:18.680
<v Speaker 1>choose a map file, upload.

333
00:18:18.359 --> 00:18:20.839
<v Speaker 2>It, boom convert, and then you can dump it back

334
00:18:20.839 --> 00:18:24.160
<v Speaker 2>out in whatever other format I want it. Yeah, that's magic,

335
00:18:24.839 --> 00:18:26.200
<v Speaker 2>of course it is. It's awesome.

336
00:18:26.279 --> 00:18:28.960
<v Speaker 1>Yeah, Richard, who's talking to us today?

337
00:18:29.119 --> 00:18:32.319
<v Speaker 2>Gret A comments off a show nineteen forty eight, that's

338
00:18:32.359 --> 00:18:35.119
<v Speaker 2>one where we talked about this open source maintenance fee

339
00:18:35.119 --> 00:18:38.039
<v Speaker 2>with some Rob guy. And there's a lot of comments

340
00:18:38.039 --> 00:18:40.400
<v Speaker 2>on the show, honestly, and Rob responded to most of them.

341
00:18:40.480 --> 00:18:43.319
<v Speaker 2>Thank you, Rob. That was very kind of you because

342
00:18:43.359 --> 00:18:45.440
<v Speaker 2>people are clearly excited and interested, and I think this

343
00:18:45.480 --> 00:18:48.000
<v Speaker 2>recap's a really good idea, but here's one we didn't

344
00:18:48.039 --> 00:18:49.839
<v Speaker 2>get a response to, and I thought we might take

345
00:18:49.839 --> 00:18:52.599
<v Speaker 2>it on a little bit. Chris blithe and get asking

346
00:18:52.640 --> 00:18:54.519
<v Speaker 2>this about a year ago. I just listened to the show.

347
00:18:54.559 --> 00:18:56.880
<v Speaker 2>The one thing I don't understand and we'd love to

348
00:18:56.920 --> 00:18:59.279
<v Speaker 2>hear Robs feel on it. What would be stopping a

349
00:18:59.319 --> 00:19:02.279
<v Speaker 2>big organization just automatically building your open source repo on

350
00:19:02.359 --> 00:19:04.599
<v Speaker 2>their build server and pushing their art effects to their

351
00:19:04.599 --> 00:19:07.359
<v Speaker 2>internal feed and therefore you get all the project management

352
00:19:07.359 --> 00:19:10.480
<v Speaker 2>stuff and security updates, but just not ready to go binary.

353
00:19:11.359 --> 00:19:13.559
<v Speaker 2>Let's be honest, setting up an automate build is pretty

354
00:19:13.599 --> 00:19:15.160
<v Speaker 2>low in terms of effort and would be you know,

355
00:19:15.200 --> 00:19:17.319
<v Speaker 2>fit in the short term bracket or is there some

356
00:19:17.720 --> 00:19:21.000
<v Speaker 2>secret way for maintainers to stop that from happening. I

357
00:19:21.000 --> 00:19:22.640
<v Speaker 2>don't think there's any way to stop that from happening,

358
00:19:22.640 --> 00:19:25.039
<v Speaker 2>and I think that's the way most organizations actually do

359
00:19:25.119 --> 00:19:26.000
<v Speaker 2>things by design.

360
00:19:26.240 --> 00:19:29.599
<v Speaker 4>No, I don't know that many organizations do that, but

361
00:19:29.680 --> 00:19:32.920
<v Speaker 4>it absolutely is by design that they can't.

362
00:19:33.039 --> 00:19:33.519
<v Speaker 1>Yeah.

363
00:19:33.599 --> 00:19:36.480
<v Speaker 2>Yeah, I mean I've seen both things where your build

364
00:19:36.519 --> 00:19:39.160
<v Speaker 2>process actually goes and fetches the bit from the open

365
00:19:39.200 --> 00:19:42.039
<v Speaker 2>source repository and continues on. I've also seen versions where

366
00:19:42.319 --> 00:19:45.640
<v Speaker 2>they maintain a local repository and decide when to push

367
00:19:45.640 --> 00:19:48.559
<v Speaker 2>new versions in and everybody builds off of that. But

368
00:19:48.759 --> 00:19:51.319
<v Speaker 2>I don't think that takes anything away from the open

369
00:19:51.359 --> 00:19:52.839
<v Speaker 2>source maintainer or the project.

370
00:19:53.039 --> 00:19:53.119
<v Speaker 3>No.

371
00:19:53.599 --> 00:19:57.519
<v Speaker 4>His point is, I bet you can do this under

372
00:19:57.559 --> 00:20:00.680
<v Speaker 4>two hours, right, and take care of it. And that

373
00:20:00.720 --> 00:20:03.440
<v Speaker 4>two hours is two hours per year is the cost.

374
00:20:03.559 --> 00:20:06.519
<v Speaker 4>We're talking costs the maintenance feedback then, and that's that's

375
00:20:06.599 --> 00:20:10.079
<v Speaker 4>two hours per year. And depending on the project and

376
00:20:10.160 --> 00:20:11.359
<v Speaker 4>what you have to do and what you have to

377
00:20:11.440 --> 00:20:14.759
<v Speaker 4>keep up on, it might be two hours, it might

378
00:20:14.799 --> 00:20:18.079
<v Speaker 4>be more than that, but it's absolutely more mind to

379
00:20:18.119 --> 00:20:22.400
<v Speaker 4>share that you have absorbed into the company, right, and

380
00:20:22.440 --> 00:20:27.000
<v Speaker 4>we'll talk about it. But most people don't think that

381
00:20:27.039 --> 00:20:29.599
<v Speaker 4>way about the open source projects, which is why the

382
00:20:29.599 --> 00:20:31.720
<v Speaker 4>open source maintenance fee is working.

383
00:20:32.279 --> 00:20:34.039
<v Speaker 2>Yeah, so's.

384
00:20:38.680 --> 00:20:42.000
<v Speaker 4>Talk about because it's it's but he's right, he's absolutely right.

385
00:20:42.039 --> 00:20:44.440
<v Speaker 4>You could absolutely do all that. That's by design. That's

386
00:20:44.480 --> 00:20:47.359
<v Speaker 4>fantastic because the idea is then hey, you're in the code,

387
00:20:47.400 --> 00:20:49.920
<v Speaker 4>you're helping, you're being in there. There's more people then

388
00:20:49.960 --> 00:20:53.119
<v Speaker 4>that are working at that level. Fantastic, You're maintaining the

389
00:20:53.160 --> 00:20:55.599
<v Speaker 4>source code. There you go. Good job, but it's not

390
00:20:55.720 --> 00:20:56.160
<v Speaker 4>very common.

391
00:20:56.200 --> 00:20:58.200
<v Speaker 2>Awesome, So Chris, thank you so much for comment in

392
00:20:58.240 --> 00:20:59.400
<v Speaker 2>a copy of music co buy. It is on its

393
00:20:59.440 --> 00:21:00.519
<v Speaker 2>way to you. And if you like a copy of

394
00:21:00.559 --> 00:21:02.079
<v Speaker 2>music cob buy, I write a comment on the website

395
00:21:02.079 --> 00:21:03.880
<v Speaker 2>at dot NetRocks dot com or on the facebooks. We

396
00:21:03.920 --> 00:21:05.599
<v Speaker 2>publish every show there and if you comment there and

397
00:21:05.599 --> 00:21:07.319
<v Speaker 2>never read on the show, we'll send you a copy

398
00:21:07.319 --> 00:21:07.960
<v Speaker 2>of music Coby.

399
00:21:08.079 --> 00:21:09.759
<v Speaker 1>And if you don't want to do that, you can

400
00:21:09.839 --> 00:21:12.559
<v Speaker 1>just go get it yourself. Music too, code by dot net.

401
00:21:12.759 --> 00:21:16.160
<v Speaker 1>It's twenty two tracks of twenty five minutes long of

402
00:21:16.720 --> 00:21:20.319
<v Speaker 1>music that is scientifically designed to keep you in a

403
00:21:20.359 --> 00:21:26.359
<v Speaker 1>state of flow for focus, relaxing, and particularly coding. So

404
00:21:28.079 --> 00:21:31.200
<v Speaker 1>that voice you heard before was Rob Mentioning. He is

405
00:21:31.240 --> 00:21:33.799
<v Speaker 1>the CEO and co founder of fire Giant, a company

406
00:21:33.799 --> 00:21:36.960
<v Speaker 1>that provides commercial support and tools for the Wicks tool set.

407
00:21:37.319 --> 00:21:40.200
<v Speaker 1>He's also the creator and maintainer of Wicks, the most

408
00:21:40.279 --> 00:21:44.359
<v Speaker 1>powerful set of tools for building Windows installation packages. Wicks

409
00:21:44.440 --> 00:21:47.319
<v Speaker 1>holds the unique distinction of being the first open source

410
00:21:47.359 --> 00:21:51.279
<v Speaker 1>project released by Microsoft, and Rob has been deeply involved

411
00:21:51.279 --> 00:21:55.039
<v Speaker 1>in open source for over twenty five years. He's passionate

412
00:21:55.079 --> 00:21:59.279
<v Speaker 1>about making open source sustainable and his proposal of the

413
00:21:59.319 --> 00:22:01.799
<v Speaker 1>open source maintenance Fee. I guess it's not a proposal now,

414
00:22:01.839 --> 00:22:05.079
<v Speaker 1>but it's the thing. The open source maintenance Fee is

415
00:22:05.160 --> 00:22:07.799
<v Speaker 1>all about creating a better path forward for projects and

416
00:22:07.839 --> 00:22:10.559
<v Speaker 1>their maintainers. Welcome back, Rob, and I guess you gave

417
00:22:10.559 --> 00:22:12.119
<v Speaker 1>away the end. It seems to be working.

418
00:22:12.480 --> 00:22:15.519
<v Speaker 4>Yeah, but there's a lot of things still to talk about. Sure,

419
00:22:15.559 --> 00:22:19.240
<v Speaker 4>and it's working for us. I don't know, there's a

420
00:22:19.319 --> 00:22:22.079
<v Speaker 4>lot to talk about. There's a lot of details to it.

421
00:22:22.119 --> 00:22:22.960
<v Speaker 4>I think we should say it.

422
00:22:23.160 --> 00:22:23.839
<v Speaker 2>Started the beginning.

423
00:22:23.839 --> 00:22:23.960
<v Speaker 3>Then.

424
00:22:24.240 --> 00:22:26.359
<v Speaker 2>I don't know that everybody listened to the last show,

425
00:22:26.359 --> 00:22:27.079
<v Speaker 2>although they should.

426
00:22:27.480 --> 00:22:28.920
<v Speaker 4>How far back do you want to go? Do you

427
00:22:28.920 --> 00:22:30.359
<v Speaker 4>want the motivation or what it is?

428
00:22:32.079 --> 00:22:33.119
<v Speaker 1>The elevator pitch, and.

429
00:22:33.440 --> 00:22:36.920
<v Speaker 4>We'll do the elevator pitch. There was a time back

430
00:22:36.960 --> 00:22:41.279
<v Speaker 4>in two thousand and twenty four that we were starting

431
00:22:41.319 --> 00:22:47.480
<v Speaker 4>to see a escalation of pressure on open source maintainers

432
00:22:47.480 --> 00:22:50.880
<v Speaker 4>that turned into for me, the catalyst was the exe

433
00:22:51.079 --> 00:22:56.200
<v Speaker 4>utls attack, where we now believe state actors pressured a

434
00:22:56.319 --> 00:23:00.559
<v Speaker 4>single maintainer into giving access to one of them so

435
00:23:00.640 --> 00:23:04.319
<v Speaker 4>they could insert a very very subtle build system flaw

436
00:23:04.839 --> 00:23:08.559
<v Speaker 4>or not flaw attack into Linux, which then snuck its

437
00:23:08.559 --> 00:23:15.599
<v Speaker 4>way into almost everywhere until some engineer at Microsoft happened

438
00:23:15.599 --> 00:23:18.640
<v Speaker 4>to notice things were running a little slow and went, hey,

439
00:23:18.720 --> 00:23:19.519
<v Speaker 4>this seems.

440
00:23:19.200 --> 00:23:22.759
<v Speaker 2>Like a problem, and lil So was like half a second,

441
00:23:24.920 --> 00:23:25.400
<v Speaker 2>I don't.

442
00:23:25.240 --> 00:23:27.519
<v Speaker 4>Know how you find it if he was doing very

443
00:23:27.559 --> 00:23:30.200
<v Speaker 4>sensitive performance testing. So that's like the only was it. Yes,

444
00:23:30.319 --> 00:23:31.559
<v Speaker 4>that thing could have been in. You would have a

445
00:23:31.599 --> 00:23:35.240
<v Speaker 4>backdoor into all Linux, including those on the clouds. And

446
00:23:35.480 --> 00:23:39.839
<v Speaker 4>where that goes is crazy. That happens, That's very exciting.

447
00:23:40.000 --> 00:23:42.240
<v Speaker 4>That's like the things that you know Jason Bourne novels

448
00:23:42.279 --> 00:23:44.799
<v Speaker 4>are done about or whatever. I was more interested in

449
00:23:44.839 --> 00:23:47.680
<v Speaker 4>the people because at that point me, like many of

450
00:23:47.680 --> 00:23:50.200
<v Speaker 4>my friends, were very frustrated. And if you listen to

451
00:23:50.200 --> 00:23:52.279
<v Speaker 4>that episode, which I did, I went back and listen

452
00:23:52.279 --> 00:23:55.480
<v Speaker 4>to it, you can hear the frustration, I think in

453
00:23:55.599 --> 00:24:00.559
<v Speaker 4>my voice a bit. And I was just like that

454
00:24:00.720 --> 00:24:03.319
<v Speaker 4>incident kind of said enough is enough, We're going to

455
00:24:03.400 --> 00:24:05.759
<v Speaker 4>solve this problem. I'm at least going to take a

456
00:24:05.759 --> 00:24:09.920
<v Speaker 4>shot at it. So over the next well not quite

457
00:24:09.960 --> 00:24:12.400
<v Speaker 4>a year, six months for the summer for sure, into

458
00:24:12.440 --> 00:24:15.480
<v Speaker 4>the fall, and then early twenty twenty five came up

459
00:24:15.519 --> 00:24:19.160
<v Speaker 4>with this idea called the open source maintenance fee that says,

460
00:24:19.799 --> 00:24:22.200
<v Speaker 4>there's an open source project, which means that all the

461
00:24:22.240 --> 00:24:25.319
<v Speaker 4>source code is available under the licenses that we know

462
00:24:25.519 --> 00:24:29.480
<v Speaker 4>very well from the OSI that specify how you can

463
00:24:29.920 --> 00:24:33.839
<v Speaker 4>share and access that source code, and they are generally

464
00:24:33.920 --> 00:24:36.359
<v Speaker 4>very liberal, definitely on the part that you can see

465
00:24:36.400 --> 00:24:40.279
<v Speaker 4>the source code. Then what if we added this very

466
00:24:40.319 --> 00:24:44.200
<v Speaker 4>common concept, a ula to the binaries the things that

467
00:24:44.240 --> 00:24:47.240
<v Speaker 4>get built from that source code from the project maintainers.

468
00:24:47.559 --> 00:24:50.000
<v Speaker 4>And the maintainers could say, hey, I'm going to put

469
00:24:50.039 --> 00:24:51.920
<v Speaker 4>a ULA on this because I spend a lot of

470
00:24:51.920 --> 00:24:55.319
<v Speaker 4>time building these projects, keeping them up to date, keeping

471
00:24:55.359 --> 00:24:58.960
<v Speaker 4>the issue tracker free from spam, maybe answering questions, answering

472
00:24:59.039 --> 00:25:01.599
<v Speaker 4>questions all over the place, keeping doctations like this long

473
00:25:01.640 --> 00:25:06.000
<v Speaker 4>list of things that all maintainers do. So how about

474
00:25:06.000 --> 00:25:09.839
<v Speaker 4>we have a small fee that we charge people compensation

475
00:25:10.160 --> 00:25:12.960
<v Speaker 4>for all of those tasks that a maintainers do. And

476
00:25:13.000 --> 00:25:16.160
<v Speaker 4>this idea was at that time for me very scary

477
00:25:17.000 --> 00:25:19.240
<v Speaker 4>when we were talking about a year ago, and now

478
00:25:19.279 --> 00:25:22.039
<v Speaker 4>I'm just like, yeah, this is this makes so much sense.

479
00:25:22.039 --> 00:25:23.400
<v Speaker 4>We should just do this. And so that's why I'm

480
00:25:23.400 --> 00:25:25.599
<v Speaker 4>really glad to be talking to you guys again about

481
00:25:25.640 --> 00:25:29.880
<v Speaker 4>the idea of the source code is open source. The

482
00:25:29.880 --> 00:25:33.960
<v Speaker 4>binaries that come from it are protected, not protected, are

483
00:25:34.000 --> 00:25:38.599
<v Speaker 4>licensed under a separate eula, and that separation creates a

484
00:25:38.640 --> 00:25:43.480
<v Speaker 4>space where we can have maintainers become sustainable, that they

485
00:25:43.519 --> 00:25:46.880
<v Speaker 4>can actually find a place where hey, because there's companies

486
00:25:47.039 --> 00:25:50.319
<v Speaker 4>paying for the maintenance fees, they can actually work on

487
00:25:50.359 --> 00:25:53.680
<v Speaker 4>the project and stay involved in projects that might be

488
00:25:54.039 --> 00:25:57.759
<v Speaker 4>wearing them down after all these interactions with people that

489
00:25:58.240 --> 00:26:02.400
<v Speaker 4>have assumed that all of their interactions with them are free, right.

490
00:26:02.519 --> 00:26:04.720
<v Speaker 2>Yeah, And this is back to Chris's comment at the

491
00:26:04.759 --> 00:26:07.519
<v Speaker 2>top of the show here where hey, if just so

492
00:26:07.559 --> 00:26:10.000
<v Speaker 2>avoid the binary, do I have no obligation? And it's

493
00:26:10.079 --> 00:26:12.160
<v Speaker 2>like always never about that in the first place.

494
00:26:12.200 --> 00:26:15.720
<v Speaker 4>Really, yeah, And if you enter at the source code level,

495
00:26:15.759 --> 00:26:17.960
<v Speaker 4>you're entering in a different place. Sure, right, If you're

496
00:26:17.960 --> 00:26:20.799
<v Speaker 4>in there and you're starting to working there, you're generally

497
00:26:20.799 --> 00:26:23.000
<v Speaker 4>look at the code and now you're becoming part of

498
00:26:23.000 --> 00:26:26.960
<v Speaker 4>the community that you're actually moving forward this project. What

499
00:26:27.079 --> 00:26:29.240
<v Speaker 4>the space that I found were the people on top

500
00:26:29.640 --> 00:26:33.079
<v Speaker 4>that were just using the binaries straight out and then expecting,

501
00:26:33.160 --> 00:26:36.079
<v Speaker 4>like my favorite example is there's this bug that's been

502
00:26:36.079 --> 00:26:38.599
<v Speaker 4>over for ten years. How have you not fixed this

503
00:26:38.720 --> 00:26:40.039
<v Speaker 4>bug in ten years?

504
00:26:40.279 --> 00:26:43.519
<v Speaker 2>Right? Yeah, I'm going to uninstall this free product.

505
00:26:43.240 --> 00:26:46.119
<v Speaker 4>Okay exactly. And then they're like and then maybe you

506
00:26:46.160 --> 00:26:48.359
<v Speaker 4>maybe as a maintainer, you're like, look, oh, man, I

507
00:26:48.400 --> 00:26:50.440
<v Speaker 4>love my project. You're right, it's been ten years. I'll

508
00:26:50.440 --> 00:26:52.440
<v Speaker 4>go back and look at that. They spend the time

509
00:26:52.680 --> 00:26:54.880
<v Speaker 4>they fix it, and then they're in there, and then

510
00:26:54.880 --> 00:26:57.480
<v Speaker 4>the person saying, well, how long until you get the

511
00:26:57.559 --> 00:27:00.759
<v Speaker 4>build out? Like where's the build Why isn't that available

512
00:27:00.799 --> 00:27:03.359
<v Speaker 4>right now? And it's like, well, I have to just

513
00:27:03.440 --> 00:27:05.359
<v Speaker 4>go through all the work and all those sorts of things. Yeah,

514
00:27:05.400 --> 00:27:06.519
<v Speaker 4>it's that whole space.

515
00:27:06.920 --> 00:27:09.799
<v Speaker 2>Yeah, yeah, it's and it's it is a bund It

516
00:27:09.920 --> 00:27:12.079
<v Speaker 2>sure feels like a bunch of ungrateful wretches, you know,

517
00:27:12.240 --> 00:27:15.599
<v Speaker 2>when they're at that level the angry issues of whis

518
00:27:15.640 --> 00:27:17.880
<v Speaker 2>are not a built version of this. Why I don't

519
00:27:17.880 --> 00:27:20.640
<v Speaker 2>want source code like that drives me crazy too.

520
00:27:21.039 --> 00:27:24.240
<v Speaker 4>Yeah. And it's when you become a successful project. We

521
00:27:24.279 --> 00:27:26.480
<v Speaker 4>talked to us a little bit last time, that you

522
00:27:26.599 --> 00:27:29.759
<v Speaker 4>end up with a lot of people in your project. Yeah,

523
00:27:29.920 --> 00:27:32.240
<v Speaker 4>very successful projects like you know, the wig tool sets

524
00:27:32.240 --> 00:27:34.920
<v Speaker 4>getting millions like we're up to the almost twenty million

525
00:27:35.200 --> 00:27:39.359
<v Speaker 4>downloads of our various parts, the primary entry points. There's

526
00:27:39.400 --> 00:27:42.400
<v Speaker 4>like twenty million downloads almost. That's a lot of people

527
00:27:42.400 --> 00:27:43.599
<v Speaker 4>that have been used in that product.

528
00:27:43.680 --> 00:27:43.759
<v Speaker 1>Right.

529
00:27:44.000 --> 00:27:47.960
<v Speaker 4>It's cut product project, It's complex, it has lots of

530
00:27:48.039 --> 00:27:50.720
<v Speaker 4>parts moving around in it, and you can get people

531
00:27:50.799 --> 00:27:55.319
<v Speaker 4>that I think, it's just free and it really just

532
00:27:55.359 --> 00:27:59.119
<v Speaker 4>keeps coming back to that same place of the attitudes

533
00:27:59.160 --> 00:28:00.960
<v Speaker 4>as opposed to being part of a community and working

534
00:28:01.039 --> 00:28:04.200
<v Speaker 4>on it and helping and participating. People just show up

535
00:28:04.279 --> 00:28:07.519
<v Speaker 4>and ask their question and want an answer and download EBITs.

536
00:28:07.519 --> 00:28:10.759
<v Speaker 1>You could buy an answer. Well, so would you like

537
00:28:10.759 --> 00:28:11.680
<v Speaker 1>to buy an answer?

538
00:28:11.920 --> 00:28:13.960
<v Speaker 4>Well, you know, and this is the other thing that

539
00:28:14.400 --> 00:28:17.680
<v Speaker 4>there are. There are business models that people will then

540
00:28:17.720 --> 00:28:19.839
<v Speaker 4>tell you, well, if you want to do open source,

541
00:28:19.839 --> 00:28:21.920
<v Speaker 4>then you should, you know, create a company, go create

542
00:28:21.960 --> 00:28:25.240
<v Speaker 4>a service company around it, where maybe you offer support,

543
00:28:25.559 --> 00:28:28.640
<v Speaker 4>or you offer other additional features on top of it,

544
00:28:29.119 --> 00:28:31.720
<v Speaker 4>or maybe you do consulting and you go customize it,

545
00:28:31.799 --> 00:28:33.319
<v Speaker 4>work it with other people things like that.

546
00:28:33.359 --> 00:28:36.519
<v Speaker 1>For you get on a short list of people who

547
00:28:36.680 --> 00:28:40.920
<v Speaker 1>you can, you know, take their suggestions and make customizations

548
00:28:40.960 --> 00:28:41.599
<v Speaker 1>for right.

549
00:28:41.880 --> 00:28:43.960
<v Speaker 4>However you want to do that, The challenge all those

550
00:28:44.079 --> 00:28:47.039
<v Speaker 4>are You're now putting together a business, right and there's

551
00:28:47.079 --> 00:28:49.000
<v Speaker 4>a lot of maintainers that are like, my project is

552
00:28:49.039 --> 00:28:51.519
<v Speaker 4>only so big and I don't necessarily want to put

553
00:28:51.559 --> 00:28:54.279
<v Speaker 4>together a whole business behind it. So is there a

554
00:28:54.359 --> 00:28:57.720
<v Speaker 4>space for me? The challenge was can we find something

555
00:28:57.759 --> 00:29:00.599
<v Speaker 4>in there that meets those maintainers that are starting to

556
00:29:00.599 --> 00:29:03.960
<v Speaker 4>get burned out on their project that they don't have

557
00:29:04.039 --> 00:29:06.279
<v Speaker 4>to go and say I'm going to quit my job

558
00:29:06.440 --> 00:29:09.400
<v Speaker 4>and create a whole business around this. And that was

559
00:29:09.440 --> 00:29:11.279
<v Speaker 4>one of the key characteristics that I want to make

560
00:29:11.279 --> 00:29:13.119
<v Speaker 4>sure that we can meet in that space.

561
00:29:13.319 --> 00:29:17.440
<v Speaker 1>So how does the open source maintenancee work exactly right now?

562
00:29:18.079 --> 00:29:21.559
<v Speaker 4>The easiest way to put it together that has worked

563
00:29:21.559 --> 00:29:24.799
<v Speaker 4>out really well is we kind of co opt to

564
00:29:24.839 --> 00:29:27.799
<v Speaker 4>Gethub sponsors, And turns out GitHub has been a really

565
00:29:27.839 --> 00:29:32.319
<v Speaker 4>good partner through all of this. And like I said,

566
00:29:32.319 --> 00:29:34.920
<v Speaker 4>the idea was to not have to create an entire company.

567
00:29:35.079 --> 00:29:40.279
<v Speaker 4>So with GitHub sponsors, you can set up your fuduciary

568
00:29:40.920 --> 00:29:44.680
<v Speaker 4>connection with GitHub and your bank account through Stripe. That's

569
00:29:44.720 --> 00:29:47.680
<v Speaker 4>a very easy thing to do as an individual. And

570
00:29:47.799 --> 00:29:52.079
<v Speaker 4>then you say, I'm going to offer the I'm going

571
00:29:52.119 --> 00:29:55.400
<v Speaker 4>to build the binaries for my project put a yula

572
00:29:55.480 --> 00:29:57.039
<v Speaker 4>on them, and we actually have a ula that you

573
00:29:57.079 --> 00:29:58.839
<v Speaker 4>can copy and paste out of the open source maintenance

574
00:29:58.839 --> 00:30:00.079
<v Speaker 4>fee if you want to just use that one and

575
00:30:01.119 --> 00:30:03.480
<v Speaker 4>put it up there. And then you say, you said

576
00:30:03.559 --> 00:30:06.000
<v Speaker 4>for your gid HOB sponsors to say here's the fee

577
00:30:06.039 --> 00:30:10.640
<v Speaker 4>that you pay and GETTHUB. Then we'll connect the payment

578
00:30:10.720 --> 00:30:14.119
<v Speaker 4>from the companies straight into your bank account, so you

579
00:30:14.160 --> 00:30:16.519
<v Speaker 4>don't have to do as a maintainer, you don't have

580
00:30:16.559 --> 00:30:19.200
<v Speaker 4>to do anything, but you know, a day's worth of work.

581
00:30:19.319 --> 00:30:21.039
<v Speaker 4>Generally you have to wait a little bit on the

582
00:30:21.039 --> 00:30:23.200
<v Speaker 4>bank stuff, but a day's worth of work to connect

583
00:30:23.240 --> 00:30:26.359
<v Speaker 4>all that things together. So it literally allows maintainers to

584
00:30:26.400 --> 00:30:30.000
<v Speaker 4>stand all of this up without standing up a whole

585
00:30:30.000 --> 00:30:32.440
<v Speaker 4>lot of infrastructure by building on top of GitHub sponsors.

586
00:30:32.680 --> 00:30:34.839
<v Speaker 1>It's great. And this is this is something that I

587
00:30:34.920 --> 00:30:39.119
<v Speaker 1>kind of suggested back in twenty twenty two when we

588
00:30:39.119 --> 00:30:42.680
<v Speaker 1>were at NBC talking about making open source work for

589
00:30:42.720 --> 00:30:46.400
<v Speaker 1>everyone with David Whitney episode eighteen eighteen, and you know,

590
00:30:46.440 --> 00:30:49.240
<v Speaker 1>we were just talking about that whole problem of open

591
00:30:49.279 --> 00:30:51.599
<v Speaker 1>source maintainers need to get paid somehow, and I think

592
00:30:51.640 --> 00:30:55.240
<v Speaker 1>I suggested that we did it through maybe I suggested

593
00:30:55.319 --> 00:30:58.079
<v Speaker 1>new Get. I think it was new Get that I suggested, you.

594
00:30:58.039 --> 00:31:00.640
<v Speaker 4>Know, I think you said you said get up. Someone

595
00:31:00.720 --> 00:31:02.519
<v Speaker 4>else said nugot. I think I think it was Dave

596
00:31:02.559 --> 00:31:05.839
<v Speaker 4>Whitney maybe someone that has recommended nugat.

597
00:31:06.680 --> 00:31:09.319
<v Speaker 1>But we were talking about this, this whole idea.

598
00:31:09.119 --> 00:31:12.880
<v Speaker 4>Yes, this idea yeah. And the trick though, was in

599
00:31:12.920 --> 00:31:15.640
<v Speaker 4>the past sponsors and all these conversations have been around

600
00:31:15.640 --> 00:31:17.759
<v Speaker 4>it would be nice if you pay. It should be

601
00:31:17.839 --> 00:31:20.680
<v Speaker 4>nice if you could put a donation, a tip jar,

602
00:31:20.920 --> 00:31:24.920
<v Speaker 4>something like that. The important facet that has worked out

603
00:31:25.200 --> 00:31:29.680
<v Speaker 4>really well in the open source maintenance fee is the EULA,

604
00:31:29.079 --> 00:31:33.200
<v Speaker 4>the fact that it's not optional, it's not a donation,

605
00:31:33.480 --> 00:31:37.839
<v Speaker 4>it's not charity, and that actually activates everything that you

606
00:31:37.960 --> 00:31:41.079
<v Speaker 4>need to inside the companies, because if it's a charity

607
00:31:41.119 --> 00:31:46.920
<v Speaker 4>or a donation, the story usually goes, I'm an employee,

608
00:31:46.920 --> 00:31:48.640
<v Speaker 4>I think we should you know, we use this project.

609
00:31:48.720 --> 00:31:51.519
<v Speaker 4>Let's go sponsor it. You will hit eventually a procurement

610
00:31:51.559 --> 00:31:53.640
<v Speaker 4>team that goes, do we have to spend money on this?

611
00:31:53.960 --> 00:31:56.519
<v Speaker 4>The answer is no, and the procurement team says great,

612
00:31:57.279 --> 00:32:02.480
<v Speaker 4>no answer. So now, but with a EULA, then the

613
00:32:02.599 --> 00:32:06.119
<v Speaker 4>ULA says, here are the terms legal goes yep, those

614
00:32:06.160 --> 00:32:09.000
<v Speaker 4>are the terms. Procurement goes great, how do we pay it?

615
00:32:09.400 --> 00:32:11.880
<v Speaker 4>And you say great, go to GitHub sponsors and pay

616
00:32:11.920 --> 00:32:16.000
<v Speaker 4>it there. Now, when we launched this we talked to

617
00:32:16.440 --> 00:32:18.640
<v Speaker 4>last year. It was still brand new. I think I'd

618
00:32:18.640 --> 00:32:20.039
<v Speaker 4>only talked to you guys. They had only been out

619
00:32:20.039 --> 00:32:23.279
<v Speaker 4>a week and it was like May yeah, yeah, and

620
00:32:23.359 --> 00:32:25.759
<v Speaker 4>I was. It was early enough that I was afraid

621
00:32:25.839 --> 00:32:27.640
<v Speaker 4>to say what was going to happen. I had a

622
00:32:27.680 --> 00:32:29.359
<v Speaker 4>whole lot of hopes, I had a lot of ideas

623
00:32:29.440 --> 00:32:31.920
<v Speaker 4>was good, but I also know but I was also

624
00:32:31.960 --> 00:32:34.079
<v Speaker 4>confident that there was going to be bugs right, There

625
00:32:34.079 --> 00:32:36.480
<v Speaker 4>are things that I needed to work out. And so

626
00:32:36.839 --> 00:32:39.599
<v Speaker 4>the tool set being my project means I could put

627
00:32:39.599 --> 00:32:44.559
<v Speaker 4>it in a real project with real users and absorb

628
00:32:44.680 --> 00:32:48.119
<v Speaker 4>all of the growing pains just the initial launch, right

629
00:32:48.119 --> 00:32:50.400
<v Speaker 4>because I treated it just like a product, Pull the

630
00:32:50.400 --> 00:32:53.000
<v Speaker 4>bugs in, resolve them. So like the fact got built

631
00:32:53.079 --> 00:32:56.680
<v Speaker 4>up from every single question that people asked. One of

632
00:32:56.720 --> 00:33:02.680
<v Speaker 4>the trickier ones was get hub sponsors when it launched,

633
00:33:02.759 --> 00:33:05.000
<v Speaker 4>And this is my mistake. I didn't catch this detail

634
00:33:05.519 --> 00:33:08.519
<v Speaker 4>when we put it out there to pay by invoice,

635
00:33:08.559 --> 00:33:10.599
<v Speaker 4>which is what all major companies want to do. They

636
00:33:10.640 --> 00:33:12.880
<v Speaker 4>all want to pay by invoice, require you to pay

637
00:33:13.319 --> 00:33:17.000
<v Speaker 4>five thousand dollars up front, so you had to in

638
00:33:17.039 --> 00:33:20.160
<v Speaker 4>your invoice, you had to invoice five thousand dollars, and

639
00:33:20.240 --> 00:33:23.839
<v Speaker 4>I think there was also a three year commitment to

640
00:33:23.960 --> 00:33:26.720
<v Speaker 4>doing that if you went through invoicing. And when you

641
00:33:26.759 --> 00:33:29.599
<v Speaker 4>think about if you're a small company and you're paying

642
00:33:29.640 --> 00:33:31.519
<v Speaker 4>ten bucks per month, one hundred and twenty bucks per

643
00:33:31.640 --> 00:33:34.400
<v Speaker 4>year five thousand dollars up front for five years, was like, I,

644
00:33:34.799 --> 00:33:36.640
<v Speaker 4>how many years do we have to go before we

645
00:33:36.680 --> 00:33:39.359
<v Speaker 4>finally pay off this chunk of change that we put

646
00:33:39.400 --> 00:33:42.680
<v Speaker 4>in to get hubbed? So I never really like I

647
00:33:42.720 --> 00:33:44.920
<v Speaker 4>talked him a little bit. I never quite understood their system.

648
00:33:44.960 --> 00:33:47.960
<v Speaker 4>It was something about trying to get charitable donations to

649
00:33:48.039 --> 00:33:51.160
<v Speaker 4>be recurring from bigger companies and have them have bigger

650
00:33:51.200 --> 00:33:53.799
<v Speaker 4>pools of money in there to spread abrout a bunch

651
00:33:53.839 --> 00:33:57.000
<v Speaker 4>of their projects. So it was very charity donation kind

652
00:33:57.000 --> 00:34:00.000
<v Speaker 4>of oriented, which of course doesn't work for what we want.

653
00:34:00.000 --> 00:34:02.200
<v Speaker 4>I wanted to use it here, and so they were

654
00:34:02.240 --> 00:34:06.519
<v Speaker 4>awesome and they created a whole extra invoicing system for

655
00:34:06.880 --> 00:34:10.199
<v Speaker 4>the open source maintenance fee. Wow, so you can now

656
00:34:10.280 --> 00:34:11.880
<v Speaker 4>just pay only your invoice.

657
00:34:11.559 --> 00:34:15.159
<v Speaker 1>Isn't the whole idea that you want to make using

658
00:34:15.199 --> 00:34:19.320
<v Speaker 1>an open source tool free for anyone who just wants

659
00:34:19.360 --> 00:34:22.239
<v Speaker 1>to kick the tires and run it. And then if

660
00:34:22.280 --> 00:34:25.679
<v Speaker 1>you start making money with your software project that we're

661
00:34:25.719 --> 00:34:28.400
<v Speaker 1>an integral part of, that's when the feed kicks in.

662
00:34:28.519 --> 00:34:29.280
<v Speaker 1>Is that in the yula?

663
00:34:29.440 --> 00:34:33.599
<v Speaker 4>Yeah? Yeah, so actually that was one of the bugs

664
00:34:33.599 --> 00:34:37.239
<v Speaker 4>that we had to fix as well. The first bug

665
00:34:37.440 --> 00:34:39.719
<v Speaker 4>was getting it so that people companies could pay by

666
00:34:39.719 --> 00:34:42.639
<v Speaker 4>invoice and get hub was great. It took a little bit,

667
00:34:42.679 --> 00:34:44.639
<v Speaker 4>but we got that they had to make coding changes

668
00:34:44.679 --> 00:34:46.119
<v Speaker 4>on their side for that to happen, so it was

669
00:34:46.199 --> 00:34:49.800
<v Speaker 4>great there. I bring this up because I really appreciate

670
00:34:49.880 --> 00:34:54.400
<v Speaker 4>what GitHub did to make that happen. Kidding, your issue

671
00:34:54.400 --> 00:34:57.159
<v Speaker 4>that you're bringing up is also interesting because your original

672
00:34:57.239 --> 00:35:00.800
<v Speaker 4>yula said that if you make money, you must pay

673
00:35:00.840 --> 00:35:03.639
<v Speaker 4>this maintenance fee, and it got us into an interesting

674
00:35:03.639 --> 00:35:07.559
<v Speaker 4>situation where there might be a someone that was just

675
00:35:07.639 --> 00:35:11.039
<v Speaker 4>getting started in their business and maybe they were making

676
00:35:11.119 --> 00:35:15.559
<v Speaker 4>like their first sale for five dollars or something like that,

677
00:35:15.800 --> 00:35:17.480
<v Speaker 4>and now they're like, great, and I use a whole

678
00:35:17.480 --> 00:35:20.400
<v Speaker 4>bunch of open source to build it. How Like I

679
00:35:20.519 --> 00:35:23.159
<v Speaker 4>now have to pay a fee. I'm going to go

680
00:35:23.239 --> 00:35:25.039
<v Speaker 4>negative for trying to do this, and that was never

681
00:35:25.079 --> 00:35:25.599
<v Speaker 4>the intention.

682
00:35:25.920 --> 00:35:30.000
<v Speaker 1>We got to set the bar to real money first, yeah,

683
00:35:30.119 --> 00:35:32.400
<v Speaker 1>right right right, So, and then the challenge is that

684
00:35:32.440 --> 00:35:34.679
<v Speaker 1>so we did I in so we released open source

685
00:35:34.719 --> 00:35:37.239
<v Speaker 1>maintenance fee one point one v one point one.

686
00:35:37.519 --> 00:35:39.320
<v Speaker 4>Like I said, it's a product. So it got versioned

687
00:35:39.800 --> 00:35:42.320
<v Speaker 4>and move the minimum bar up to you have to

688
00:35:42.320 --> 00:35:45.440
<v Speaker 4>make more than ten thousand dollars per year. It's still

689
00:35:45.480 --> 00:35:49.000
<v Speaker 4>really low. But the idea, hopefully was that one of

690
00:35:49.000 --> 00:35:52.360
<v Speaker 4>the important parts is if an open source project takes

691
00:35:52.360 --> 00:35:55.159
<v Speaker 4>a maintenance fee, they pay the maintenance fee for their

692
00:35:55.239 --> 00:35:58.920
<v Speaker 4>projects down the line. Because the one of the important

693
00:35:58.960 --> 00:36:01.679
<v Speaker 4>factors is you only pay the maintenance fee for the

694
00:36:01.719 --> 00:36:05.840
<v Speaker 4>projects that you use directly. You don't pay this like, oh,

695
00:36:06.039 --> 00:36:08.760
<v Speaker 4>every single project that I depend on in the project,

696
00:36:08.840 --> 00:36:09.719
<v Speaker 4>they depend on and so and.

697
00:36:09.800 --> 00:36:11.079
<v Speaker 1>So and so, right, the whole tree.

698
00:36:11.239 --> 00:36:14.239
<v Speaker 4>Only the ones that you chose, right, you picked them,

699
00:36:14.320 --> 00:36:16.000
<v Speaker 4>therefore you pay the maintenance fee to them.

700
00:36:16.079 --> 00:36:16.199
<v Speaker 3>Right.

701
00:36:16.320 --> 00:36:19.360
<v Speaker 4>But then when those maintenance those projects make a maintenance fee,

702
00:36:19.519 --> 00:36:21.880
<v Speaker 4>they then will pay their projects down the line. So

703
00:36:22.039 --> 00:36:25.000
<v Speaker 4>it hopefully works its way down the system. I haven't

704
00:36:25.039 --> 00:36:26.920
<v Speaker 4>seen a whole lot of projects adopted yet to know

705
00:36:26.960 --> 00:36:28.239
<v Speaker 4>how well it works down the same.

706
00:36:28.079 --> 00:36:31.519
<v Speaker 1>Trickle down economics. I think they call that in the eighties.

707
00:36:31.679 --> 00:36:36.760
<v Speaker 4>It is it is in the dot net ecosystem, which

708
00:36:36.760 --> 00:36:39.239
<v Speaker 4>is the one that I know really well. The dependency

709
00:36:39.239 --> 00:36:40.519
<v Speaker 4>trees don't tend to be very deep.

710
00:36:40.639 --> 00:36:40.840
<v Speaker 1>Yeah.

711
00:36:41.880 --> 00:36:44.320
<v Speaker 4>The one case that I can make is like x

712
00:36:44.400 --> 00:36:47.079
<v Speaker 4>unit is probably one of the most popular ones. That is,

713
00:36:47.559 --> 00:36:49.760
<v Speaker 4>like the Wix tool set uses x unit for some

714
00:36:49.800 --> 00:36:54.360
<v Speaker 4>of our testing systems. So we, you know, as part

715
00:36:54.360 --> 00:36:57.440
<v Speaker 4>of fire Giant, we pay x unit a fee, and

716
00:36:57.480 --> 00:36:59.880
<v Speaker 4>that's we just choose to They don't have a maintenance fee,

717
00:36:59.880 --> 00:37:02.760
<v Speaker 4>but we choose to say, hey, we're going to pretend

718
00:37:02.840 --> 00:37:05.760
<v Speaker 4>every dependency that we have we're making money on this project.

719
00:37:05.760 --> 00:37:08.519
<v Speaker 4>Therefore we are going to pay all of our dependencies.

720
00:37:08.559 --> 00:37:10.639
<v Speaker 4>And next unit is our I think it's the only

721
00:37:10.679 --> 00:37:14.800
<v Speaker 4>dependency that isn't a Microsoft dependency in wex, So we

722
00:37:14.920 --> 00:37:16.119
<v Speaker 4>pay that there.

723
00:37:16.199 --> 00:37:17.679
<v Speaker 2>All right, Well, don't we take a quick break for

724
00:37:17.760 --> 00:37:24.559
<v Speaker 2>these very important messages. Yeah, and we're back. It's dot

725
00:37:24.639 --> 00:37:27.440
<v Speaker 2>net rocks. I'merchard Campbelllet's call Franklin. Hey here at toppling

726
00:37:27.480 --> 00:37:32.159
<v Speaker 2>with Rob mentioned about the open source maintenance fee, and uh, Okay,

727
00:37:32.199 --> 00:37:34.360
<v Speaker 2>so you rev to one point one, you obviously learn

728
00:37:34.480 --> 00:37:37.039
<v Speaker 2>some things, but otherwise, how is it going if you

729
00:37:37.119 --> 00:37:38.360
<v Speaker 2>got some folks signed up?

730
00:37:38.480 --> 00:37:42.400
<v Speaker 4>Yeah, so it has completely changed my outlook on contributing

731
00:37:42.440 --> 00:37:44.159
<v Speaker 4>to my project completely.

732
00:37:44.199 --> 00:37:44.440
<v Speaker 2>Wow.

733
00:37:44.480 --> 00:37:48.119
<v Speaker 4>We went from no sponsors because we didn't take sponsors

734
00:37:48.199 --> 00:37:50.920
<v Speaker 4>before this, so we have a nice clean start to

735
00:37:51.280 --> 00:37:54.840
<v Speaker 4>now about a year later, and today I think we're

736
00:37:54.840 --> 00:37:59.519
<v Speaker 4>at like three hundred and eight wow wow sponsors, which

737
00:37:59.559 --> 00:38:04.400
<v Speaker 4>is I went digging could be the most, if not

738
00:38:04.519 --> 00:38:07.039
<v Speaker 4>one of the most sponsored projects on GitHub.

739
00:38:07.079 --> 00:38:07.360
<v Speaker 1>Wow.

740
00:38:08.280 --> 00:38:13.239
<v Speaker 4>Like it's there, aren't I compare. I've compared us to VTE,

741
00:38:13.559 --> 00:38:16.599
<v Speaker 4>which is the kind of turned into the default build

742
00:38:16.599 --> 00:38:19.960
<v Speaker 4>system of JavaScript. I don't know how better else to

743
00:38:19.960 --> 00:38:22.840
<v Speaker 4>describe it, but it's a massive project JavaScript typescript all

744
00:38:22.840 --> 00:38:25.119
<v Speaker 4>that being a huge space, lots of people depending on it,

745
00:38:25.320 --> 00:38:29.039
<v Speaker 4>created by even you who also created view guys brilliant.

746
00:38:29.280 --> 00:38:31.280
<v Speaker 4>I'm impressed by everything he does. And he had, like

747
00:38:32.079 --> 00:38:36.599
<v Speaker 4>their project had like sixty two sixty five people sponsoring it.

748
00:38:36.840 --> 00:38:37.199
<v Speaker 1>Wow.

749
00:38:37.519 --> 00:38:41.920
<v Speaker 4>So it is working exactly like we wanted.

750
00:38:42.119 --> 00:38:45.239
<v Speaker 2>You've plugged into this business mechanism that I think you

751
00:38:45.320 --> 00:38:47.039
<v Speaker 2>grappled it with a lot of other people didn't that

752
00:38:47.480 --> 00:38:50.800
<v Speaker 2>when you create this construct of it is an obligation

753
00:38:50.960 --> 00:38:54.679
<v Speaker 2>for a business using the binary to pay, They pay.

754
00:38:54.679 --> 00:38:57.519
<v Speaker 4>And they don't complaint the business is the only thing

755
00:38:57.559 --> 00:39:01.199
<v Speaker 4>they complain about is how we use getub sponsors to

756
00:39:01.199 --> 00:39:04.159
<v Speaker 4>do this because finding the invoice thing that we talked about,

757
00:39:04.239 --> 00:39:07.119
<v Speaker 4>how yes, it's it's purely a how do we pay?

758
00:39:07.199 --> 00:39:11.360
<v Speaker 4>Not why or do we have to? It's purely a

759
00:39:11.519 --> 00:39:14.320
<v Speaker 4>what is the mechanism by which we put the money

760
00:39:14.320 --> 00:39:16.119
<v Speaker 4>into the right place? Because we just want to solve

761
00:39:16.119 --> 00:39:21.960
<v Speaker 4>this problem and streamlining that is probably the biggest problem

762
00:39:22.280 --> 00:39:27.119
<v Speaker 4>to tackle. When I first announced this idea, everybody said,

763
00:39:27.159 --> 00:39:29.039
<v Speaker 4>how are you going to enforce this? Even Carl brought

764
00:39:29.039 --> 00:39:30.960
<v Speaker 4>it up, like how are you going to force people

765
00:39:31.519 --> 00:39:35.199
<v Speaker 4>to do this? And I was like, well, our primary

766
00:39:35.239 --> 00:39:38.519
<v Speaker 4>focus is education first. Because's brand new, all those sorts

767
00:39:38.519 --> 00:39:38.960
<v Speaker 4>of challenges.

768
00:39:39.000 --> 00:39:41.239
<v Speaker 1>It's kind of like a Grateful Dead show. You know,

769
00:39:41.920 --> 00:39:44.920
<v Speaker 1>you can tape it, go ahead, We're not going to cool.

770
00:39:45.039 --> 00:39:47.360
<v Speaker 4>I didn't know that about Grateful Dead, but yeah it.

771
00:39:48.440 --> 00:39:52.559
<v Speaker 1>So they're all dead now, so grate Yeah.

772
00:39:52.599 --> 00:39:56.199
<v Speaker 4>So on that front, it worked perfectly in that it

773
00:39:56.360 --> 00:39:58.840
<v Speaker 4>got it for it. We did get the feedback that

774
00:39:59.039 --> 00:40:04.440
<v Speaker 4>there was no notification that the EULA had changed. And

775
00:40:04.480 --> 00:40:06.480
<v Speaker 4>when we talked about before, I said, we have this

776
00:40:06.599 --> 00:40:09.679
<v Speaker 4>perfect mechanism in nugat packages, which Wix happens to be

777
00:40:09.840 --> 00:40:12.960
<v Speaker 4>all shipp through nugat packages that you can say requires

778
00:40:13.000 --> 00:40:16.679
<v Speaker 4>license acceptance. It's a bit in the nugit manifest and

779
00:40:16.880 --> 00:40:19.679
<v Speaker 4>if you install through visual Studio, it will prompt up

780
00:40:19.679 --> 00:40:22.280
<v Speaker 4>a little box to say, hey, accept the ULA. But

781
00:40:22.480 --> 00:40:25.480
<v Speaker 4>most of which stuff is a dot net tool and

782
00:40:25.760 --> 00:40:29.199
<v Speaker 4>a MS bill desicate. Neither of those routes that you

783
00:40:29.360 --> 00:40:32.079
<v Speaker 4>use showed you, including dot net tool installed does not

784
00:40:32.199 --> 00:40:34.320
<v Speaker 4>tell you that there is a license that you must accept.

785
00:40:34.559 --> 00:40:37.559
<v Speaker 4>So you're like silently accepting the license as the dot

786
00:40:37.599 --> 00:40:38.679
<v Speaker 4>net tool installs it or.

787
00:40:38.639 --> 00:40:39.920
<v Speaker 2>Something that's not sexy.

788
00:40:40.119 --> 00:40:40.360
<v Speaker 3>Yeah.

789
00:40:40.400 --> 00:40:42.320
<v Speaker 4>Well I couldn't get the dot net team to care.

790
00:40:43.159 --> 00:40:45.519
<v Speaker 4>They're like, oh, this is this is not our problem,

791
00:40:45.559 --> 00:40:48.360
<v Speaker 4>and actually there's an issue. It's it's in the newgit repo.

792
00:40:48.519 --> 00:40:49.800
<v Speaker 4>I got bounced out of the dot net one in

793
00:40:49.840 --> 00:40:51.440
<v Speaker 4>the NuGet when it's been like I don't know thirteen

794
00:40:51.519 --> 00:40:54.039
<v Speaker 4>years or something, me complaining about open source project for

795
00:40:54.119 --> 00:40:56.960
<v Speaker 4>Noshue for a long time, but like they're not interested

796
00:40:56.960 --> 00:40:59.039
<v Speaker 4>in tackling this in fact, the discussion is mostly about

797
00:40:59.039 --> 00:41:03.679
<v Speaker 4>maybe we should remove this. So the feedback was coming in, Hey,

798
00:41:04.599 --> 00:41:07.199
<v Speaker 4>we didn't realize this was happening. I only saw this

799
00:41:07.239 --> 00:41:09.679
<v Speaker 4>because I read this one page in the documentation which

800
00:41:10.280 --> 00:41:13.679
<v Speaker 4>notified to me that, yeah, people don't read the new releases.

801
00:41:13.679 --> 00:41:16.159
<v Speaker 4>They just pick up the new one and go. So

802
00:41:16.239 --> 00:41:18.880
<v Speaker 4>a lot of people didn't even realize it's happening. So

803
00:41:19.639 --> 00:41:23.840
<v Speaker 4>we implemented in Wix seven, which just released back in

804
00:41:23.920 --> 00:41:26.239
<v Speaker 4>this April, so a year after wik six, when we

805
00:41:26.239 --> 00:41:28.840
<v Speaker 4>introduced open source maintenance fee. This concept of what I

806
00:41:28.880 --> 00:41:34.280
<v Speaker 4>call ed uforcement. It is a property you add an

807
00:41:34.360 --> 00:41:38.320
<v Speaker 4>MS build to say accept the EULA, or you can

808
00:41:38.400 --> 00:41:40.239
<v Speaker 4>add it to the command line tool, to the Wix's

809
00:41:40.239 --> 00:41:42.840
<v Speaker 4>command line tool say accept the EULA, and then you

810
00:41:42.920 --> 00:41:45.559
<v Speaker 4>specify the version. So in the latest version you say

811
00:41:45.599 --> 00:41:48.920
<v Speaker 4>accept EULA Wix seven, and so that means that you

812
00:41:49.079 --> 00:41:51.360
<v Speaker 4>now have acknowledged that there's ULA, and if you don't

813
00:41:51.360 --> 00:41:54.320
<v Speaker 4>pass that switch, then the tool fails errors and says, hey,

814
00:41:54.559 --> 00:41:57.000
<v Speaker 4>you need to accept the open source license fee. Go

815
00:41:57.039 --> 00:41:58.920
<v Speaker 4>to this link and you can read all about it,

816
00:41:58.920 --> 00:42:00.960
<v Speaker 4>and we have the information and it basically tells you, hey,

817
00:42:01.000 --> 00:42:03.760
<v Speaker 4>you need to if you're doing all this, you need

818
00:42:03.800 --> 00:42:07.360
<v Speaker 4>to pay the fee. And after you've done that, then

819
00:42:07.400 --> 00:42:10.400
<v Speaker 4>here's the command line switch you add. So Carl will say, well,

820
00:42:10.400 --> 00:42:12.400
<v Speaker 4>then they can just go ahead and add the command

821
00:42:12.440 --> 00:42:15.280
<v Speaker 4>line so which once they learn how which is true.

822
00:42:15.519 --> 00:42:19.039
<v Speaker 2>But generally speaking, businesses are not criminal, no, and they

823
00:42:19.039 --> 00:42:20.960
<v Speaker 2>don't want to be criminal. They don't want to be

824
00:42:21.000 --> 00:42:22.480
<v Speaker 2>they don't want to be criminals. They want to follow

825
00:42:22.480 --> 00:42:24.800
<v Speaker 2>the rules. Make the rules clear and easy to follow,

826
00:42:24.800 --> 00:42:26.199
<v Speaker 2>and they will follow them exactly.

827
00:42:26.320 --> 00:42:30.800
<v Speaker 4>And so we have finally put together these pieces that

828
00:42:31.320 --> 00:42:35.559
<v Speaker 4>have fit into a yula, which is a natural concept

829
00:42:35.559 --> 00:42:39.480
<v Speaker 4>for them, unnatural and open source, but it makes sense

830
00:42:39.480 --> 00:42:43.320
<v Speaker 4>as soon as they evaluate it, come back with a

831
00:42:43.599 --> 00:42:46.000
<v Speaker 4>payment process that they have to go through gethub sponsors,

832
00:42:46.039 --> 00:42:48.760
<v Speaker 4>which is a little bit unusual, but it's get hubbed

833
00:42:48.840 --> 00:42:50.760
<v Speaker 4>and trusted and therefore they just have to kind of

834
00:42:50.760 --> 00:42:54.039
<v Speaker 4>work their way through. And so smoothing that procurement process

835
00:42:54.119 --> 00:42:56.440
<v Speaker 4>is the last thing that I'm kind of continuing to

836
00:42:58.320 --> 00:43:01.000
<v Speaker 4>iterate on trying to find easy an easier ways through

837
00:43:01.239 --> 00:43:03.719
<v Speaker 4>because I kid you not, the emails that we get,

838
00:43:03.960 --> 00:43:06.760
<v Speaker 4>we're almost up to like one or two a day

839
00:43:06.840 --> 00:43:10.199
<v Speaker 4>of people asking how do we do GitHub sponsors, How

840
00:43:10.239 --> 00:43:12.360
<v Speaker 4>do we pay you through get hobs sponsors. Can we

841
00:43:12.400 --> 00:43:14.239
<v Speaker 4>have another mechanism. We're not really used to doing it

842
00:43:14.280 --> 00:43:17.280
<v Speaker 4>this way, and so if we can figure out how

843
00:43:17.280 --> 00:43:20.760
<v Speaker 4>to smooth that out one more time, then it just

844
00:43:20.800 --> 00:43:23.519
<v Speaker 4>fits very naturally. And all the companies are like, uh, okay,

845
00:43:23.760 --> 00:43:26.000
<v Speaker 4>we just just do it done.

846
00:43:25.519 --> 00:43:27.719
<v Speaker 1>And and they pay annually, so.

847
00:43:28.239 --> 00:43:31.079
<v Speaker 4>You could pay annually, you could pay monthly. Getthub supports

848
00:43:31.119 --> 00:43:34.159
<v Speaker 4>both of them through the invoice whatever.

849
00:43:34.400 --> 00:43:35.800
<v Speaker 2>But getthub Sponsors does all that.

850
00:43:35.920 --> 00:43:40.239
<v Speaker 4>Get houb Sponsors does all that. Like I it is.

851
00:43:41.239 --> 00:43:44.960
<v Speaker 4>It has worked so well by just fitting into these parts,

852
00:43:45.599 --> 00:43:51.119
<v Speaker 4>and the pushback has been minimal, like I was prepared

853
00:43:51.159 --> 00:43:54.159
<v Speaker 4>for so much more sure, but people, but people have

854
00:43:54.239 --> 00:43:57.400
<v Speaker 4>been like, there's been a couple like you should not pay,

855
00:43:57.519 --> 00:43:59.800
<v Speaker 4>you should not charge for open source that goes against

856
00:43:59.800 --> 00:44:02.519
<v Speaker 4>them luntro of it yah, which of course is demonstrably false.

857
00:44:02.639 --> 00:44:05.119
<v Speaker 4>That's not at all true anywhere in the history of anything.

858
00:44:05.679 --> 00:44:07.679
<v Speaker 4>This is exactly where you do pay it. I've had

859
00:44:08.039 --> 00:44:11.400
<v Speaker 4>I've only had developers say that they're not sure that

860
00:44:11.440 --> 00:44:14.559
<v Speaker 4>the wording in the yula is quite right right, and

861
00:44:14.599 --> 00:44:17.280
<v Speaker 4>I'm like, that's possible. I had a lawyer write it.

862
00:44:18.840 --> 00:44:21.480
<v Speaker 4>If you have a lawyer that says that there's a

863
00:44:21.519 --> 00:44:23.599
<v Speaker 4>problem here, I would love to work with them. But

864
00:44:24.079 --> 00:44:27.400
<v Speaker 4>my understanding from legals that I had, these are all

865
00:44:27.480 --> 00:44:31.000
<v Speaker 4>the correct words. They quibble over what does user mean?

866
00:44:31.199 --> 00:44:34.079
<v Speaker 4>And it's defined in particular way legally. And it's very

867
00:44:34.079 --> 00:44:36.039
<v Speaker 4>funny because I had the same comments to my lawyer

868
00:44:36.079 --> 00:44:37.400
<v Speaker 4>when I read it, like does it really mean this?

869
00:44:37.440 --> 00:44:39.480
<v Speaker 4>He's like, well, if you change it the way you're suggesting,

870
00:44:39.800 --> 00:44:41.519
<v Speaker 4>then that messes all these days up. I'm like, I'm

871
00:44:41.519 --> 00:44:44.320
<v Speaker 4>not doing law Okay, I trust you've got this right.

872
00:44:44.440 --> 00:44:49.000
<v Speaker 4>The professionals do the professional thing exactly exactly. So last

873
00:44:49.039 --> 00:44:51.639
<v Speaker 4>year I was very uncertain how it would go, and

874
00:44:51.840 --> 00:44:58.880
<v Speaker 4>now it's a completely viable model that a maintainers that

875
00:44:58.920 --> 00:45:00.840
<v Speaker 4>are like my project has gotten to the point where

876
00:45:00.840 --> 00:45:04.000
<v Speaker 4>I'm spending more time on this than I feel like

877
00:45:04.119 --> 00:45:07.639
<v Speaker 4>I'm being conversated for because it's just making social value

878
00:45:07.639 --> 00:45:10.119
<v Speaker 4>for the system. I think this is this is an

879
00:45:10.360 --> 00:45:14.079
<v Speaker 4>absolutely a viable option for them to consider it.

880
00:45:14.559 --> 00:45:16.800
<v Speaker 1>Last year I looked at it and I kicked the

881
00:45:16.840 --> 00:45:18.639
<v Speaker 1>tires and I was like, well, you know, maybe I'll

882
00:45:18.639 --> 00:45:21.400
<v Speaker 1>wait a year. So this just while you were talking

883
00:45:21.480 --> 00:45:24.239
<v Speaker 1>I went and looked at my new get published packages,

884
00:45:24.760 --> 00:45:28.880
<v Speaker 1>and my most popular project is Blazer Sliders. So this

885
00:45:29.039 --> 00:45:31.880
<v Speaker 1>is you know, you get panels that have sliders between

886
00:45:31.920 --> 00:45:33.960
<v Speaker 1>them and that kind of stuff, vertical, horizontal, you can

887
00:45:34.000 --> 00:45:36.760
<v Speaker 1>nest them and everything. It's really cool. And I've got

888
00:45:36.800 --> 00:45:42.559
<v Speaker 1>twenty four thousand downloads, so and it's it's a main

889
00:45:42.920 --> 00:45:45.119
<v Speaker 1>It's not hard to maintain. But every time there's a

890
00:45:45.119 --> 00:45:47.320
<v Speaker 1>new version of dot net and I have to you know,

891
00:45:47.519 --> 00:45:49.880
<v Speaker 1>upgrade it and test it, make sure that it all works.

892
00:45:49.920 --> 00:45:52.239
<v Speaker 1>I've got clients that use it. Yep. So I'm thinking

893
00:45:52.239 --> 00:45:54.000
<v Speaker 1>I might this might be a good time to pull

894
00:45:54.039 --> 00:45:55.440
<v Speaker 1>the trigger on that. Yep. Sure.

895
00:45:55.440 --> 00:45:58.320
<v Speaker 4>And it's exactly that spot that you're like, oh, well, yeah,

896
00:45:58.360 --> 00:46:00.599
<v Speaker 4>you know what, I have enough, there's of value me

897
00:46:00.679 --> 00:46:03.239
<v Speaker 4>continue to stay on top of the dot net releases

898
00:46:03.239 --> 00:46:05.320
<v Speaker 4>that come out, the security releases that come out. You

899
00:46:05.360 --> 00:46:07.559
<v Speaker 4>just have to be aware of them, all those things.

900
00:46:07.599 --> 00:46:09.480
<v Speaker 4>And now you're like, yeah, you know what, I'm going

901
00:46:09.519 --> 00:46:10.599
<v Speaker 4>to do that and then I'm going to go get

902
00:46:10.639 --> 00:46:13.159
<v Speaker 4>another couple, you know, extra picks for my guitar or

903
00:46:13.199 --> 00:46:19.639
<v Speaker 4>whatever you're doing. You're like, you know, like pickups, pickups,

904
00:46:19.840 --> 00:46:23.239
<v Speaker 4>all right, all of those things become viable or you know,

905
00:46:23.440 --> 00:46:25.880
<v Speaker 4>you you donate it, or you you know, I don't know,

906
00:46:25.960 --> 00:46:29.079
<v Speaker 4>take your wife, your daughter, your son, your whatever out

907
00:46:29.119 --> 00:46:31.039
<v Speaker 4>to dinner that you haven't seen him, like all those things.

908
00:46:31.079 --> 00:46:33.960
<v Speaker 1>Well, I'm a I'm a big fan of pricing things

909
00:46:33.960 --> 00:46:36.559
<v Speaker 1>according to the value of the customer to the customer, right,

910
00:46:37.159 --> 00:46:40.119
<v Speaker 1>and so if a customer is using Blazer sliders in

911
00:46:40.159 --> 00:46:43.559
<v Speaker 1>a in a project that they're making millions of dollars

912
00:46:43.599 --> 00:46:46.320
<v Speaker 1>a year on, you know, it's kind of it makes

913
00:46:46.320 --> 00:46:46.840
<v Speaker 1>sense to.

914
00:46:46.880 --> 00:46:49.440
<v Speaker 4>It makes sense some of that down and that's why

915
00:46:49.440 --> 00:46:52.360
<v Speaker 4>it's worked. It's it's been everybody's been like, okay, it

916
00:46:52.400 --> 00:46:54.960
<v Speaker 4>makes sense. The numbers small. If anything, the number is

917
00:46:54.960 --> 00:46:57.440
<v Speaker 4>too small. I have to deal with procurement. My hope

918
00:46:57.599 --> 00:47:00.760
<v Speaker 4>is that while I try to work on pre procurement

919
00:47:01.280 --> 00:47:03.760
<v Speaker 4>at the same time, if more projects start picking it up,

920
00:47:04.159 --> 00:47:07.519
<v Speaker 4>then it just becomes part of procurement, which is what

921
00:47:07.679 --> 00:47:10.559
<v Speaker 4>happened with open source. The lawyers were like, you can't

922
00:47:10.639 --> 00:47:13.039
<v Speaker 4>touch OPO source, and then they got comfortable with the

923
00:47:13.079 --> 00:47:15.440
<v Speaker 4>licenses and then it became a process. This is how

924
00:47:15.519 --> 00:47:16.760
<v Speaker 4>you accept OPO source.

925
00:47:17.280 --> 00:47:19.840
<v Speaker 2>I means it's obviously working for Wicks, but if you

926
00:47:19.920 --> 00:47:22.119
<v Speaker 2>got some other folks that are being successful with it.

927
00:47:22.000 --> 00:47:26.159
<v Speaker 4>So it's still early. It's early, and I have honestly

928
00:47:27.159 --> 00:47:29.880
<v Speaker 4>shied most people away from trying to pick it up

929
00:47:29.920 --> 00:47:32.119
<v Speaker 4>because I didn't think I had all the bugs worked

930
00:47:32.119 --> 00:47:35.880
<v Speaker 4>out right, and I didn't want them to go through

931
00:47:37.239 --> 00:47:41.000
<v Speaker 4>pain that I didn't know how to help them resolve,

932
00:47:41.320 --> 00:47:43.360
<v Speaker 4>because there was a potential that you know, you get

933
00:47:43.360 --> 00:47:46.800
<v Speaker 4>a lot of lashback, and as a maintainer, especially in money,

934
00:47:47.079 --> 00:47:50.840
<v Speaker 4>I was very worried that it could get really, really nasty. Yeah,

935
00:47:50.880 --> 00:47:53.239
<v Speaker 4>and so just finding the right way to say things

936
00:47:53.239 --> 00:47:56.159
<v Speaker 4>and word things was a big part of it, and

937
00:47:56.679 --> 00:47:59.800
<v Speaker 4>I feel like we're very much there to that end.

938
00:48:01.079 --> 00:48:04.159
<v Speaker 4>Simon Kropp, who is notorious.

939
00:48:04.239 --> 00:48:06.840
<v Speaker 2>Notorious, awesome on this show certainly.

940
00:48:06.880 --> 00:48:11.320
<v Speaker 4>And huge in the dot net ecosystem, was the first

941
00:48:11.519 --> 00:48:13.880
<v Speaker 4>second person I talked to the open Source Maintenance Fee about.

942
00:48:14.320 --> 00:48:16.280
<v Speaker 4>I didn't know Simon before that. I just cold called

943
00:48:16.320 --> 00:48:17.840
<v Speaker 4>him and said, hey, can I talk I want to

944
00:48:17.840 --> 00:48:20.079
<v Speaker 4>show this thing to you. And he was the one

945
00:48:20.199 --> 00:48:23.960
<v Speaker 4>very early had fantastic questions, helped me frame and make

946
00:48:24.000 --> 00:48:28.000
<v Speaker 4>sure I had answered a lot of questions early, but

947
00:48:28.119 --> 00:48:30.880
<v Speaker 4>he at that time was noncommittal. I'd say he's like, well,

948
00:48:30.920 --> 00:48:32.679
<v Speaker 4>we'll see how it goes. But he's starting to bring

949
00:48:32.719 --> 00:48:36.320
<v Speaker 4>his projects on now that's cool, and his projects are

950
00:48:36.800 --> 00:48:40.280
<v Speaker 4>bigger than mine, like as pure numbers go libraries and

951
00:48:40.320 --> 00:48:43.320
<v Speaker 4>these like that. There, it's much bigger. He's already opened

952
00:48:43.320 --> 00:48:46.960
<v Speaker 4>the issue in Verify, which is one of his big

953
00:48:46.960 --> 00:48:50.280
<v Speaker 4>testing systems, and he's doing it the right way because

954
00:48:50.360 --> 00:48:53.400
<v Speaker 4>the docutation said, if you're going to introduce the open

955
00:48:53.440 --> 00:48:56.679
<v Speaker 4>source maintenance fee, put an announcement out, explain what you're

956
00:48:56.679 --> 00:49:01.480
<v Speaker 4>doing and why, and leave a lead time of three

957
00:49:01.519 --> 00:49:04.760
<v Speaker 4>to six months, because if you don't, people will complain

958
00:49:04.840 --> 00:49:06.880
<v Speaker 4>that you didn't tell them right, yeah, that you run

959
00:49:07.559 --> 00:49:10.599
<v Speaker 4>exactly well, it just too fast. If you do, then

960
00:49:10.639 --> 00:49:13.400
<v Speaker 4>they don't complain or they don't have anything to complain

961
00:49:13.440 --> 00:49:15.840
<v Speaker 4>about in the end. So it's just things we learned.

962
00:49:15.880 --> 00:49:18.599
<v Speaker 1>Simon is a brilliant, brilliant guy. He's helped me on

963
00:49:18.639 --> 00:49:21.000
<v Speaker 1>a couple of my open source projects too, and it

964
00:49:21.039 --> 00:49:23.760
<v Speaker 1>seems like every other better Know framework is because of him.

965
00:49:24.199 --> 00:49:27.239
<v Speaker 4>Yes, I'm betting, and we'll see if it works, but

966
00:49:27.360 --> 00:49:29.800
<v Speaker 4>I'm betting that the open source maintenance Fee, depending on

967
00:49:29.800 --> 00:49:33.400
<v Speaker 4>how it goes, could make you know, Simon like retired. Yeah,

968
00:49:33.559 --> 00:49:36.119
<v Speaker 4>that's actually my thinking is that given his projects, he's

969
00:49:36.639 --> 00:49:41.360
<v Speaker 4>so prolific, he could through this have so many people

970
00:49:41.400 --> 00:49:44.559
<v Speaker 4>that he could finish and then just work on his projects.

971
00:49:44.599 --> 00:49:47.360
<v Speaker 4>And I keep thinking, how is that not the best

972
00:49:47.400 --> 00:49:52.159
<v Speaker 4>thing for people using these projects? Simon available to work

973
00:49:52.199 --> 00:49:54.039
<v Speaker 4>on all things full time, on.

974
00:49:54.280 --> 00:49:58.320
<v Speaker 2>Verify, on you know exactly so many, so many things, all.

975
00:49:58.199 --> 00:50:00.159
<v Speaker 4>Of them and all of them. Then he wouldn't have

976
00:50:00.199 --> 00:50:01.840
<v Speaker 4>to pick which ones he's doing. He'd just be able

977
00:50:01.840 --> 00:50:04.119
<v Speaker 4>to do them all because the dude's a madman. So

978
00:50:04.960 --> 00:50:08.880
<v Speaker 4>that's I'm excited to see how it goes for him.

979
00:50:09.000 --> 00:50:11.199
<v Speaker 2>Well, people will vote for their feet, right, he can

980
00:50:11.239 --> 00:50:14.519
<v Speaker 2>go focus on the ones that are getting the most sponsorship.

981
00:50:13.880 --> 00:50:16.800
<v Speaker 4>That that too, or spin up new projects and help

982
00:50:16.800 --> 00:50:20.400
<v Speaker 4>and things like that. It's it's all in my opinion,

983
00:50:20.480 --> 00:50:23.840
<v Speaker 4>it's all good. And I contrast it with like going

984
00:50:23.880 --> 00:50:27.800
<v Speaker 4>back to VT Evan and they started a company, and

985
00:50:27.880 --> 00:50:31.840
<v Speaker 4>they recently got acquired by cloud Flare, which of all companies,

986
00:50:31.920 --> 00:50:34.119
<v Speaker 4>is probably one of the better ones because they are

987
00:50:34.159 --> 00:50:36.800
<v Speaker 4>generally very much about continuing to keep things in the open.

988
00:50:38.280 --> 00:50:42.360
<v Speaker 4>But I keep wondering if Evan had put the open

989
00:50:42.360 --> 00:50:46.480
<v Speaker 4>source maintenance fee on vat and view. Yeah, that thing

990
00:50:46.599 --> 00:50:49.400
<v Speaker 4>gets I forget. It was like twenty million down in

991
00:50:49.400 --> 00:50:51.880
<v Speaker 4>a month. Yeah, double digit millions, you.

992
00:50:51.840 --> 00:50:55.400
<v Speaker 1>Know, Richard, when I'm thinking about Polly, Yeah, totally Polly

993
00:50:55.519 --> 00:50:59.599
<v Speaker 1>Appenaxtonnes Polly, Yeah, you know, and it gets millions and

994
00:50:59.599 --> 00:51:01.159
<v Speaker 1>millions downloads.

995
00:51:00.719 --> 00:51:03.320
<v Speaker 4>Exactly that that whole space. You're like, do that, and

996
00:51:03.360 --> 00:51:05.800
<v Speaker 4>then what are we doing. We're funding a person to

997
00:51:05.880 --> 00:51:09.159
<v Speaker 4>work on a project that they've been successful at, they

998
00:51:09.559 --> 00:51:12.920
<v Speaker 4>figured it out, they like what they're doing, presumably they've

999
00:51:12.960 --> 00:51:15.039
<v Speaker 4>been working on it so hard and for so long.

1000
00:51:15.440 --> 00:51:17.239
<v Speaker 4>Now we're just funding them to continue to do more

1001
00:51:17.280 --> 00:51:19.880
<v Speaker 4>of that. I in a way that.

1002
00:51:20.000 --> 00:51:22.519
<v Speaker 2>You know, no EXI I'd love to see Simon Cropp

1003
00:51:22.559 --> 00:51:25.159
<v Speaker 2>do even more, like goodness knows what he's holding back on.

1004
00:51:25.360 --> 00:51:29.440
<v Speaker 4>Yes, So so I am. I have gone from very

1005
00:51:29.800 --> 00:51:34.360
<v Speaker 4>frustrated and very afraid and concerned about what was happening

1006
00:51:34.559 --> 00:51:36.199
<v Speaker 4>to now I'm on the other side where I'm like,

1007
00:51:37.000 --> 00:51:38.679
<v Speaker 4>you don't have to adopt the open source maintenance fee.

1008
00:51:38.679 --> 00:51:40.119
<v Speaker 4>If you don't want money or do you want to deal,

1009
00:51:40.119 --> 00:51:42.800
<v Speaker 4>then that's fine. I'm not saying do that, but if

1010
00:51:42.800 --> 00:51:47.320
<v Speaker 4>you have any questions, it has been working really well.

1011
00:51:47.639 --> 00:51:50.559
<v Speaker 4>Oh Jason Everything was I think one of the first ones.

1012
00:51:50.760 --> 00:51:52.920
<v Speaker 4>And I know Kazoo adopted on a bunch of his

1013
00:51:53.000 --> 00:51:55.559
<v Speaker 4>smaller projects, but Jason Everything might have been the first

1014
00:51:55.559 --> 00:51:59.480
<v Speaker 4>project that was bigger. Greg Daniels, I don't I don't

1015
00:51:59.519 --> 00:52:01.519
<v Speaker 4>really know him. He just kind of picked it up

1016
00:52:01.559 --> 00:52:04.599
<v Speaker 4>out of nowhere that I didn't really understand. It just

1017
00:52:04.639 --> 00:52:07.079
<v Speaker 4>surprised me, and I learned a few things in his

1018
00:52:07.199 --> 00:52:09.840
<v Speaker 4>release of more things to put into the fack and

1019
00:52:09.840 --> 00:52:12.000
<v Speaker 4>and people's reactions, like the timeframe.

1020
00:52:12.039 --> 00:52:14.679
<v Speaker 1>Guess how many downloads of Polly have gone through new

1021
00:52:14.719 --> 00:52:17.360
<v Speaker 1>get two point eight billion?

1022
00:52:17.800 --> 00:52:20.280
<v Speaker 4>Now that that's tricky. Downloads are tricky because if they are,

1023
00:52:20.719 --> 00:52:24.719
<v Speaker 4>aren't they referenced by the dot net framework somewhere like internally?

1024
00:52:25.079 --> 00:52:28.960
<v Speaker 1>Well, so the transit of ones wouldn't count. No dot

1025
00:52:29.000 --> 00:52:34.360
<v Speaker 1>net framework forked the stop Polly that they're using for themselves. Okay,

1026
00:52:34.360 --> 00:52:35.800
<v Speaker 1>it's not that Polly is included.

1027
00:52:35.840 --> 00:52:40.800
<v Speaker 4>Okay, Okay, then then i'mification all right, cool. Then no,

1028
00:52:40.840 --> 00:52:44.199
<v Speaker 4>then then that's pretty much probably all straight up direct

1029
00:52:44.239 --> 00:52:45.199
<v Speaker 4>references to Polly.

1030
00:52:45.360 --> 00:52:48.480
<v Speaker 1>Yeah, there's still people at aptnx that are maintaining it, so,

1031
00:52:48.719 --> 00:52:51.840
<v Speaker 1>I mean, you know, the money would obviously trickle to them.

1032
00:52:51.760 --> 00:52:54.159
<v Speaker 4>Look like if fire Giant. I was getting a point

1033
00:52:54.159 --> 00:52:57.039
<v Speaker 4>where like, I can't do this. I can't fund Wix

1034
00:52:57.599 --> 00:52:59.760
<v Speaker 4>with the security vulnerabilies that we're hitting and things like that.

1035
00:52:59.760 --> 00:53:02.760
<v Speaker 4>We the whole lot of dev time into it in

1036
00:53:02.800 --> 00:53:07.079
<v Speaker 4>twenty twenty four, and it was brutal. With the open

1037
00:53:07.079 --> 00:53:09.280
<v Speaker 4>source maintenance fee, it's much more like, yeah, let's pick

1038
00:53:09.320 --> 00:53:10.920
<v Speaker 4>up one of the features and do those, and we've

1039
00:53:10.920 --> 00:53:13.760
<v Speaker 4>been able to do that. We did a long standing

1040
00:53:13.800 --> 00:53:16.519
<v Speaker 4>feature that we'd wanted to do forever, per user, per

1041
00:53:16.599 --> 00:53:20.039
<v Speaker 4>machine switching inside bundles. I mean it was complicated, a

1042
00:53:20.039 --> 00:53:21.960
<v Speaker 4>whole lot of problems. Yeah, we knocked it out in

1043
00:53:22.000 --> 00:53:25.760
<v Speaker 4>Wick seven and it was like, it feels better. The

1044
00:53:25.800 --> 00:53:28.159
<v Speaker 4>whole thing feels better. Answering questions, Yeah, no problem with

1045
00:53:28.280 --> 00:53:29.639
<v Speaker 4>suit as I get to it, I mean, boom boom,

1046
00:53:29.679 --> 00:53:32.239
<v Speaker 4>boom boom, knock them all out, keep going. Yeah, the

1047
00:53:32.840 --> 00:53:35.519
<v Speaker 4>attitude and everything just feels so much better that. All right,

1048
00:53:35.880 --> 00:53:39.639
<v Speaker 4>these large companies, these companies of all sizes are paying

1049
00:53:39.639 --> 00:53:41.840
<v Speaker 4>a maintenance fee for me to keep this project going

1050
00:53:41.840 --> 00:53:44.159
<v Speaker 4>that I want to see successful, and now I don't

1051
00:53:44.199 --> 00:53:46.000
<v Speaker 4>feel taken advantage of at all.

1052
00:53:46.159 --> 00:53:49.840
<v Speaker 1>So we didn't really talk about what's you set Obviously

1053
00:53:49.880 --> 00:53:52.760
<v Speaker 1>set the maintenance fee for your project, but what's the

1054
00:53:52.880 --> 00:53:56.000
<v Speaker 1>range that you would advise people to do.

1055
00:53:56.239 --> 00:53:59.639
<v Speaker 4>So there are two models pre presented on the open

1056
00:53:59.679 --> 00:54:03.639
<v Speaker 4>source maintenance fee dot org has two models that it proposes.

1057
00:54:03.920 --> 00:54:06.880
<v Speaker 4>One is if is a ten dollars fee if you're

1058
00:54:07.199 --> 00:54:09.800
<v Speaker 4>if you're just a library or something like that, you

1059
00:54:09.800 --> 00:54:13.039
<v Speaker 4>want it simple, just do ten dollars straight up. If

1060
00:54:13.079 --> 00:54:17.639
<v Speaker 4>you're at all bigger complicated anything, I would recommend in

1061
00:54:17.760 --> 00:54:21.480
<v Speaker 4>all cases you have ten dollars for a twenty person

1062
00:54:21.800 --> 00:54:24.760
<v Speaker 4>up to a twenty person company, forty dollars for up

1063
00:54:24.760 --> 00:54:27.239
<v Speaker 4>to one hundred person company, and then the sixty dollars

1064
00:54:27.280 --> 00:54:28.960
<v Speaker 4>for after the one hundred person company. And that kind

1065
00:54:28.960 --> 00:54:30.760
<v Speaker 4>of ranges that we found.

1066
00:54:30.559 --> 00:54:33.880
<v Speaker 1>Is this per year or per month, per month, okay.

1067
00:54:33.519 --> 00:54:33.960
<v Speaker 4>Per month?

1068
00:54:34.079 --> 00:54:34.320
<v Speaker 1>Wow?

1069
00:54:34.360 --> 00:54:37.239
<v Speaker 4>And then and like I said, nobody's really complaining about

1070
00:54:37.239 --> 00:54:38.000
<v Speaker 4>the present.

1071
00:54:37.719 --> 00:54:39.159
<v Speaker 1>Now, nobody would complain about that.

1072
00:54:39.400 --> 00:54:42.440
<v Speaker 4>No, We've had a couple devs complain about it, but

1073
00:54:42.599 --> 00:54:46.000
<v Speaker 4>they're not business people. Like that's the tricky thing. Also

1074
00:54:46.239 --> 00:54:50.400
<v Speaker 4>not tricky. There's a small cases of most of the

1075
00:54:50.400 --> 00:54:52.599
<v Speaker 4>people that give me feedback and the maintenance fee have

1076
00:54:52.760 --> 00:54:54.960
<v Speaker 4>been developers. And then I just have to make sure

1077
00:54:55.000 --> 00:54:57.119
<v Speaker 4>I coordinate with who they are where they come in

1078
00:54:57.159 --> 00:54:59.639
<v Speaker 4>at because as a developer I am guilty of this

1079
00:54:59.679 --> 00:55:00.119
<v Speaker 4>as well.

1080
00:55:00.000 --> 00:55:00.079
<v Speaker 1>Well.

1081
00:55:00.119 --> 00:55:04.599
<v Speaker 4>I don't always think businesslike yeah right, and and they're like, no,

1082
00:55:04.599 --> 00:55:06.559
<v Speaker 4>nobody would ever do that. You're like, well, you know,

1083
00:55:06.559 --> 00:55:08.280
<v Speaker 4>if it's just two hours, I'll just stand to see

1084
00:55:08.280 --> 00:55:10.159
<v Speaker 4>I system and run it myself. And you're like, absolutely,

1085
00:55:10.239 --> 00:55:12.159
<v Speaker 4>you could do that, but does your boss want you

1086
00:55:12.239 --> 00:55:14.119
<v Speaker 4>doing that? Is that really the best time for you

1087
00:55:14.199 --> 00:55:16.119
<v Speaker 4>to be using you know, is it worth all that

1088
00:55:16.119 --> 00:55:18.119
<v Speaker 4>a headache? No, you know, let's just pay the fee

1089
00:55:18.159 --> 00:55:20.559
<v Speaker 4>because it's not that much and the whole balance ends

1090
00:55:20.599 --> 00:55:26.039
<v Speaker 4>up working out. So yeah, I I am, like I said,

1091
00:55:26.079 --> 00:55:28.440
<v Speaker 4>I'm quite tickled that it all worked out. I was

1092
00:55:28.440 --> 00:55:30.159
<v Speaker 4>telling my wife I was going on the show today

1093
00:55:30.280 --> 00:55:32.480
<v Speaker 4>this morning, and she was kind of talking about and

1094
00:55:32.519 --> 00:55:34.119
<v Speaker 4>she said, oh, yeah, and now someone could go and

1095
00:55:34.320 --> 00:55:36.280
<v Speaker 4>work in the open source field, and I'm like, the

1096
00:55:36.400 --> 00:55:40.000
<v Speaker 4>open source field, that's not a thing. But I was like,

1097
00:55:40.079 --> 00:55:42.480
<v Speaker 4>you know, there's actually a space here that if you

1098
00:55:42.480 --> 00:55:46.159
<v Speaker 4>create a project's big enough, then yeah, you can work

1099
00:55:46.320 --> 00:55:48.440
<v Speaker 4>in the open source field.

1100
00:55:48.880 --> 00:55:49.440
<v Speaker 1>It's true.

1101
00:55:49.639 --> 00:55:50.440
<v Speaker 2>Yeah, it's true.

1102
00:55:50.480 --> 00:55:52.679
<v Speaker 1>Well this is great, and I hope we have inspired

1103
00:55:52.760 --> 00:55:56.360
<v Speaker 1>some people who have big repositories that a lot of

1104
00:55:56.360 --> 00:55:58.719
<v Speaker 1>people are using to take a look at it.

1105
00:55:58.840 --> 00:56:01.239
<v Speaker 4>And you never know, and I hope people that work

1106
00:56:01.239 --> 00:56:04.119
<v Speaker 4>at companies start going, you know what, we should make

1107
00:56:04.159 --> 00:56:06.199
<v Speaker 4>sure that all of our projects are covered. Why don't

1108
00:56:06.239 --> 00:56:08.760
<v Speaker 4>we just pay a maintenance fee as if they didn't,

1109
00:56:08.840 --> 00:56:11.440
<v Speaker 4>But they do, right, That's what we do at fire Giant.

1110
00:56:11.639 --> 00:56:14.719
<v Speaker 4>We basically say every dependency that we can sponsor, we

1111
00:56:14.800 --> 00:56:16.559
<v Speaker 4>go and sponsor the mat our fee right like they

1112
00:56:16.559 --> 00:56:17.079
<v Speaker 4>took a fee.

1113
00:56:17.199 --> 00:56:19.920
<v Speaker 1>Just do it, absolutely, just do it, do it well.

1114
00:56:20.039 --> 00:56:22.320
<v Speaker 1>This is this is a great solution, Rob. Thank you

1115
00:56:22.360 --> 00:56:25.000
<v Speaker 1>for the update, and it's been great talking to you.

1116
00:56:25.079 --> 00:56:27.199
<v Speaker 1>Thank you for having me and congrats on the progress. Man.

1117
00:56:27.239 --> 00:56:28.639
<v Speaker 2>It's going well.

1118
00:56:28.519 --> 00:56:31.599
<v Speaker 4>Yep, and hopefully you have other people coming. Oh yeah yeah,

1119
00:56:31.599 --> 00:56:33.159
<v Speaker 4>I use the opens sours means fee. It's no big deal.

1120
00:56:34.159 --> 00:56:36.000
<v Speaker 4>That's what I want. Big deal, just the way we

1121
00:56:36.039 --> 00:56:37.599
<v Speaker 4>do it, good way it works, just the thing you do.

1122
00:56:37.920 --> 00:56:38.480
<v Speaker 4>Give me the time.

1123
00:56:38.639 --> 00:56:41.000
<v Speaker 1>Right, Well, thanks again, Rob, and we will talk to you,

1124
00:56:41.079 --> 00:56:42.079
<v Speaker 1>dear listener next.

1125
00:56:41.880 --> 00:56:57.719
<v Speaker 5>Time on dot net rocks.

1126
00:57:04.039 --> 00:57:06.800
<v Speaker 6>Dot net Rocks is brought to you by Franklin's Net

1127
00:57:06.880 --> 00:57:10.840
<v Speaker 6>and produced by Pop Studios. A full service audio, video

1128
00:57:10.880 --> 00:57:14.960
<v Speaker 6>and post production facility located physically in New London, Connecticut,

1129
00:57:15.199 --> 00:57:20.039
<v Speaker 6>and of course in the cloud online at PWOP dot com.

1130
00:57:20.199 --> 00:57:22.360
<v Speaker 3>Visit our website at d O T N E T

1131
00:57:22.599 --> 00:57:26.599
<v Speaker 3>R O c k S dot com for RSS feeds, downloads,

1132
00:57:26.760 --> 00:57:30.440
<v Speaker 3>mobile apps, comments, and access to the full archives going

1133
00:57:30.480 --> 00:57:33.880
<v Speaker 3>back to show number one, recorded in September two thousand

1134
00:57:33.880 --> 00:57:34.159
<v Speaker 3>and two.

1135
00:57:34.760 --> 00:57:37.119
<v Speaker 6>And make sure you check out our sponsors. They keep

1136
00:57:37.199 --> 00:57:39.719
<v Speaker 6>us in business. Now go write some code.

1137
00:57:40.039 --> 00:57:40.840
<v Speaker 1>See you next time.

1138
00:57:41.719 --> 00:57:43.559
<v Speaker 4>You got jam Vans

1139
00:57:50.280 --> 00:57:50.320
<v Speaker 6>And
