AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Open-source projects require ongoing support and maintenance, which can be costly. Contributors should be willing to take on the responsibility of keeping projects going even if the primary funding company changes direction or loses interest. It is important for projects to have clear governance models and for contributors to exercise their rights to fork the project if necessary. Companies sponsoring open-source projects should appreciate the value of the community and the contributions they make.
Open-source projects should clearly communicate their direction and goals. This includes being transparent about the governance model and making it clear if the project is a dictatorship or if there is room for community input. Projects should also provide extension APIs and interfaces to allow for experimentation and customization while maintaining core stability. The concept of freeloading should be abandoned, as everyone benefits from the shared collaboration and contributions in the open-source community.
Contributors to open-source projects, whether through code, documentation, or community support, should be appreciated and acknowledged for their time and effort. Companies should recognize that downloads and usage do not equate to direct monetization and should not expect contributors to work for free. It is important to foster a sense of gratitude and respect for the community's contributions.
Open-source projects need to strike a balance between community contributions and commercial interests. While it is essential to listen to the community and value their input, the project's core direction should ultimately prioritize long-term sustainability and viability. Providing clear guidelines and plugin systems can allow for experimentation and customization while maintaining the project's integrity and stability.
Open source projects should have clear values that reflect the personalities and philosophies of the creators. Having strong leadership and clarity on values helps engage the community and makes decision-making more predictable. Projects with clear values are more likely to be successful and garner trust within the community.
Deciding when to open source software requires careful consideration. It is important to have a clear business model and understand whether the software will have a viable market. Opening up the source code should be done with a clear roadmap and a path to version 1. Additionally, evaluating whether an ecosystem can be created around the software is also crucial when making the decision to open source.
DevRel (Developer Relations) and advocacy play important roles in open source projects. DevRel involves building and maintaining relationships with developers and the community, while advocacy focuses on promoting the software and making it accessible to others. It is important for companies and individuals to understand the role of DevRel, ensure sustainability, and align it with the broader goals of the project.
Kelsey Hightower joined Bryan and Adam to revisit a topic Bryan had spoken about a decade ago: corporate open source anti-patterns. Kelsey brought his typical sagacity to a complex and fraught topic.
We've been hosting a live show weekly on Mondays at 5p for about an hour, and recording them all; here is the recording from August 28th, 2023.
In addition to Bryan Cantrill and Adam Leventhal, we were joined by Kelsey Hightower.
Here is the (lightly edited) live chat from the show:
Listen to all your favourite podcasts with AI-powered features
Listen to the best highlights from the podcasts you love and dive into the full episode
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
Listen to all your favourite podcasts with AI-powered features
Listen to the best highlights from the podcasts you love and dive into the full episode