We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

The Trouble with FreeBSD

Formal Metadata

Title
The Trouble with FreeBSD
Subtitle
How did the FreeBSD community become what it is today?
Title of Series
Number of Parts
31
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date2017
LanguageEnglish

Content Metadata

Subject Area
Genre
Abstract
This provides a discussion in to how the FreeBSD community has become what it is, what some of its problems are and one or two ideas on how to fix it. An open source project’s community is what makes it a living thing. Without its community the project is a static lump of code. FreeBSD is one of the largest and longest continuously running open source projects around. Not only that, it comes from an even longer lineage before it via the original BSD work at the University of California, Berkeley. That doesn’t necessarily mean that it is without its problems. While FreeBSD isn’t in any danger of disappearing any time soon, it does have issues with attracting new contributors, keeping its existing contributors and keeping its community healthy. These issues are not always unique to FreeBSD but FreeBSD provides an interesting case study. This presentation will cover: How FreeBSD’s community and its processes have evolved over the years and how this compares to other, often newer, projects. What FreeBSD could learn from other projects. How this all fits into broader issues around open source development communities and things that do and don’t work.