└── README.md


/README.md:
--------------------------------------------------------------------------------
  1 | <!--
  2 | # A handy guide to financial support for open source.
  3 | *"I do open source work, how do I find funding?"*
  4 | 
  5 | Below I've listed every way I know of that people get paid for open source work, roughly ordered from small to large. Each funding category links to several real examples. (Wherever possible, I've tried to link to a useful article or page instead of just a homepage.)
  6 | 
  7 | The categories are not mutually exclusive. For example, a project might have a foundation but also use crowdfunding to raise money. Someone else might do consulting and also have a donation button. Etc. The purpose of this guide is to provide an exhaustive list of all the ways you can get paid, so that you can figure out what works best for you.
  8 | 
  9 | 
 10 | ---
 11 | 
 12 | 
 13 | -->
 14 | 
 15 | # 开源项目挣钱实用手册
 16 | 
 17 | *"我在参与开源项目，但是我该如何挣钱呢？"*
 18 | 
 19 | 我列出了我从各种渠道所知道的开源项目带来收入的人们的故事，每种出资类型都有一系列的真实案例，粗略的按照出资量从小到大排列。（我已尽可能的将链接指向具体故事而非主页面）。
 20 | 
 21 | 本文中的出资类型并非互斥的，例如一个项目既可以由基金会也可以通过众筹来筹集资金，而一个人既可以靠咨询挣钱也可以获得捐赠。本文的主要目的是提供一个详尽的挣钱方式列表，而你只需要从中选出适合你的。
 22 | 
 23 | 本中文版是[原版](https://github.com/nayafia/lemonade-stand)的翻译版本。
 24 | 
 25 | 原项目名称 Lemonade Stand 是指销售柠檬汁的小摊，而在美国，这种小摊通常是由小朋友运作的。
 26 | 
 27 | ---
 28 | 
 29 | <!--
 30 | # Table of Contents
 31 | 1. [Donation button](#donation-button)
 32 | 2. [Bounties](#bounties)
 33 | 3. [Crowdfunding (one-time)](#crowdfunding-one-time)
 34 | 4. [Crowdfunding (recurring)](#crowdfunding-recurring)
 35 | 5. [Books and merchandise](#books-and-merchandise)
 36 | 6. [Advertising & sponsorships](#advertising--sponsorships)
 37 | 7. [Get hired by a company to work on project](#get-hired-by-a-company-to-work-on-project)
 38 | 8. [Start a project while currently employed](#start-a-project-while-currently-employed)
 39 | 9. [Grants](#grants)
 40 | 10. [Consulting & services](#consulting--services)
 41 | 11. [SaaS](#saas)
 42 | 12. [Dual license](#dual-license)
 43 | 13. [Open core](#open-core)
 44 | 14. [Foundations & consortiums](#foundations--consortiums)
 45 | 15. [Venture capital](#venture-capital)
 46 | 
 47 | APPENDIX: [Contributing to this guide](#contributing-to-this-guide) // [License & attribution](#license-and-attribution)
 48 | 
 49 | **"personal effort" notes when a funding effort was led by an individual, not a project*
 50 | 
 51 | -->
 52 | 
 53 | # 目录
 54 | 
 55 | 1. [捐赠按钮](#捐赠按钮)
 56 | 2. [悬赏](#悬赏)
 57 | 3. [众筹（一次性）](#众筹（一次性）)
 58 | 4. [众筹（持续性）](#众筹（持续性）)
 59 | 5. [卖书及周边](#卖书及周边)
 60 | 6. [广告](#广告)
 61 | 7. [受雇于公司并继续你的项目](#受雇于公司并继续你的项目)
 62 | 8. [在职时启动项目](#在职时启动项目)
 63 | 9. [补贴](#补贴)
 64 | 10. [咨询服务](#咨询服务)
 65 | 11. [SaaS](#saas)
 66 | 12. [双重协议](#双重协议)
 67 | 13. [开放核心](#开放核心)
 68 | 14. [基金会](#基金会)
 69 | 15. [风险投资](#风险投资)
 70 | 
 71 | 附录: [贡献](#贡献) // [协议](#协议)
 72 | 
 73 | **“个人努力” 用来标记其资金是由个人而非项目主导筹集获得的。**
 74 | 
 75 | 
 76 | <!--
 77 | ## Donation button
 78 | *Stick a donation button on your site. Stripe and PayPal are examples of services you can use to accept donations.*
 79 | 
 80 | -->
 81 | 
 82 | ## 捐赠按钮
 83 | 
 84 | 在你的网站页面里放上捐赠按钮。Stripe 和 PayPal 都可以很方便的提供这项服务。
 85 | 
 86 | <!--
 87 | #### Pros
 88 | * Few strings attached
 89 | * Little work involved: "set it and forget it"
 90 | 
 91 | -->
 92 | 
 93 | #### 优点
 94 | 
 95 | * 限制条件少
 96 | * 工作量小：放好后就可以不管了
 97 | 
 98 | <!--
 99 | ####Cons
100 | * Usually not much money unless you have dedicated fundraising efforts
101 | * Need a legal entity to donate to (ex. [SFC](http://sfconservancy.org), [OpenCollective](http://opencollective.com) are fiscal sponsors for this purpose). Harder for individuals or international donations to manage
102 | * Sometimes not clear who “deserves” money in a project or how it gets distributed
103 | 
104 | -->
105 | 
106 | #### 缺点
107 | 
108 | * 除非你努力筹款，通常都不会有太多钱
109 | * 需要一个法人实体来接受捐赠（[SFC](http://sfconservancy.org)、 [OpenCollective](http://opencollective.com)可在这方面提供帮助），因此较难管理个人的国际性捐赠
110 | * 在多人项目中很难明确如何分配这笔捐赠
111 | 
112 | <!--
113 | ####Case Studies
114 | * [Twisted](https://twistedmatrix.com/trac/wiki/WhyDonate)
115 | * [Git](https://git-scm.com/sfc)
116 | * [Transmission](https://www.transmissionbt.com/)
117 | 
118 | -->
119 | 
120 | #### 案例学习
121 | 
122 | * [Twisted](https://twistedmatrix.com/trac/wiki/WhyDonate)
123 | * [Git](https://git-scm.com/sfc)
124 | * [Transmission](https://www.transmissionbt.com/)
125 | 
126 | <!--
127 | ##Bounties
128 | *Sometimes, projects or companies post bounties for open source work (ex. "fix this bug and collect $100"). There are several websites, listed below, that help facilitate the posting and collection of bounties.*
129 | 
130 | -->
131 | 
132 | ## 悬赏
133 | 
134 | 项目或公司可能时不时的张贴开源项目的悬赏工作（例如“修漏洞赚 $100”），下面列出了一些网站，他们收集和发布了这类悬赏工作。
135 | 
136 | <!--
137 | ####Pros
138 | * Open to community participation
139 | * Money is tied to doing specific work (more like paying for service than donations)
140 | * Especially popular for security work
141 | 
142 | -->
143 | 
144 | #### 优点
145 | 
146 | * 参与到开源社区
147 | * 确定的工作有确定的回报
148 | * 在修复安全漏洞方面特别流行
149 | 
150 | <!--
151 | ####Cons
152 | * Can create perverse incentives in a project (low quality PRs, distracting priorities)
153 | * Usually not much money per bounty (~<$500)
154 | * Doesn’t provide recurring revenue
155 | 
156 | -->
157 | 
158 | #### 缺点
159 | 
160 | * 会在项目中产生不合理的激励机制（低质量的PR也会影响项目的专注性）
161 | * 通常没多少钱 (~&lt;$500)
162 | * 无法提供持久的收入
163 | 
164 | <!--
165 | ####Case Studies
166 | * [Bountysource](http://bountysource.com)
167 | * [GitHub Bug Bounty Program](https://bounty.github.com/)
168 | 
169 | -->
170 | 
171 | #### 案例学习
172 | 
173 | * [Bountysource](http://bountysource.com)
174 | * [GitHub Bug Bounty Program](https://bounty.github.com/)
175 | 
176 | <!--
177 | ##Crowdfunding (one-time)
178 | *If you have a specific idea you'd like to implement (rather than ongoing project work), a one-time crowdfunding campaign can help raise the funds you need. Both individuals and companies might be willing to donate to your campaign.*
179 | 
180 | -->
181 | 
182 | ## 众筹（一次性）
183 | 
184 | 如果你想实现一个特别的想法（区别于长期项目），一次性的众筹活动可以帮助你筹集到你需要的资金，许多个人和公司都可能会为你的想法捐款。
185 | 
186 | <!--
187 | ####Pros
188 | * Few strings attached
189 | * Can be easier for an individual to legally manage via, ex. [Kickstarter](https://kickstarter.com/)
190 | 
191 | -->
192 | 
193 | #### 优点
194 | 
195 | * 限制条件少
196 | * 对个人来说也可以很容易合法的进行，例如通过 [Kickstarter](https://kickstarter.com/)
197 | 
198 | <!--
199 | ####Cons
200 | * Lots of work involved to market campaign
201 | * Usually has to be tied to concrete outcome, perks
202 | * Usually not that much money (~$50K for one time)
203 | * Companies not always comfortable donating to campaigns
204 | 
205 | -->
206 | 
207 | #### 缺点
208 | 
209 | * 一大堆的市场工作需要做
210 | * 通常都需要为捐赠者提供回报甚至是特权
211 | * 通常钱也不是那么多（一次大约 $50K）
212 | * 公司并不常愿意向众筹捐款
213 | 
214 | <!--
215 | ####Case Studies
216 | * [Michal Papis + Rvm (personal effort)](https://www.bountysource.com/teams/rvm/fundraiser)
217 | * [Andrew Godwin + Django (personal effort)](https://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django)
218 | * [ribasushi + CPAN (personal effort)](https://www.tilt.com/tilts/year-of-ribasushi-help-him-focus-on-cpan-for-2016)
219 | * [RESTful WP-CLI](https://www.kickstarter.com/projects/danielbachhuber/a-more-restful-wp-cli)
220 | 
221 | -->
222 | 
223 | #### 案例学习
224 | 
225 | * [Michal Papis + Rvm (个人努力)](https://www.bountysource.com/teams/rvm/fundraiser)
226 | * [Andrew Godwin + Django (个人努力)](https://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django)
227 | * [ribasushi + CPAN (个人努力)](https://www.tilt.com/tilts/year-of-ribasushi-help-him-focus-on-cpan-for-2016)
228 | * [RESTful WP-CLI](https://www.kickstarter.com/projects/danielbachhuber/a-more-restful-wp-cli)
229 | 
230 | <!--
231 | ##Crowdfunding (recurring)
232 | *If you'd like to fund ongoing project work, you can set up a recurring crowdfunding campaign, with a monthly or annual financial commitment that renews indefinitely (or until the donor cancels). Those who use your project regularly (including both individuals and companies) might be willing to fund your work.*
233 | 
234 | -->
235 | 
236 | ## 众筹（持续性）
237 | 
238 | 如果你想要为持续性的项目筹集资金，可以设立一个持续性的众筹，捐赠者承诺按月或按年提供资金直到捐赠者退出。对于那些经常使用你的项目的个人或公司可能会愿意为你的项目提供资金。
239 | 
240 | <!--
241 | ####Pros
242 | * Few strings attached
243 | * Can be easier for an individual to legally manage via, ex. [Patreon](https://patreon.com), [Salt](https://salt.bountysource.com/), [Gratipay](https://gratipay.com/), [OpenCollective](https://opencollective.com)
244 | 
245 | -->
246 | 
247 | #### 优点
248 | 
249 | * 限制条件少
250 | * 对个人来说也可以很容易合法的进行，例如通过 [Patreon](https://patreon.com)、 [Salt](https://salt.bountysource.com/)、 [Gratipay](https://gratipay.com/)、 [OpenCollective](https://opencollective.com)
251 | 
252 | <!--
253 | ####Cons
254 | * Harder to get commitments to recurring donations (often requires preexisting brand/reputation)
255 | * Harder to explain concrete outcomes, perks that come with recurring donations
256 | * Usually not that much money (~$1-4K monthly)
257 | * Companies not always comfortable donating to campaigns
258 | 
259 | -->
260 | 
261 | #### 缺点
262 | 
263 | * 很难获得承诺的持续性捐赠（这通常需要你或项目已经有一定的名声）
264 | * 很难解释持续性的捐赠能获得什么样明确的回报或特权
265 | * 通常钱也不是那么多（一个月 $1-4K）
266 | 
267 | <!--
268 | ####Case Studies
269 | * [MochaJS](https://opencollective.com/mochajs)
270 | * [React-boilerplate](https://opencollective.com/react-boilerplate)
271 | * [jsbin](https://gratipay.com/jsbin/)
272 | * [Tom Christie + Django REST framework (personal effort)](https://fund.django-rest-framework.org/topics/funding/)
273 | * [Ruby Together](https://rubytogether.org)
274 | 
275 | -->
276 | 
277 | #### 案例学习
278 | 
279 | * [MochaJS](https://opencollective.com/mochajs)
280 | * [React-boilerplate](https://opencollective.com/react-boilerplate)
281 | * [jsbin](https://gratipay.com/jsbin/)
282 | * [Tom Christie + Django REST framework (个人努力)](https://fund.django-rest-framework.org/topics/funding/)
283 | * [Ruby Together](https://rubytogether.org)
284 | 
285 | <!--
286 | ##Books and merchandise
287 | *If you are an expert in a domain that other people might find useful to learn about, you could write and sell a book or series of books. You can find a publisher (like O'Reilly) or self-publish. In addition to selling books, some projects sell merchandise (ex. shirts, hoodies) to support their work.*
288 | 
289 | -->
290 | 
291 | ## 卖书及周边
292 | 
293 | 如果你是某个领域的专家，你可以写书卖书，可以找个出版社（像 O'Reilly）或自己出版（译者注：在中国不行）。除了卖书之外，有些项目也卖短袖外套等。
294 | 
295 | <!--
296 | ####Pros
297 | * Outcome not tied to project work itself, so you retain creative freedom
298 | * Can serve as marketing for the project itself
299 | * Can be recurring source of revenue after initial development
300 | 
301 | -->
302 | 
303 | #### 优点
304 | 
305 | * 筹集到的资金并不和项目本身管理关联，所以项目本身可以保持创作的自由
306 | * 销售的商品本身也可以当做为项目做的宣传
307 | * 在初次销售后可以成为持续性的资金来源
308 | 
309 | <!--
310 | ####Cons
311 | * Often not a significant source of revenue
312 | * Can distract from core development of project
313 | * Merchandise can have upfront costs
314 | 
315 | -->
316 | 
317 | #### 缺点
318 | 
319 | * 通常钱也不是那么多
320 | * 会影响用在项目上的精力
321 | * 卖周边需要准备预付资金
322 | 
323 | <!--
324 | ####Case Studies
325 | * [Lua](https://www.lua.org/pil/)
326 | * [Daniel and Audrey Roy Greenfeld + Two Scoops of Django (personal effort)](https://www.twoscoopspress.com/products/two-scoops-of-django-1-8)
327 | * [Sandi Metz + Practical Object-Oriented Design in Ruby (personal effort)](http://www.poodr.com/)
328 | 
329 | -->
330 | 
331 | #### 案例学习
332 | 
333 | * [Lua](https://www.lua.org/pil/)
334 | * [Daniel and Audrey Roy Greenfeld + Two Scoops of Django (个人努力)](https://www.twoscoopspress.com/products/two-scoops-of-django-1-8)
335 | * [Sandi Metz + Practical Object-Oriented Design in Ruby (个人努力)](http://www.poodr.com/)
336 | 
337 | <!--
338 | ##Advertising & sponsorships
339 | *If your project has a large audience, you can sell sponsorships to advertisers who might want to reach them. You probably have a very targeted audience (ex. if you have a Python project, you can assume your audience is likely people who are technically familiar with Python), so use that to your advantage.*
340 | 
341 | -->
342 | 
343 | ## 广告
344 | 
345 | 如果你的项目已经有了一定的受众，你可以帮助广告商向你的受众推销。通常你的项目都会有明确的受众，这是你的优势也是广告商所喜欢的。（比如你有一个 Python 项目，那么基本上可以假定你的受众一定是技术上熟悉 Python 的）
346 | 
347 | <!--
348 | ####Pros
349 | * Business model aligned with something people are willing to pay for
350 | 
351 | -->
352 | 
353 | #### 优势
354 | 
355 | * 这是成熟明确而且大众也能接受的商业模式
356 | 
357 | <!--
358 | ####Cons
359 | * Need large enough audience to justify sponsorships
360 | * Need to manage trust and transparency with user base (ex. no tracking)
361 | * Can be a lot of work to find and manage clients
362 | 
363 | -->
364 | 
365 | #### 缺点
366 | 
367 | * 需要足够多的受众才能请来广告商
368 | * 需要通过透明化来让受众相信你（比如让其信任你不会追踪他们）
369 | * 需要许多精力来寻找和管理广告商
370 | 
371 | <!--
372 | ####Case Studies
373 | * [Read the Docs](http://blog.readthedocs.com/ads-on-read-the-docs/)
374 | * [Hoodie](http://hood.ie/sponsoring/)
375 | 
376 | -->
377 | 
378 | #### 案例学习
379 | 
380 | * [Read the Docs](http://blog.readthedocs.com/ads-on-read-the-docs/)
381 | * [Hoodie](http://hood.ie/sponsoring/)
382 | 
383 | <!--
384 | ##Get hired by a company to work on project
385 | *Companies sometimes hire individuals to do open source work. Find a company that uses the project you want to work on. Often this is a split arrangement (ex. 50% company work, 50% open source work). Alternatively, if you have an idea for a new project, find a company that would be interested in using what you produce. In these situations, having demonstrated experience you can point to will be very helpful.*
386 | 
387 | -->
388 | 
389 | ## 受雇于公司并继续你的项目
390 | 
391 | 公司有时候会雇佣一些个人来做开源项目，你可以寻找一个正在使用你的开源项目的公司。当然具体在公司里可能公司工作和开源项目工作时间会是五五分。除此之外，也可以找一个愿意尝试使用你的新项目的公司。如果你有展示项目经验，这将会非常有用。
392 | 
393 | <!--
394 | ####Pros
395 | * Taps into those who have resources (i.e. companies)
396 | * Can be well-aligned with company needs
397 | * Steady income
398 | 
399 | -->
400 | 
401 | #### 优点
402 | 
403 | * 可以利用公司的资源
404 | * 可以很好的和公司的需求保持一致
405 | * 稳定的收入
406 | 
407 | <!--
408 | ####Cons
409 | * Usually involves “getting lucky”: no clear, repeatable path to finding this arrangement
410 | * Project already needs to be well-known and used
411 | * Person not contributing to company’s bottom line, which makes them expendable
412 | * Governance issues, company could have undue influence over project
413 | * Can affect project dynamics + balance
414 | 
415 | -->
416 | 
417 | #### 缺点
418 | 
419 | * 获得这样的机会需要极好的运气，现目前没有明确可重复的方式获得这样的机会
420 | * 项目通常需要非常出名并且被使用
421 | * 对于没有为公司的利润工作，这使得个人很容易被公司优先舍弃
422 | * 公司可能会过分影响项目的发展
423 | * 可能会因平衡不好两边而影响项目
424 | 
425 | <!--
426 | ####Case Studies
427 | * [Donald Stufft + Hewlett-Packard and Python packaging (personal effort)](https://twitter.com/dstufft/status/594119386333609984)
428 | * [Rich Hickey + Cognitect and Clojure](http://www.bizjournals.com/triangle/news/2013/09/17/durhams-relevance-to-merge-with.html?full=true)
429 | * [Aaron Patterson + ManageIQ and Ruby, Rails (personal effort)](http://community.redhat.com/blog/2014/09/tenderlove-joins-manageiq/)
430 | * [Ryan Dahl + Joyent and Node.js (opens a YouTube video) (personal effort)](http://www.youtube.com/watch?v=SAc0vQCC6UQ&t=29m20s)
431 | 
432 | -->
433 | 
434 | #### 案例学习
435 | 
436 | * [Donald Stufft + Hewlett-Packard and Python packaging (个人努力)](https://twitter.com/dstufft/status/594119386333609984)
437 | * [Rich Hickey + Cognitect and Clojure](http://www.bizjournals.com/triangle/news/2013/09/17/durhams-relevance-to-merge-with.html?full=true)
438 | * [Aaron Patterson + ManageIQ and Ruby, Rails (个人努力)](http://community.redhat.com/blog/2014/09/tenderlove-joins-manageiq/)
439 | * [Ryan Dahl + Joyent and Node.js (opens a YouTube video) (个人努力)](http://www.youtube.com/watch?v=SAc0vQCC6UQ&t=29m20s)
440 | 
441 | <!--
442 | ##Start a project while currently employed
443 | *Many open source projects started as employee side projects. The project might eventually outgrow the company, but starting it as a side project can be a great way to incubate the idea.*
444 | 
445 | *If you pursue this path, make sure you understand your company's policy on open source work. Some companies encourage employees to contribute to open source during working hours. Some might treat your open source work as a company project. Don't assume anything; ask someone at your company before starting.*
446 | 
447 | -->
448 | 
449 | ## 在职时启动项目
450 | 
451 | 许多开源项目最初都是员工的编外项目（Side Project），即便其最终可能会成长为一家公司，但以编外项目的形式在公司里进行孵化应该是不错的选择。
452 | 
453 | 如果你想走这条路，请确定你理解了公司在开源项目上的政策。有些公司鼓励员工在工作时间从事开源项目开发，而有些则将你的任何工作视作公司项目。不要假定任何前提，最好在开始前问问你公司里的相关人员。
454 | 
455 | <!--
456 | ####Pros
457 | * Freedom to test new ideas without worrying about salary
458 | * Can be well-aligned with company needs
459 | * Suitable for newer, experimental ideas
460 | 
461 | -->
462 | 
463 | #### 优点
464 | 
465 | * 可以不用担心收入的情况下尝试新想法
466 | * 可以和公司的需求很好的保持一致
467 | * 适合尝试新想法
468 | 
469 | <!--
470 | ####Cons
471 | * Need to do it as a side project or be approved to work on it during salaried time
472 | * Risk of undue company influence
473 | * Can lead to complicated governance later down the line
474 | 
475 | -->
476 | 
477 | #### 缺点
478 | 
479 | * 需要用业余时间开发，或者获准在工作时间开发
480 | * 有被公司过分影响的风险
481 | * 持续下去可能会出现极度复杂的管理情况
482 | 
483 | <!--
484 | ####Case Studies
485 | * [Mozilla and Rust](https://www.rust-lang.org/faq.html#is-this-project-controlled-by-mozilla)
486 | * [Google and Go](https://golang.org/doc/faq#history)
487 | * [Facebook and React](https://www.quora.com/How-was-the-idea-to-develop-React-conceived-and-how-many-people-worked-on-developing-it-and-implementing-it-at-Facebook/answer/Bill-Fisher-17)
488 | * [Futurice's open source program](http://futurice.com/blog/sponsoring-free-time-open-source-activities)
489 | 
490 | -->
491 | 
492 | #### 案例学习
493 | 
494 | * [Mozilla and Rust](https://www.rust-lang.org/faq.html#is-this-project-controlled-by-mozilla)
495 | * [Google and Go](https://golang.org/doc/faq#history)
496 | * [Facebook and React](https://www.quora.com/How-was-the-idea-to-develop-React-conceived-and-how-many-people-worked-on-developing-it-and-implementing-it-at-Facebook/answer/Bill-Fisher-17)
497 | * [Futurice's open source program](http://futurice.com/blog/sponsoring-free-time-open-source-activities)
498 | 
499 | <!--
500 | ##Grants
501 | *Grants are effectively large donations that do not require repayment. Oftentimes the grantmaker receives other benefits from giving you the grant, such as access to you, demonstration of impact, a report of your work, or tax benefits.*
502 | 
503 | *Grants can come from many places, including companies, software foundations, philanthropic foundations, and the government. The technical and legal aspects of a grant vary greatly depending on where it comes from. For example, a company might give you a "grant" but legally treat it as a consulting invoice. A philanthropic foundation can only make grants to nonprofits, so you would need to be a nonprofit yourself, or (more commonly) find a nonprofit to sponsor you. If you're unfamiliar with grants, the best way to understand how grants work is to talk to someone who has received one before. Some examples of grant recipients are listed below.*
504 | 
505 | -->
506 | 
507 | ## 补贴
508 | 
509 | 补贴是不需要偿还的极其有效的大笔捐赠，提供补贴的组织通常能够通过给予补贴而从其他方面获得利益，例如接近你，展示其影响力，获得你的工作汇报或税率优惠。
510 | 
511 | 补贴可能来自很多地方，包括公司、软件基金会、慈善基金会以及政府，其技术及法律方面会因其来源的不同有很大的差异。比如一家公司可以通过开咨询费发票给你补贴，而慈善基金会则只能给非盈利组织或个人，通常你得找到一个非盈利组织来帮助你。如果你对补贴不熟悉，了解它的最好方式就是和曾经获得过的人去了解。下面列出了一些成功的案例。
512 | 
513 | <!--
514 | ####Pros
515 | * Fewer strings attached
516 | * Guaranteed money can help project focus for an unbroken period of time
517 | * Gives project room to breathe and experiment
518 | 
519 | -->
520 | 
521 | #### 优点
522 | 
523 | * 限制条件少
524 | * 有保证的资金可以确保你能在一段时间里专注在你的项目上
525 | * 让你的项目有时间喘口气和做些试验
526 | 
527 | <!--
528 | ####Cons
529 | * There aren’t many software-related grantmakers (philanthropic, gov’t, corporate)
530 | * Grants are finite. Still need to find sustainability beyond the life of a grant
531 | 
532 | -->
533 | 
534 | #### 缺点
535 | 
536 | * 软件方面没太多提供补贴的组织
537 | * 补贴是有限的，始终需要在用完补贴前找到一个持续方法
538 | 
539 | <!--
540 | ####Case Studies
541 | * [Dat](https://usopendata.org/)
542 | * [Andrey Petrov + Stripe Open-Source Retreat and urllib3](https://medium.com/@shazow/urllib3-stripe-and-open-source-grants-edb9c0e46e82#.45ylnxrh4)
543 | * [Django + Mozilla Open Source Support](https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/)
544 | 
545 | -->
546 | 
547 | #### 案例学习
548 | * [Dat](https://usopendata.org/)
549 | * [Andrey Petrov + Stripe Open-Source Retreat and urllib3](https://medium.com/@shazow/urllib3-stripe-and-open-source-grants-edb9c0e46e82#.45ylnxrh4)
550 | * [Django + Mozilla Open Source Support](https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/)
551 | 
552 | <!--
553 | ##Consulting & services
554 | *Consulting can be a flexible way to fund open source work. You have more freedom to structure your time as you wish (for example, consulting 30 hrs of the week and spending 10 hrs of the week on open source work). Consultants can usually charge more for their time than salaried employees because the work is less steady, they don't receive benefits, etc. If you plan on doing this type of work regularly, you will probably want to set up an LLC (or equivalent outside of the US).*
555 | 
556 | *If your project is popular, you can also offer consulting & services around the project itself. For example, a client might pay you to implement the project for them, build something custom, or train them on how to use it.*
557 | 
558 | -->
559 | 
560 | ## 咨询服务
561 | 
562 | 咨询是一种为开源项目提供资金的灵活方式。你可以更加自由的规划你的时间，比如一周 30 小时做咨询业务，10 小时做开源项目。咨询师通常收费相对较贵，因为工作不稳定且没有公司福利。如果你打算做这类公司，你应该想要创建一家有限责任公司。
563 | 
564 | <!--
565 | ####Pros
566 | * Business model aligned with something people are willing to pay for
567 | 
568 | -->
569 | 
570 | #### 优点
571 | 
572 | * 这是成熟明确而且大众也能接受的商业模式
573 | 
574 | <!--
575 | ####Cons
576 | * Consulting requires human power, doesn’t scale well (except for rare outliers)
577 | * Business needs can distract from writing code or other tasks related to the project itself
578 | * Can be at odds with making software simple to use
579 | * Project needs to be sufficiently popular that people are willing to pay for related services
580 | 
581 | -->
582 | 
583 | #### 缺点
584 | 
585 | * 咨询工作需要人力，而且不宜规模化（除了极少数）
586 | * 商业本身的需求会分散开源项目上的注意力
587 | * 可能会和软件的简易要求有差异
588 | * 项目需要足够流行，才会让人愿意为相关服务付钱
589 | 
590 | <!--
591 | ####Case Studies
592 | * [Neighbourhoodie](https://neighbourhood.ie/)
593 | * [Baroque Software](http://baroquesoftware.com/)
594 | * [OpenSSL](http://openssl.com/what.html)
595 | 
596 | -->
597 | 
598 | #### 案例学习
599 | 
600 | * [Neighbourhoodie](https://neighbourhood.ie/)
601 | * [Baroque Software](http://baroquesoftware.com/)
602 | * [OpenSSL](http://openssl.com/what.html)
603 | 
604 | <!--
605 | ##SaaS
606 | *SaaS means [Software as a Service](https://en.wikipedia.org/wiki/Software_as_a_service). In this model, the codebase itself is open source, but you might offer additional paid services that make it easier for people to use your project. One common example of a paid service is charging for hosting.*
607 | 
608 | -->
609 | 
610 | ## SaaS
611 | 
612 | SaaS 即 [软件即服务（Software as a Service）](https://en.wikipedia.org/wiki/Software_as_a_service)。在这个模型下，代码本身是开源的，但是你可以提供增值服务使得用户更容易使用。一个典型的增值服务就是托管付费。
613 | 
614 | <!--
615 | ####Pros
616 | * Can build community around open project and make money off of services for hosting
617 | * Allows open source project to focus on users and as needs grow to help enterprises adopt the project
618 | * Can scale by number of users
619 | 
620 | -->
621 | 
622 | #### 优点
623 | 
624 | * 可以围绕这个开源项目建立一个社区，然后通过托管服务赚钱
625 | * 让开源项目可以专注在用户层面，当需求增加后再帮助企业采用这个项目
626 | * 可以根据用户数进行规模化改造
627 | 
628 | <!--
629 | ####Cons
630 | * Often means the hosting needs to be cheaper than hiring a dev to run the project for you.
631 | * “Two tiers” of product support can make free users unhappy
632 | 
633 | -->
634 | 
635 | #### 缺点
636 | 
637 | * 对增值服务使用者来说，通常意味着托管服务必须比招聘一个人来维护项目更便宜
638 | * 增值服务有可能会使得免费用户不太高兴
639 | 
640 | <!--
641 | ####Case Studies
642 | * [WordPress.com](http://wordpress.com/)
643 | * [Moodle](https://moodle.org/)
644 | * [Forge Laravel](https://forge.laravel.com/)
645 | * [Gitlab](http://gitlab.com)
646 | * [Sentry](https://getsentry.com/)
647 | * [Travis CI](https://travis-ci.org/)
648 | * [Ghost](https://ghost.org/)
649 | 
650 | -->
651 | 
652 | #### 案例学习
653 | 
654 | * [WordPress.com](http://wordpress.com/)
655 | * [Moodle](https://moodle.org/)
656 | * [Forge Laravel](https://forge.laravel.com/)
657 | * [Gitlab](http://gitlab.com)
658 | * [Sentry](https://getsentry.com/)
659 | * [Travis CI](https://travis-ci.org/)
660 | * [Ghost](https://ghost.org/)
661 | 
662 | <!--
663 | ##Dual License
664 | *Sometimes, projects offer an identical codebase with two different licenses: one that is commercially-friendly, and one that is less so (ex. GPL). The latter is free for anyone to use, but companies pay for the commercial license in order to have legal peace of mind.*
665 | 
666 | -->
667 | 
668 | ## 双重协议
669 | 
670 | 有时候项目可以在完全相同的代码里提供两种不同的授权协议：一个是商业友好的，而另外一个则不（例如 GPL）。后者对于个人来说可以免费使用，而公司需要通过购买商业协议来获得合法的商业授权。
671 | 
672 | <!--
673 | ####Pros
674 | * Business model aligned with something people are willing to pay for
675 | * Can scale well if successful
676 | 
677 | -->
678 | 
679 | #### 优点
680 | 
681 | * 这是成熟明确而且大众也能接受的商业模式
682 | * 如果成功的话，也可以做到规模化
683 | 
684 | <!--
685 | ####Cons
686 | * Can be at odds with making software freely accessible
687 | * Project needs to be big enough that customer need exists
688 | 
689 | -->
690 | 
691 | #### 缺点
692 | 
693 | * 会和让软件自由获得的理想有冲突
694 | * 项目需要足够大以满足客户的需求
695 | 
696 | <!--
697 | ####Case Studies
698 | * [MySQL](http://www.mysql.com/about/legal/licensing/oem/)
699 | * [SQLite](https://www.sqlite.org/copyright.html)
700 | 
701 | -->
702 | 
703 | #### 案例学习
704 | 
705 | * [MySQL](http://www.mysql.com/about/legal/licensing/oem/)
706 | * [SQLite](https://www.sqlite.org/copyright.html)
707 | 
708 | <!--
709 | ##Open core
710 | *Under an [open core](https://en.wikipedia.org/wiki/Open_core) model, some aspects of the project are free, but other features are proprietary and available only to paid users. Usually this works when there is enterprise demand for the project.*
711 | 
712 | -->
713 | 
714 | ## 开放核心
715 | 
716 | 在[开放核心](https://en.wikipedia.org/wiki/Open_core)模型中，项目的一些方面是免费的，但一些功能则是私有的，且只对付费用户开放，通常要求这个项目有企业的需求。
717 | 
718 | <!--
719 | ####Pros
720 | * Business model aligned with something people are willing to pay for
721 | * Can scale well if successful
722 | 
723 | -->
724 | 
725 | #### 优点
726 | 
727 | * 这是成熟明确而且大众也能接受的商业模式
728 | * 如果成功的话，也可以做到规模化
729 | 
730 | <!--
731 | ####Cons
732 | * Need to have something you can charge for (which means making certain features exclusive)
733 | * Can be at odds with making software freely accessible
734 | * “Two tiers” of product support can make free users unhappy
735 | 
736 | -->
737 | 
738 | #### 缺点
739 | 
740 | * 需要设计付费项目，且该项目应该是独有的
741 | * 会和让软件自由获得的理想有冲突
742 | * 独有功能有可能会使得免费用户不太高兴
743 | 
744 | 
745 | <!--
746 | ####Case Studies
747 | * [Docker](https://www.docker.com/)
748 | * [Elastic](https://www.elastic.co/)
749 | * [Mesosphere](https://mesosphere.com/)
750 | * [Sidekiq](http://sidekiq.org/)
751 | 
752 | -->
753 | 
754 | #### 案例学习
755 | 
756 | * [Docker](https://www.docker.com/)
757 | * [Elastic](https://www.elastic.co/)
758 | * [Mesosphere](https://mesosphere.com/)
759 | * [Sidekiq](http://sidekiq.org/)
760 | 
761 | <!--
762 | ##Foundations & consortiums
763 | *A [foundation](https://en.wikipedia.org/wiki/Foundation_(nonprofit)) is a legal entity that can accept and/or disburse donations. Because their purpose is not to make profits, they can be a great choice to signal neutrality and steward a project. In the US, foundations are either 501c3 (nonprofit) or 501c6 (trade consortium). Many software foundations are 501c6 because 501c3s require demonstrating a charitable purpose, which can be more difficult in software.*
764 | 
765 | -->
766 | 
767 | ## 基金会
768 | 
769 | [基金会](https://en.wikipedia.org/wiki/Foundation_&#40;nonprofit&#41;)是可以接收和支出的合法法人实体。鉴于其目的并非获得利润，因此可以更好保持中立地管理项目。在美国，基金会可以是 501c3（非盈利）或 501c6（贸易联盟），许多软件基金会都是贸易联盟，因为非盈利基金会要求展示出慈善的目的，这在软件开发中比较困难。
770 | 
771 | <!--
772 | ####Pros
773 | * Neutrality. Foundation protects the code and helps steward community
774 | * Influence distributed across multiple donors
775 | * Can legitimize project, companies might feel more comfortable giving to foundations than individuals
776 | 
777 | -->
778 | 
779 | #### 优点
780 | 
781 | * 中立，基金会可以帮助保护代码和管理社区
782 | * 可以在许多捐赠者中散布影响力
783 | * 使得项目合法，公司会更愿意向基金会付款/捐赠而非个人
784 | 
785 | <!--
786 | ####Cons
787 | * Only really worth it for big projects
788 | * Difficult to set up for IRS reasons (many do 501c6 instead of 501c3), restrictions on what you can do
789 | * Requires serious community effort and diverse skills (you still need to fundraise after setting up the entity!)
790 | 
791 | -->
792 | 
793 | #### 缺点
794 | 
795 | * 只适合大项目
796 | * 由于 IRS 的限制，项目能做什么会有所限制
797 | * 需要大量社区的努力和各种技能，而且之后仍旧需要努力获得筹款
798 | 
799 | <!--
800 | ####Case Studies
801 | * [Ruby Together](http://rubytogether.org/)
802 | * [Python Software Foundation](https://www.python.org/psf/)
803 | * [Node.js Foundation](https://www.sitepoint.com/goodbye-joyent-hello-node-js-foundation/)
804 | 
805 | -->
806 | 
807 | #### 案例学习
808 | 
809 | * [Ruby Together](http://rubytogether.org/)
810 | * [Python Software Foundation](https://www.python.org/psf/)
811 | * [Node.js Foundation](https://www.sitepoint.com/goodbye-joyent-hello-node-js-foundation/)
812 | 
813 | <!--
814 | ##Venture capital
815 | *Venture capital is a form of funding for high growth businesses. Unlike a bank loan or other forms of debt financing, venture capitaists take equity (a percent ownership in your business) in exchange for funding. The tradeoff is that unlike taking out a loan, you don't have to repay your creditors if your business tanks. If you do succeed, however, you should expect to return capital to your investor at a multiple.*
816 | 
817 | *Venture capital is "high risk high reward": VCs are more risk tolerant than, say, a bank, but they also expect a large payoff if you are successful. If you plan on raising venture capital, you should set up a business entity structured as a C Corp, preferably Delaware. If you're unfamiliar with the venture capital process, the best place to start is by reaching out to similar founders who have successfully raised venture.*
818 | 
819 | -->
820 | 
821 | ## 风险投资
822 | 
823 | 风险投资是高增长业务的一种筹资形式，不像银行贷款或者任意一种债务财务形式，风险投资者通过提供资金来占有你业务的一定股份。这种交易不像贷款，如果你的业务挂了你并不需要偿还出资方。当然，如果你成功了，你也需要成倍的返还给你的投资者。
824 | 
825 | 风险投资是高风险高回报的：风投者相比银行对风险更加宽容，当然他们也期待你成功后的巨额回报。如果你打算获得风险投资，你应该建立股份有限公司。如果你对风险投资过程不熟悉，开始的最好方式就是询问成功获得风险投资的人。
826 | 
827 | <!--
828 | ####Pros
829 | * Institutional support can be helpful for growing a business
830 | * Large amounts of capital available
831 | 
832 | -->
833 | 
834 | #### 优点
835 | 
836 | * 制度上的支持对成长中的业务有益
837 | * 大量的风投资金蓄势待发
838 | 
839 | <!--
840 | ####Cons
841 | * Venture capital comes with expectations of an exit (i.e. returning the money to investors at a multiple). History suggests this is structurally difficult to achieve for open source businesses
842 | * Venture capital can change motivations and distract from priorities
843 | 
844 | -->
845 | 
846 | #### 缺点
847 | 
848 | * 风险投资在投资之初便做好了获得成倍回报后退出的打算，历史证明，由于开源项目的结构特点，风险投资的成功很难
849 | * 风险投资者可能会因为优先级改变其动机
850 | 
851 | （译者注：在中国有一类风险投资者故意诱导涉世不深的创业者签订不平等协议，尤其是在创业者热情最浓而又最困难的时候，使其在业务失败时也能全身而退，相应的，创业者会输得很惨，值得小心对待）
852 | 
853 | <!--
854 | ####Case Studies
855 | * [Npm](http://blog.npmjs.org/post/76320673650/funding)
856 | * [Confluent](http://www.confluent.io/blog/confluent-raises-a-series-b-funding)
857 | * [NodeSource](https://techcrunch.com/2015/02/09/nodesource-raises-3-million-to-build-new-programming-tools/)
858 | * [Meteor](http://info.meteor.com/blog/announcing-our-20m-series-b-funding)
859 | 
860 | ---
861 | 
862 | -->
863 | 
864 | #### 案例学习
865 | 
866 | * [Npm](http://blog.npmjs.org/post/76320673650/funding)
867 | * [Confluent](http://www.confluent.io/blog/confluent-raises-a-series-b-funding)
868 | * [NodeSource](https://techcrunch.com/2015/02/09/nodesource-raises-3-million-to-build-new-programming-tools/)
869 | * [Meteor](http://info.meteor.com/blog/announcing-our-20m-series-b-funding)
870 | 
871 | --
872 | 
873 | <!--
874 | ### Contributing to this guide
875 | I wrote up this guide to aggregate knowledge off the top of my head, but I'm not planning to make major contributions or changes. I recognize the pros/cons are somewhat subjective, but they reflect my views.
876 | 
877 | If something is factually incorrect (especially with a case study example), I welcome your edits. Also, if there's a category you know of that I missed, I would also welcome that addition.
878 | 
879 | -->
880 | 
881 | ## 贡献
882 | 
883 | 我写这个手册主要是为了将我头脑中的知识都整理出来，不过我并没有打算做主要的贡献或改变。优点和缺点大多是从我的观点出发的主观想法。
884 | 
885 | 如果有什么错误（尤其是案例学习），非常欢迎大家的修改。同时，如果发现有什么分类漏掉了，我也非常欢迎大家的修改。
886 | 
887 | 关于中文版的贡献，如果有信息上的错误或遗失，请到原文中提出，如果有中文翻译上的错误，请在这里直接提出。如果你觉得有信息上的错误或遗失，但又各种原因无法用英文表述，担心中文表述不会被采纳，这种情况请还是在原文中提出，我或者其他同时会英文和中文的小伙伴会帮助解决问题的。
888 | 
889 | 本翻译项目使用[翻译辅助工具](https://github.com/wizicer/TranslationTool)辅助同步原文修订部分。
890 | 
891 | <!--
892 | ### License and attribution
893 | This guide is available under the Creative Commons CC0 1.0 License, meaning you are free to use it for any purpose, commercial or non-commercial, without any attribution back to me (public domain). If you do use it, I'd love to hear about it! (Find me here: [@nayafia](http://twitter.com/nayafia)) But you are in no way required to do so.
894 | 
895 | -->
896 | 
897 | ## 协议
898 | 
899 | 原文协议为Creative Commons CC0 1.0 License，即你可以自由的使用，商业或非商业，不过如果你用了，很开心能从你那里听到点什么，在这里找到我[@nayafia](http://twitter.com/nayafia)，当然这并不是要求必须做的。
900 | 
901 | 中文版协议为Creative Commons Attribution 4.0 International License，和原文协议差不多了，基本上可以说怎么用都可以，唯一不要修改原作者名字或以原作者名字声明演绎作品就可以了。
902 | 
903 | ![](https://i.creativecommons.org/l/by/4.0/88x31.png)
904 | 


--------------------------------------------------------------------------------