Kap. 1

Kap. 2

What Free and Open Source Can Do for You

Fassen Sie die wesentlichen Punkt zusammen, die eine Mitwirkung bei FOSS für die eigenen Karriere beitragen kann.

Kap. 3

Prepare to contribute

1. Es gibt viele Mitwirkungsmöglichkeiten, die nicht mit Kodieren zu tun haben. Welche könnten Sie sich vorstellen?
2. Welche grobe Rollenverteilung gibt es bei einem FOSS Projekt (Zwiebelmodell)?
3. Was bedeutet die Abkürzung BDFL?
4. Welche Dateien gibt es häufig bei FOSS Projekten?
5. Was ist ein "Code of Conduct"? Suchen Sie mindestens ein Beispiel im Netz?
6. Was ist ein Styleguide?
7. Was ist ein "Issue Tracker"? Welche konkreten Issue-Tracker sind Ihnen schon begegnet?
8. Welche Möglichkeiten zur Kommunikation gibt es? Ordnen Sie diese in verschiedene Kategorien ein.
9. Warum ist ein CLA oft eine schwierige Angelegenheit? Schauen Sie sich zum Beispiel das CLA von Microsoft an: https://cla.opensource.microsoft.com
10. Was ist ein "Developer Certificate of Origin"? Suche Sie im Netz nach einem.

Kap. 4

Find a project

• Set Your Goals with Goal Brainstorming
• Personal requirements (skills, interests, time, goals)
• Collect candidate projects
• Select a project
• Select a task

Kap. 5

Make a contribution

• Prepare
  • Review issue tracker
  • Set up environment
  • Text editors
  • Issue triage
  • Read the docs
• Craft
  • Gotchas (spaces, tabs, tab-size)
  • Clone and branch
  • Atomic commits
• Test
  • CI/CD
  • Diff your work
• Submit
  • Read the docs (CONTRIBUTING)
  • Pull Request
  • Patch
• Review, Revise and Collaborate
  • WIP:
  • Feedback
  • Tidy Up
  • Windows-based contributors

Kap. 6

Make a Difference Without Making a Pull Request

• Review contributions
• Provide testing
• Triage issues
• Volunteer for the Less Interesting Things

Kap. 7

Interact with the Community

• After your first contribution
• Get help
  • RTFM
  • How to ask a question
• General Tips for Participating in Discussions
• The Importance of Setting Up and Maintaining Expectations
• Communication Channels and How to Use Them

Kap. 8

It’s About the People

• Get Together (DebConf, ApacheCon, FOSDEM, ...)
• Moving Up in the Community
• FOSS is people

Kap. 9

When It Goes Wrong

• Intimidated by FOSS’ Reputation
• Can't Find a Project
• Company Policies (diagram equipment vs. time)
• Contribution Process is Unclear
• Language Barriers
• Your Contribution is Declined
  • The contribution appeared out of nowhere.
  • The contribution was good, but it wasn’t necessary.
  • The contribution was not to project standards.
  • The contributor has not signed the Contributor License Agreement.
  • The project members are mean.
• Community Problems
• Sometimes You are the Problem
• How to Exit a Community

Three rules of software contribution

1. Read all contributor documentation (and actually follow them).
2. Communicate and confirm before contributing.
3. Ask for feedback before submitting your contribution.

Kap. 10

Start Your Own Project

• producingoss.com ("POSS")
• README, User Guide, CONTRIBUTING, Code of Conduct (CoC), License
• What is Your Goal?
• Optimize for Community
• Keep everything as simple as possible
• Work in the Open
• Prevent Burnout
• Select Communication Routes
• Issue Tracking
• Styleguides
• License (https://opensource.org/licenses)
• How to Apply a License
  • Licensing File
  • Copyright Notice in every file
  • Copyright Year
• Publish

Berner Konvention

Kap. 11

Contribute for Your Job

• Contributing to FOSS in your job
• External projects, with some impact for the company
• Avoid legal problems for the company
• Employer may own the copyright of your contribution (see employment agreement)
• Project may have a CLA or DCO
• Your companies FOSS projects
• Convincing Your Employer to Support FOSS
• Benefits to the company