| • Jan Lehnardt's background in open source and how he got started | |
| • His involvement with CouchDB and becoming an evangelist for it | |
| • The community aspects of CouchDB and his role as vice-president of Apache CouchDB | |
| • Comparison between the PHP community and CouchDB community, including cultural differences | |
| • Discussion on healthy communities, contributor funnels, and drive-by contributions in open source projects | |
| • Jan Lehnardt's personal growth and development as an empathetic person | |
| • Twitter culture and Jan's decision to focus on being nice online | |
| • CouchDB community building and growth | |
| • Jan's experiences as a speaker and advocate for CouchDB | |
| • Lessons learned from the CouchDB community applied to Hoodie project | |
| • Challenges of balancing popularity with health in open source projects | |
| • Defining "popular" and "healthy" open-source projects | |
| • Metrics for measuring project success (ratio of contributors to users) | |
| • Strategies for attracting and retaining new contributors (modularity, documentation, beginner-friendly issues) | |
| • The contributor funnel: from casual contributions to dedicated membership | |
| • Mentorship: its importance and limitations in onboarding new contributors | |
| • Importance of meeting people where they are in contributing to open source projects | |
| • Value of breaking down complex tasks into smaller components for easier contribution | |
| • Benefits of having a dedicated team for non-technical aspects, such as marketing and documentation | |
| • Metrics of a healthy community, including the importance of attracting long-term contributors | |
| • Dangers of relying on a single maintainer or sponsor to sustain a project | |
| • Importance of involving the community in decision-making and contributing to a project's growth | |
| • Challenges of scaling a project and maintaining community engagement | |
| • Guilt-tripping contributors into excessive work and burnout prevention | |
| • Creating inclusive environments for under-represented groups in open source projects | |
| • Adapting conference learnings (e.g. JSConf EU) to code projects (e.g. Hoodie) | |
| • Implementing community guidelines, codes of conduct, and contributor covenants | |
| • Overcoming community inertia and changing existing power dynamics | |
| • Strategies for successfully implementing new community models in established projects | |
| • Open governance process as a means to encourage contributions | |
| • Distributed ownership and decision-making | |
| • Cloning oneself through delegation of responsibilities | |
| • Transparency and making processes reusable across multiple tasks | |
| • Risk management and quantifying potential mistakes | |
| • Earning trust and relinquishing control in project leadership | |
| • Institutionalizing governance through frameworks (e.g. Apache Software Foundation) | |
| • LTS and new release lines for a project | |
| • Importance of having a large contributor base to handle various tasks and responsibilities | |
| • Need for open-source projects to optimize for contributors' goals and interests rather than setting rigid project goals | |
| • Metrics for measuring success in an open-source community, such as user happiness and feeling safe to contribute | |
| • Critique of the BDFL (Benevolent Dictator For Life) model and its limitations in modern open-source communities |