Describe Origination

how to floss projects get created
- forking an existing open source project
  - mangement of existig project "run out of steam"
  - users decide to take development of themselves
- some decides to apply an open source licence
  - e.g., individual or member of team with appropriate responsibility
Motivation for release as floss
- giving back to community
- seeking addition team members, code or otherwise
- grow ecosystem around the software system
  - essentially a form of publicity

Detail Roles

Team shape
- depends of specifics and scale of project
- small projects often driven by an individual
- a few developers collaborate closely - often code founders
- large potentially open team combine contributions
different jobs and skill sets beyond coding
- documentation - creating and updating
- code review - pre-merge and post-merge quality control
- testing - developing tests (or test suites), and reporting back user bugs
- community - keeping team motivated and focused

required governance processes similar in big projects
- can benefit from manageing multiple projects together
e.g. apache software foundation (ASF)
- american non-profit
- manages more than 350 projects
- can share governance, management, and commounity
  - conferences (apacheCon) bringing community together
many others e.g., free software foundation (GNU)

foundations reputation: projects must he high quality
- but also want to be boradly accepting
ASF has Apache incubator
- new projects gain inital ASF linkage
- see if projects demonstrate continued development activity
- see if projects are popular iwth end users
Large organisations can donate code to incubator
- need to be sure that code can be maintained
- e.g., google wave