quartz/content/notes/22-open-source-software.md

title	aliases	tags
22-open-source-software		cosc202 lecture

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

Contrast Governance vs management

Sketch OSS foundations

Understand sustainability challenges