mediagoblin-campaign-behind-the-scenes.html 25 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551
  1. title: On the MediaGoblin fundraising campaign part 2: behind the scenes
  2. date: 2013-01-27 17:00
  3. author: Christine Lemmer-Webber
  4. slug: mediagoblin-campaign-behind-the-scenes
  5. ---
  6. <div class="outline-text-2" id="text-1">
  7. </div><p>
  8. The last year has had a lot of things happen to it in my life. I took
  9. on a lot of new responsibilities at my old job at Creative Commons,
  10. <a href="http://mediagoblin.org">MediaGoblin</a> development ran in full swing, we kicked off
  11. <a href="http://lpc.opengameart.org/">Liberated Pixel Cup</a>, I left my job at Creative Commons, we left DeKalb and
  12. moved to Madison, Morgan started her PhD program... but the largest,
  13. most overwhelmingly huge thing that happened in my life this year was
  14. the <a href="http://mediagoblin.org/pages/campaign.html">MediaGoblin campaign</a>.
  15. </p>
  16. <p>
  17. I've never done anything that felt so huge, so life changing, that
  18. used so many of my skills and all of my energy, that felt so draining
  19. and yet felt so gratifying all at once.
  20. </p>
  21. <p>
  22. The campaign was a <a href="http://mediagoblin.org/news/we-did-it.html">huge success</a>, and I've wanted to write about it for
  23. some time. But even after the campaign ended, it didn't really end;
  24. I've still been busy wrapping it up. And it's also something that
  25. felt so huge that I have a hard time putting it all down. So this
  26. will be my attempt. There will be no tl;dr... knowing of the success
  27. of the campaign is the best tl;dr you will get, so if that's what you
  28. care about, you can stop reading now (you probably already read that
  29. anyway). If you wanted to know way, way more about behind the scenes
  30. than you might have ever wanted to, here we go.
  31. </p>
  32. <div id="outline-container-2" class="outline-2">
  33. <h2 id="sec-2">Running the campaign</h2>
  34. <div class="outline-text-2" id="text-2">
  35. </div>
  36. <div id="outline-container-2-1" class="outline-3">
  37. <h3 id="sec-2-1">Pre-pre-campaign</h3>
  38. <div class="outline-text-3" id="text-2-1">
  39. </div></div></div><p>
  40. The first thing that needed to happen for the MediaGoblin campaign to
  41. happen was that I needed to <a href="http://dustycloud.org/blog/leaving-cc-to-work-on-mediagoblin">quit my job</a>. There's a bit more to it
  42. than sending in a notice saying I was quitting; I knew that I thought
  43. MediaGoblin was my most important work and that I wanted to focus on
  44. it, but how? I was looking to see if there were some jobs that might
  45. allow me to contribute to free software in some way for most of the
  46. week but then allow me one or two days (preferably two) to focus on
  47. MediaGoblin work. There were some possibilities, but in the end I
  48. decided that I would not really get as much MediaGoblin work as I
  49. would like done in that manner, and the jobs that were willing to let
  50. me do that were (understandably) somewhat cautious in the amount of
  51. time they could promise me. At that time I was feeling flustered
  52. that I wasn't giving MediaGoblin enough time, and that every time I
  53. stepped back, even though we had a lot of contributors, contributions
  54. were falling off and the community would go very silent. I wanted to
  55. be as active as possible, and so I decided I wanted to try to do it
  56. fulltime.
  57. </p>
  58. <p>
  59. Of course, I also had to talk to Morgan; this was a decision that
  60. would affect both of us, and she was starting her program at the
  61. university and that was probably going to be expensive (more expensive
  62. than we anticipated even; it turned out funding was not available this
  63. last semester so we paid for it out of pocket). However, we had been
  64. saving for a possible life change like this. Morgan agreed: we had
  65. enough money at hand, I seemed to have some contracting opportunities
  66. if I needed to fall back on them, we had some backup savings, and if I
  67. could find a way to cover enough for us to live on for the next year,
  68. I should do it. And there was a cost of not doing this: I was at a
  69. strange position in my life where I could actually pursue my life
  70. dreams and possibly make them happen. What would happen if I didn't
  71. do so?
  72. </p>
  73. <p>
  74. And so I quit my job. I turned in my notice at work, agreed to work
  75. part time for a few months and then as a contractor afterwards.
  76. </p>
  77. <p>
  78. Morgan and I left our apartment in DeKalb. There were two weeks
  79. between our old apartment and our new apartment. We put our things in
  80. storage, and went on a trip: first to Boston for a week, then to New
  81. York.
  82. </p>
  83. <p>
  84. In Boston Morgan and I stayed at the house of friend and MediaGoblin
  85. co-conspirator <a href="http://eximiousproductions.com/">Deb Nicholson</a>. Morgan took the time to visit museums
  86. and explore Boston; it was her first trip ever there. Meanwhile, I
  87. visited with free-softwareish friends and talked about
  88. free-software-ish things. I also spent a lot of time crashing the FSF
  89. office and doing MediaGoblin work from there. Deb's partner asked me
  90. when I was going to stop working and start vacationing and have a good
  91. time. I didn't know what he meant... I couldn't have been having a
  92. better time.
  93. </p>
  94. <p>
  95. The most important day of that trip was when Deb, Will Kahn-Greene
  96. (another MediaGoblin co-conspirator) and I met at the FSF offices to
  97. plan out the campaign. We talked a bit and laid out some general
  98. structure to how the campaign would work. Then it was time to answer
  99. one of the big questions: were we going to do the campaign through the
  100. FSF or through KickStarter? (John Sullivan already expressed interest
  101. in us doing it through the FSF if we were interested in doing so.) We
  102. left for a coffee shop to discuss it and finish outlining the
  103. structure of the campaign. Well, if you read my previous blogpost,
  104. you already know the results: <a href="http://dustycloud.org/blog/mediagoblin-campaign">we went with the FSF</a>.
  105. </p>
  106. <p>
  107. Of course, we still needed to agree that we were going through the
  108. FSF. We went back to the FSF offices, explained to John that we were
  109. interested in going through the FSF but there were certain features we
  110. needed during the campaign that it didn't appear the FSF had
  111. infrastructure-wise. We laid them out one for one, and John took
  112. notes on a pad of paper. "Yes, I think we can do this."
  113. </p>
  114. <p>
  115. Finally, it felt like the campaign was really real. I was excited.
  116. </p>
  117. <p>
  118. Morgan and I finished up our week in Boston, said goodbye to Deb and
  119. her (now-husband) Ernie for being such awesome hosts, and left for a
  120. week where I'd actually do some real vacationing (only a little bit
  121. of coding, honest) in New York, visited with a number of friends in
  122. the area and had a great time, and finally flew home to move our
  123. stuff between DeKalb and Madison.
  124. </p>
  125. <p>
  126. We moved into our new apartment. I walked around Madison and fell in
  127. love. For a couple of days, I just straightened things out, settled
  128. in, and mostly felt fairly relaxed, the most relaxed I had felt in a
  129. long time.
  130. </p>
  131. <p>
  132. But... time to stop relaxing. Time to start the campaign for real.
  133. Before the launch date, we had a mile-long list of TODO tasks, and a
  134. very short time to get going on them. I got to work.
  135. </p>
  136. <div id="outline-container-2-2" class="outline-3">
  137. <h3 id="sec-2-2">Campaign prep</h3>
  138. <div class="outline-text-3" id="text-2-2">
  139. </div></div><p>
  140. There was a lot to do before the campaign even started. We
  141. commissioned MediaGoblin's regular artist Jef van Schendel to do a
  142. special campaign page for the MediaGoblin site. The FSF did work to
  143. update their infrastructure for our requests. Deb, Will and I
  144. hammered out the plan for the pitch video, finalized the rewards
  145. plans (I did quite a <a href="http://dustycloud.org/tmp/campaign_estimations.txt">few calculations</a> to make sure the rewards
  146. wouldn't cost so much as to not make the campaign worth it), and then
  147. came the really huge task: the pitch video itself. Work started in
  148. late August. The plan was that this would all go live on September
  149. 1st. That gave us less than a month and a half to wrap it up and get
  150. it going.
  151. </p>
  152. <p>
  153. Here is the exact outline of tasks that we planned out:
  154. </p>
  155. <p class="verse">
  156. Aug 23-25:<br />
  157. <ul>
  158. <li>Timeline nailed down</li>
  159. <li>Chris's local reference script pieced together</li>
  160. <li>Agree on amount to pay schendje</li>
  161. <li>Talk with schendje about pay and timeline</li>
  162. </ul>
  163. Week of Aug 26:<br />
  164. <ul>
  165. <li>Work with the FSF to find out everything about what the theming is</li>
  166. <li>Storyboard finished (mid-week)</li>
  167. <li>Animation tests done</li>
  168. <li>Ideally, animatic done</li>
  169. <li>Chris Webber should find out and get to Deb (&amp; Carl) what the aspect ratios / formats best are</li>
  170. <li>Coordinate any work for audio and video recording with other people</li>
  171. <li>Deb and Chris work out draft phrasing and page layoutish content</li>
  172. </ul>
  173. Week of Sep 2:<br />
  174. <ul>
  175. <li>final storyboard signed off on (start of week)</li>
  176. <li>Reward decisions researched</li>
  177. <li>As much non-"face recording" work as can be done for the video as</li>
  178. <li>Deb and I should have videos of ourselves recorded</li>
  179. <li>Deb should get video of herself recorded to me</li>
  180. <li>Voiceovers done or mostly so</li>
  181. <li>Animations done</li>
  182. <li>Background music, if using, should be looked for</li>
  183. </ul>
  184. Week of Sep 16:<br />
  185. <ul>
  186. <li>Writing for pitch page done</li>
  187. <li>FSF should have things working</li>
  188. <li>Writing for fundraising page done</li>
  189. <li>Theming should be done</li>
  190. <li>Donation progress bar should be working</li>
  191. <li>Video mostly edited</li>
  192. <li>Talking to reporters? (or is this next week?)</li>
  193. </ul>
  194. Week of Sep 23:<br />
  195. <ul>
  196. <li>Final video edits</li>
  197. <li>Video transcoded and put in place</li>
  198. <li>Final tests and etc</li>
  199. </ul>
  200. </p>
  201. <p>
  202. This was a lot to do in not a lot of time (my <a href="http://orgmode.org/">org-mode</a> tree for the
  203. "Crowdfunding campaign" task is 3300 lines of text long, though that
  204. includes post-campaign tasks also, and for the most part I did not
  205. take breaks over this month and a half of work), and one thing I knew
  206. from seeing the success and failure of other campaigns was that things
  207. had to look good. And more important than anything else, the campaign
  208. video pitch had to be stellar. We could be cynical about this: we are
  209. catering to a certain amount of flashy visuals and shallowness. I
  210. remember watching the <a href="http://www.kickstarter.com/projects/ouya/ouya-a-new-kind-of-video-game-console">Ouya campaign</a> and thinking "they haven't put any
  211. useful substance in this video" and thus feeling very suspicious of it
  212. (I guess it looks like they're making <a href="http://mashable.com/2013/01/03/ouya-unboxed/">real stuff</a> so maybe I should
  213. stop being so wary). But what really made that campaign raise so much
  214. money? Was it proof that they had the architectural ability to
  215. produce a console that was really useful? I really didn't think that
  216. video had much substance in it; it was mostly flashiness. But it also
  217. was the right kind of flashiness for the audience it was going for,
  218. and it raised the money it needed to raise.
  219. </p>
  220. <p>
  221. Looks aren't everything though either, and I didn't want to make
  222. something vaporous. Will pointed to
  223. <a href="http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-but-with-your-own">Joey Hess's git-annex assistant campaign video</a>
  224. which is kind of awesomely the opposite of the Ouya video: it explains
  225. clearly what it wants to do but doesn't look flashy and shiny at all.
  226. (It probably helps that everyone knows who the heck Joey Hess is.)
  227. And there are also some nicer examples that fall in the middle... <a href="http://www.kickstarter.com/projects/1331941187/the-tube-open-movie">Tube</a>
  228. is by people I trust and made a kick-ass video that was visually
  229. appealing, felt like it matched the film they were producing, and also
  230. explained what they were doing clearly. That's the kind of video I
  231. was more interested in making.
  232. </p>
  233. <p>
  234. But I'm not a film-maker, and it was hard to know if this was
  235. something I could really do. A few years ago I read an interesting
  236. book titled <a href="http://www.amazon.com/Animating-Blender-Creating-Animations-Finish/dp/0240810791">Animating With Blender</a> which I thought was more useful
  237. for its instructions on how to organize a film than how to actually
  238. use Blender itself. It really illuminated how to make a film from
  239. start to finish for me.
  240. </p>
  241. <p>
  242. So the approach we took was very structured, and I took it in steps:
  243. </p>
  244. <ul>
  245. <li>I wrote an outline of the script I imagined. At this stage, it was
  246. harder to get feedback I discovered, not really enough info to
  247. convey the script I had in mind.
  248. </li>
  249. <li>I turned it into an <a href="http://dustycloud.org/misc/pitch_script.txt">actual script</a> with spoken lines and textual
  250. descriptions of what would be appearing on the screen shot for
  251. shot. This was a lot easier to get feedback on; Deb, Will and I
  252. talked about it, but I especially had a lot of back and forth
  253. emails with Deb while we ironed out exactly what the lines would
  254. be.
  255. </li>
  256. <li>With a clear script, I then produced a <a href="http://dustycloud.org/tmp/mediagoblin_animatic.webm">story reel with test audio</a>
  257. (which I mistakenly called an animatic... it isn't.) Many of the
  258. things shown in here were just images that I thought were "close
  259. enough" to conveying the thing at the moment which I had around.
  260. There were also the node animations; I spent some time in this
  261. period carefully deciding what the aesthetics of those two short
  262. animated scenes would be.
  263. </li>
  264. <li>I searched around to find some appropriate music; I tried a bunch
  265. of pieces including some folksy acoustic ones and jokingly showed
  266. Will one with <a href="http://opengameart.org/content/grassy-world-overture-8bitorchestral">a bit of overly-epic chiptune music</a> that I liked.
  267. Will actually said that this was the right call and I should go
  268. with it, saying something along the lines of "It <i>should</i> be epic
  269. and over the top! This isn't Prairie Home Companion, we aren't
  270. sitting around eating corn cobs. This is the fight for the future
  271. of the internet!" I went with that one after all.
  272. </li>
  273. <li>I worked on the render tests of <a href="http://dustycloud.org/tmp/nodetest2.webm">the nodes</a> and the <a href="http://dustycloud.org/tmp/police_scan.webm">police scanner</a>.
  274. Until I got these tests done, I was still afraid that the
  275. animations were something I wouldn't be able to pull off.
  276. </li>
  277. <li>Deb and I started doing voice and video recordings. This was a bit
  278. tough, and in retrospect we should have used some time together to
  279. visit a professional's house and get said recordings. As it was,
  280. we both recorded separately on crappy microphones and not ideal
  281. camera equipment. I spent a ton of time cleaning up audio in
  282. audacity, re-recording stuff myself, and pestering Deb with
  283. requests of things to re-record. (I am sure I was annoying about
  284. this, not to mention that she was in the middle of planning her
  285. wedding! Thanks for being patient, Deb.) I think more than
  286. anything, I underestimated how important it was to get this part
  287. down right, and I spent a lot of time being afraid that our crappy
  288. setups would ruin the video and everyone would dismiss it and not
  289. donate it because they could hear audio crackle. (I was probably
  290. more afraid of this than was rational.)
  291. </li>
  292. <li>I wrote some python scripts to be able to allow me to create the
  293. animated node graph quickly with adjustments.
  294. </li>
  295. <li>I did the actual animation of the node graph things. There were
  296. some hiccups, my police graph rig was hacky, but I have to say,
  297. this was the most fun thing for me for the entire campaign.
  298. </li>
  299. <li>I made a ton of screenshots of MediaGoblin.
  300. </li>
  301. <li>I made a number of video recordings of me doing certain small
  302. things like scrolling through <a href="http://identi.ca">identi.ca</a> or starting up a
  303. MediaGoblin process. I did more takes of these than is probably
  304. rational.
  305. </li>
  306. <li>I asked Joar Wandborg to make videos of himself eating and upload them to
  307. MediaGoblin. If you re-watch the video you'll know what part I
  308. mean.
  309. </li>
  310. <li>I knocked out the drawings that appear in the video.
  311. </li>
  312. <li>I abused my friendship with my friend Bassam Kurdali and asked him
  313. for more Blender tips than is fair or reasonable.
  314. </li>
  315. <li>I did the video editing of the whole shebang in Blender's video
  316. editor. I might have had more anxiety about the audio quality
  317. part, but I had more actual frustration over this than anything
  318. else. It wasn't the actual placing the timing or strips of
  319. things... it was putting videos on the sequence editor and
  320. battling encoding issues for <i>literally days on end</i>.
  321. </li>
  322. <li>I cut up the audio that we were using and put it in place and made
  323. the credits.
  324. </li>
  325. <li>And of course, I did the final render. My computer smoldered for
  326. a good 9 hours, and the campaign video was complete.
  327. </li>
  328. </ul>
  329. <p>
  330. When you work on something like that for that long, it's hard to
  331. not mostly just focus on all the mistakes you made. But honestly, I
  332. am damned proud of that campaign video. I think it sent all the
  333. right messages clearly, I think it looks awesome, and I think it was
  334. the right length. I feel good about it.
  335. </p>
  336. <p>
  337. There was quite a bit more to do also and we ended up being a bit
  338. farther behind than I expected by a week and a half. Still, we got
  339. all that done in only a little over a month and a half.
  340. </p>
  341. <p>
  342. Finally, everything was ready: the video, the campaign page text, the
  343. rewards decisions, the little icons that went with the rewards (done
  344. by my friend Alex Camelio), the FSF donations page... it was time to
  345. launch.
  346. </p>
  347. <div id="outline-container-2-3" class="outline-3">
  348. <h3 id="sec-2-3">The campaign begins</h3>
  349. <div class="outline-text-3" id="text-2-3">
  350. </div></div><p>
  351. <a href="http://mediagoblin.org/news/crowdfunding-campaign-launches.html">We launched!</a>
  352. </p>
  353. <p>
  354. The campaign launch was exciting. We put out a blogpost, the FSF put
  355. out notices to their own campaign, a lot of people spread the message
  356. on various channels, and money started to come in. At this point I
  357. was relieved that things had finally set off; I thought I might have
  358. a chance to finally relax in comparison to all the pre-campaign work
  359. I had done.
  360. </p>
  361. <p>
  362. Well, I was very wrong there. :)
  363. </p>
  364. <p>
  365. Before I get into what happened, Will put together an
  366. <a href="http://bluesock.org/~willg/cgi-bin/campaign.cgi">analytics script</a>. It's interesting to look at:
  367. </p>
  368. <p>
  369. <img src="http://dustycloud.org/misc/mediagoblin_campaign_graph.png" alt="http://dustycloud.org/misc/mediagoblin_campaign_graph.png" />
  370. </p>
  371. <p>
  372. Initially things went easily: the people who were most likely to
  373. donate jumped onto donate. I remember going out to lunch with a
  374. MediaGoblin donor who turned out to be from Madison; over the course
  375. of lunch, the campaign went up $600. But it didn't stay easy.
  376. </p>
  377. <p>
  378. What I discovered is what anyone who's had to do fundraising already
  379. knows: it's a real slog. You have to keep up momentum, and for a
  380. large part, that means getting out messaging every day. We had a lot
  381. of advantages: Deb knows a lot of people in the tech media, we had the
  382. FSF as a connection, we had a solid video and good branding, we had an
  383. awesome feature (3d media support!) land mid-campaign, and so on.
  384. </p>
  385. <p>
  386. The details are kind of boring and I'm not going to go into them, but
  387. what I learned the hard way is two things:
  388. </p><ul>
  389. <li>There's a point where fundraising slows down. You can see that on
  390. the graph already.
  391. </li>
  392. <li>If you step away from messaging, things basically grind to a halt.
  393. </li>
  394. <li>It's really hard to keep messaging interesting for a whole month,
  395. though.
  396. </li>
  397. </ul>
  398. <p>
  399. There was a week where I <a href="http://mediagoblin.org/news/fsws-2012-wrap-up.html">went to the Federated Social Web Summit</a> and
  400. also flew in to help CC with interviews for a position it was hiring
  401. for. I thought it was really important to go, and it turned out to be
  402. a useful thing to blog about after. But during that week, money
  403. basically stopped coming in altogether because I also dropped off of
  404. messaging. It probably would have slowed anyway, but it was hard to
  405. not be gripped by anxiety by everything just totally grinding to a
  406. halt fundraising wise. There's a certain part during fundraising
  407. where your feeling of self worth is proportional to how fast the
  408. fundraising level is climbing, so in times like that, it can be hard.
  409. </p>
  410. <p>
  411. Luckily, one major thing happened for us: the FSF helped secure a
  412. <a href="http://mediagoblin.org/news/10k-campaign-matching.html">10k matching grant</a>. (You might see a huge spike on the graph; that's
  413. the 10k grant coming in.) As important as the 10k grant itself was,
  414. when things were slow, it gave us an extra thing to rally around. I'm
  415. very grateful to the FSF that they helped us line this up; I don't
  416. even know where I'd begin to start such a thing myself.
  417. </p>
  418. <p>
  419. Anyway, a ton of anxiety later, the campaign did wrap up. We shot for
  420. 60k and it was clear we weren't going to make it. But we also set the
  421. campaign a bit higher than we needed it to be. I told Deb and Will
  422. that "if we could just make 40k, I'd feel like it was a success". As
  423. the time came closer I wrote John saying that I was considering doing
  424. something crazy like lowering our final goal to 40k, since I was
  425. afraid nobody would donate at the end if it didn't look like we'd get
  426. close to our real goal (maybe they'd think it was Kickstarter-style
  427. and would think "well, they won't make it anyway"). John advised me
  428. that the end of these things tend to be tough but sit tight. So I
  429. did.
  430. </p>
  431. <p>
  432. We made 43k and I felt pretty awesome about it. We declared the
  433. campaign a <a href="http://mediagoblin.org/news/we-did-it.html">huge success</a>, and meant it.
  434. </p>
  435. <div id="outline-container-2-4" class="outline-3">
  436. <h3 id="sec-2-4">Post-campaign: rewards and a new routine</h3>
  437. <div class="outline-text-3" id="text-2-4">
  438. </div></div><p>
  439. The campaign is over, but that doesn't mean the work is over. There's
  440. been about a month of work after the end of the campaign spent working
  441. on trying to finish the rewards of donors to the campaign. I've
  442. actually enjoyed it; one thing about the campaign that I really like
  443. is that it's allowed me to mix in excuses to make good use of my
  444. artwork. (You may have noticed that the MediaGoblin project itself is
  445. sneakily set up to make use of my favorite skills in different ways.)
  446. But of course, the purpose of the campaign wasn't to fund rewards, it
  447. was to fund me working on MediaGoblin for a year. (Or, well at one
  448. point we thought there was the possibility that maybe we'd shoot so
  449. far over the campaign that we could pay multiple people... clearly
  450. that didn't happen :)) Thankfully, that's almost all done. I've
  451. finished all the artwork and Morgan has helped a whole lot on
  452. ordering things and vectorizing the mascot for the shirt and so on.
  453. </p>
  454. <p>
  455. Last week was the first time I finally felt like I spent a full,
  456. solid week on MediaGoblin doing code reviews, coding, and a bit of
  457. administrative work.
  458. </p>
  459. <p>
  460. It felt awesome.
  461. </p>
  462. <div id="outline-container-3" class="outline-2">
  463. <h2 id="sec-3">Was it worth it?</h2>
  464. <div class="outline-text-2" id="text-3">
  465. </div></div><p>
  466. I think it was worth it. I think it's also common to think about a
  467. campaign like this as "you set up the thing, then the money rolls in".
  468. Well, I don't know if that was true for other campaigns. It certainly
  469. wasn't true for ours. It was a lot of work.
  470. </p>
  471. <p>
  472. After all the costs of the campaign are removed, the "income" from the
  473. campaign will be a bit less than $35000 (I will be making the files
  474. related to the finances of the campaign public). Keep in mind also
  475. that the campaign started in September, so since I'm promising to work
  476. on MediaGoblin full time for all of 2013, that's not just a year,
  477. that's nearly 1 1/3 years (so that's closer to $26000/year if it were
  478. really a salary). That's not a huge salary for a programmer. It's
  479. both significantly less than half of what I made at CC, and less than
  480. what I made at my first time job as a datacenter monkey, and both of
  481. those had benefits. We're paying for our own insurance as-is. We can
  482. make it through 2013, but partway through the year I will also need to
  483. figure out how to fund things going forward.
  484. </p>
  485. <p>
  486. But it's also enough... not on its own, but as said, we have some
  487. savings, and I have some contracting that I can do. And it's actually
  488. also pretty good; sure, we didn't meet our goal, but there are other
  489. awesome projects like <a href="http://www.kickstarter.com/projects/1331941187/the-tube-open-movie">Tube</a>, <a href="http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-but-with-your-own">git-annex-assistant</a>, and <a href="http://www.kickstarter.com/projects/jmathai/openphoto-a-photo-service-for-your-s3-or-dropbox-a">OpenPhoto</a>, and
  490. actually if you look at those you realize we did pretty damned well.
  491. </p>
  492. <p>
  493. And it's afforded a rare opportunity: to do exactly what I want and
  494. believe in for a year. And that's something that I wouldn't have
  495. been able to justify otherwise.
  496. </p>
  497. <p>
  498. And so... I'm looking forward to this next year!
  499. </p>
  500. <p>
  501. <b>Addendum:</b> One thing I forgot to mention in all this is that during
  502. the middle of the MediaGoblin campaign, I got a lot of help from the
  503. community itself as they stepped up to take care of the codebase when
  504. I was in campaign-madness-mode. (Not to mention all the community
  505. help in promoting the campaign, or even in making MediaGoblin into
  506. anything at all!) So thanks, all. :)
  507. </p>