add all 2016 summaries

BONUS – Behind the Scenes of Season 1 and 2_summary.txt

@@ -0,0 +1,42 @@
+• Behind-the-scenes look at Request for Commits podcast
+• Origin story of the show, started as a result of Nadia Eghbal's interview on The Changelog
+• Different perspectives and approaches between hosts Mikeal Rogers and Nadia Eghbal
+• Importance of thorough notes prepared by Nadia before each episode
+• Design of the show, including its structured format and focus on sustainability
+• Hosts' approach to interviews, which often dive into deeper topics beyond just technical accomplishments
+• Interview style and approach
+• Credibility and background discussion in interviews
+• Show longevity and relevance of discussions
+• Favorite moments from the season
+• Karl Fogel's book "Producing Open Source Software" and its impact on open source sustainability
+• Upcoming topics for future episodes, including potential discussions with Karl Fogel about his new book
+• Discussion of grant funding and its role in sustaining open-source projects
+• Nadia Eghbal's reflections on her previous episode about venture capital (VC) and open-source funding, stating that she has changed her perspective and now believes VC may not be the best solution
+• In-depth conversation with Heather about licenses and their role in sustainable open-source practices
+• The idea of license proliferation and its costs on both sides (developers and lawyers)
+• Sustainability as a key aspect of developer mindset, comparable to testing
+• Reflections on season one of the podcast and the goals achieved
+• The importance of valuing testing and sustainable practices in project management
+• Companies' dependency on open source and the need for a relationship based on business value rather than charity
+• Community involvement and contribution to open source, with all engineers contributing to open source for part of their time
+• Sustainability as a critical aspect of working in open source, going beyond just getting paid for work
+• The target audience for the show: community leaders within open source who have responsibility to a project or people and are craving depth of conversation on sustainability
+• Why Mikeal Rogers and Nadia Eghbal co-host the show together, with a shared passion for exploring topics related to sustainability in open source.
+• Plans for season two
+• Reaction to season one (positive feedback from the community)
+• Importance of quality content (music, editing, sound quality)
+• Nadia and Mikeal's experience with producing podcasts and working with hosts
+• Origins of Request for Commits podcast (initial idea by Nadia and Mikeal)
+• Discussion on the plan for season two of Request for Commits
+• Seasonal vs weekly podcasting approach and its benefits
+• Focusing on quality over quantity and taking time to research and prepare episodes
+• Importance of setting expectations with listeners and maintaining relevance in the community
+• Exploring a different perspective on podcasting, where it's not just about producing new content but also about creating timeless episodes that can be revisited later
+• Feedback from listeners on season one and suggestions for future seasons
+• Ideas for season two, including featuring unsung heroes and doing research to find new guests
+• The importance of diversity in stories and perspectives for the show's growth and avoiding stagnation
+• Identifying unsung heroes in open source projects who may not receive attention or recognition
+• The role of events and in-person interactions in thriving open source communities
+• How to submit suggestions for guests on season two, including using Twitter and being respectful of the selection process
+• A behind-the-scenes look at the planning and production of the show
+• Upcoming plans for season two, including recording in quarter one 2017

Building Communities_summary.txt

@@ -0,0 +1,41 @@
+• 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

Documentation and the Value of Non-Code Contributions_summary.txt

@@ -0,0 +1,46 @@
+• Eric Holscher's experience with Python and Django, including how he learned about the importance of documentation
+• The origins of Read the Docs and its growth from 100k views in the first month to much more
+• How Sphinx enabled easy integration with Read the Docs for hosting and building documentation
+• The role of a well-designed interface and aesthetics in driving adoption of Read the Docs
+• Django's emphasis on documentation and how it influenced Eric Holscher's values and approach to project management
+• Eric Holscher's background and how he ended up working at the Journal-World newspaper
+• The inspiration for Read the Docs and its focus on open access
+• The beginnings of Write the Docs conference and its rapid growth
+• The changing cultural perception of documentation in the software industry
+• Efforts to raise awareness and improve documentation practices
+• The importance of documentation in software development is growing, with many developers valuing it as much as testing.
+• Documentation is essential for new projects to be adopted by others, especially open-source ones.
+• A well-documented project can lead to increased adoption and usage.
+• Writing documentation is a fundamental part of being a good software developer, requiring effective communication skills.
+• Documentation can help prevent rework and improve code quality by thinking through the public API before implementation.
+• Documentation needs vary based on type of project and community
+• Different projects require different levels of documentation complexity
+• Markdown is suitable for small projects, but more powerful languages like AsciiDoc or reStructuredText are needed for large API references and complex codebases
+• Documentation should be tailored to specific audiences (e.g. developers vs users)
+• Automation can help with certain aspects of documentation, but some level of human curation is still necessary
+• Different programming methodologies (e.g. Django, Node.js) require unique documentation approaches
+• The challenge of creating documentation is like navigating a sales funnel, where each step increases complexity
+• Standardizing tools and processes can reduce distractions and allow people to focus on writing
+• Embedded documentation in code, such as auto-generated Javadoc-style listings, has its limitations
+• Sphinx is mentioned as a tool that allows for contextualized and up-to-date documentation by intermingling prose content with auto-generated content
+• Write the Docs aims to establish documentation as a core skill that can be developed and valued separately from coding expertise
+• There is tension between professionalizing documentation and encouraging beginners to contribute through documentation
+• Valuing documentation requires recognizing it as an important part of the project, rather than just a "non-code contribution"
+• Signaling the importance of documentation includes requiring documentation alongside code contributions, making it a core part of the development process
+• The importance of documentation as a product in open source projects
+• Incentivizing non-code contributions and increasing diversity in project teams
+• Attracting and retaining contributors through documentation and community building
+• Increasing the value of non-technical contributions to open source projects
+• Sharing knowledge and best practices across communities and conferences
+• Addressing structural issues in software development, such as lack of diversity and exclusionary practices
+• Community building through experimental areas
+• Monetization strategies for open source projects
+• Challenges of incentivizing contributions beyond coding, such as project management
+• Sustainability models for open source services
+• Failures of previous monetization models, including the Red Hat model
+• Empathy and compensation for maintainers of free code
+• Struggles with making a market rate salary while maintaining an open source service
+• Potential contributors to a product are not contributing due to perceived sufficiency of its functionality
+• The company is exploring advertising as a revenue model, focusing on non-intrusive methods
+• They are creating a "newspaper-style" ad experience, hosting ads and not tracking user data
+• Rolling out advertising was stressful due to concerns about alienating users

Finding New Contributors_summary.txt

@@ -0,0 +1,44 @@
+• Charlotte Spencer's first pull request was a spelling correction on a Node.js Express tutorial
+• Contributing to open source is not just about coding skills but also requires social skills and communication with others
+• Hoodie project does a good job of onboarding new contributors, providing them with issues, mentorship, and inviting them to Slack channels
+• Once contributors have made their first pull request, they may feel overwhelmed by what to do next and may not know how to continue contributing
+• Charlotte Spencer's journey from her first contribution to becoming a member of the Hoodie core team was accidental and happened through contributions to various parts of the website over several months
+• The importance of community support in open source projects
+• Bringing diverse skills and perspectives to Hoodie, an open-source project
+• Contributing to accessibility features on the Hoodie website and demo products
+• Removing ableist language and promoting inclusive communication
+• Fostering a positive attitude and culture within open source communities
+• Creating the Twitter account "Your First PR" to help beginners with their first pull request
+• Highlighting issues that are approachable for new contributors
+• The importance of having a "first-timers only" guide in open source projects
+• Challenges faced by maintainers when reviewing PRs from new contributors
+• The need for maintainers to be understanding and patient with first-time contributors
+• The anxiety and nervousness experienced by new contributors
+• The analogy between contributing to open source and going on a date, highlighting the awkwardness and uncertainty of the experience
+• Delayed review of a pull request and apology from the maintainer
+• Importance of open channels of communication in projects
+• Non-code contributions, such as moderation, community building, and content creation, are undervalued and important to project success
+• Examples of non-code contributions include logo design, blog posts, and community engagement
+• Challenges for small projects with limited resources and visibility, including attracting contributors and maintaining a welcoming atmosphere
+• The importance of setting clear expectations for your project through a well-written README
+• Having a code of conduct to outline intentions and set boundaries
+• Documenting everything, including processes and time commitments
+• Creating beginner-friendly issues that provide enough information for contributors to succeed
+• Building a support system to help new contributors and improve the community over time
+• Retaining first-time contributors in open-source projects
+• Importance of transparency and communication in open-source communities
+• Value of junior members contributing to a team and questioning established processes
+• Difficulty in balancing transparency with the need for summary or overview in large-scale projects
+• Need for adaptability and willingness to change processes as a project grows and scales
+• Importance of admitting when mistakes are made and being open to feedback and improvement
+• Best practices for contribution-type events to balance new contributors with maintainers' expectations
+• Importance of communication between event organizers and project maintainers before running an event
+• Providing hands-on support for beginners at in-person events
+• Setting clear intentions for the type of event (beginner-focused or casual) and communicating that clearly to participants
+• Admin tasks, such as setting up environments, troubleshooting, and disaster planning
+• Strategies to prevent gaming the system by event organizers, including reviewing pull requests and setting expectations for contributors
+• The importance of community over competition in open source projects
+• Managing spammy pull requests and maintaining project value
+• Navigating contributor flux and adapting to changing circumstances
+• Mitigating the risk of burnout and promoting self-care among contributors
+• Strategies for maintaining a sustainable and diverse contributor base

Funding the Web_summary.txt

@@ -0,0 +1,58 @@
+• Founding of Brave and its open-source basis
+• History of Netscape and its impact on the browser landscape
+• Creation of JavaScript and its standardization
+• Rise and fall of Netscape, including Microsoft's entry into the market
+• Founding of Mozilla as an escape pod from Netscape's struggles
+• Development of Firefox from Mozilla code
+• Early browser wars and emerging monetization models
+• Implementing tabbed browsing in Phoenix and Chimera
+• Mozilla's Roadmap update in 2003 by Hyatt and the speaker
+• Benefits of open source development: zero cost to users, multiple engines developed in the open (Chromium/Blink, WebKit, Mozilla)
+• History of browser development: Netscape, Microsoft IE, Apple Safari, Google Chrome
+• Business models for browsers: advertising revenue from search deals, neglecting browser development as secondary business focus
+• WebKit's origins as a fork of KHTML and its struggles with HTML compatibility
+• Dave Hyatt's recruitment by Google and Apple's limited investment in WebKit
+• The Techtopus case, an alleged Sherman Clayton antitrust violation involving Google, Apple, Adobe, and Intel colluding to suppress salaries and limit talent poaching
+• Brendan Eich's dinner conversation with Sergey Brin, Larry Page, and Mitchell Baker about Steve Jobs' request to not hire Dave Hyatt
+• Maciej Stachowiak and Darin Adler's role in WebKit and their decision to make it an open-source project
+• The impact of large companies' interests on the development of web technologies
+• Google's use of WebKit for Chrome and its financial relationship with Mozilla through search revenue
+• Google vs Bing and the importance of a default search engine
+• Microsoft's struggle with browser market share and competition from Chrome and Safari
+• The economics of browsers and the cost of maintaining a browser business
+• Brave's sustainability model and revenue streams (search partnerships, microdonations, and ecommerce)
+• The challenges of competing with Google and other established players in the browser market
+• Brave's vision for frictionless small payments
+• Concerns about Google and Facebook's dominance in advertising and data collection
+• The need for browser vendors to prioritize user privacy and security
+• The role of ad exchanges and fake ad agencies in spreading malware through targeted ads
+• Brave's approach to handling user data and potential business models
+• Malvertising and malware on reputable websites, including The New York Times and BBC
+• Programmatic advertising and ad exchanges allowing malicious ads to be displayed
+• Risk of ransomware and other types of malware through malvertising
+• Publishers tolerating low-quality ad space due to financial pressure
+• The rise of ad blocking and its impact on the advertising industry
+• Brave's goals of creating a better advertising model that benefits users and provides them with revenue control
+• Concerns about user understanding of Brave's unique approach to advertising
+• Legacies with JavaScript and its use for third-party ads
+• Importance of user privacy and safety in web browsing
+• Brave's approach to advertising, focusing on user opt-in and publisher opt-in
+• The concept of "Wanamaker's dilemma" and the need for targeted marketing
+• Brave's vision for a private, secure system where users own their data
+• Potential for personal ad businesses and local computation
+• Sustainability issues in developing and using browsers, including funding models
+• Comparison to open source development and funding challenges
+• The role of platform code as a cost center and the need for shared costs
+• The traditional model of newspaper revenue was based on advertising, but with the rise of digital platforms, this is no longer sustainable
+• Facebook and Google take 80% of the $70 billion spent on ads in the US, leaving little for publishers
+• Many ads are not viewed or are fraudulent, highlighting a need for more efficient and private ad platforms
+• Brave's proposed solution uses Bitcoin and micro-payments to fund the web while respecting user privacy
+• The future of online revenue may involve frictionless payments, permissionless transactions, and automated micro-royalties for creators
+• Open-source approach for ad-blocking browser
+• Need for secure and trustworthy data handling
+• Proprietary ads compromised by third-party intermediaries
+• 50/50 revenue share between Brave and users
+• Private matching of device identifiers for advertising
+• Zero-knowledge proof protocol for verifying ad impressions
+• Importance of transparency and auditability in open-source code
+• Lock-in from user trust and brand value

Grant Funding What Happens When You Pay for Open Source Work_summary.txt

@@ -0,0 +1,53 @@
+• Max Ogden's background and experience with open source and data distribution
+• How Max discovered grant funding for Dat and found his first funders
+• The mechanics of working with grant funders and building relationships
+• Code for America and how it helped Max think about different applications of code
+• The transition from being an outsider pushing technical solutions to working with governments as a change agent
+• Code for America's model for government innovation and civic tech
+• The importance of open source in government procurement and development
+• Max Ogden's experience as a Code for America fellow in Boston, working on open-source projects and advocating for better software and hiring practices
+• The challenges of implementing open source solutions in government, including contracting and support issues
+• The origins of the Dat project, initially focused on government data sharing but later expanding to scientific data
+• A fortuitous meeting at the Mozilla festival that led to a grant from a foundation to work on Dat's development
+• The Knight Prototype Fund offers smaller grants ($30,000) for 6 months to test ideas and develop prototypes
+• Grant writing can be intimidating due to large amounts of money or multi-year commitments, but there are alternative funding options available
+• Grants come from different sources (government, philanthropic private foundations, EU)
+• Building relationships with funders is crucial for grant success
+• The grant process involves finding the right foundation and funder, establishing a relationship, and writing grants to pursue specific missions
+• Grant writing is not about the technical details of the project, but rather about communicating the mission and vision to the funder.
+• Building relationships with investors is key, similar to venture capital
+• Meeting potential funders at events can lead to successful partnerships
+• Grants from organizations like the Knight Foundation and Sloan Foundation have supported Max Ogden's project, Dat
+• Max's project has received significant funding increases over time, from $50,000 to $3 million
+• The Sloan Foundation's grant requirements led to a shift in project direction to prioritize scientific use cases, specifically addressing issues with data sharing in scientific research
+• The speaker's grant allowed them to partner with scientific labs to develop software that improves data-sharing workflows.
+• The challenges of working with scientists include dealing with large datasets and non-standard file formats.
+• Incentives for open-source development are often lacking in science and government institutions.
+• Grants can provide a solution by paying developers to work on challenging problems.
+• The speaker's team was able to attract top talent, including Mathias Buus, by offering the opportunity to work on impactful projects.
+• Community involvement and events can help developers meet potential coworkers and funders.
+• Interdisciplinary approaches and understanding of affected communities are crucial for developing effective solutions.
+• Giving team members autonomy and freedom is key to attracting world-class talent.
+• The grant-funded project aims to explore the future of scientific data sharing.
+• Paying developers to work on open-source projects can create mismatched incentives
+• Autonomy is key, allowing developers to work on their own projects and prioritize tasks
+• Conference-driven development can be effective in keeping teams focused and motivated
+• Decentralized and asynchronous planning helps with project coordination and decision-making
+• Travel budgets for convening team members can be an effective way to boost productivity and collaboration
+• Funder relationships can facilitate travel expenses and other convenings
+• The team's unique blend of non-profit, academic, and software-focused aspects creates a distinct model
+• Grants as funding mechanism for open source projects
+• Importance of linking social mission with project goals
+• Role of grants in supporting public goods and infrastructure
+• Distinction between technology-focused foundations and socially-missioned organizations
+• Gaps in knowledge between grant makers and open source communities, particularly around timelines and agility
+• Need for trust-based relationships between funders and open source projects
+• Grants are a complex process with constraints on budgeting and planning
+• Open source projects can be more competitive if tied to social causes and impact
+• Procurement reform in government could make grants more accessible to open source
+• Organizations like US Digital Service and 18F are working to promote open source within government
+• Alternative funding models, such as the Substance Consortium, may emerge for supporting open source projects
+• Substance is a project with an open governance structure and multiple stakeholders who contribute financially but not exclusively as employees.
+• Collaborative Knowledge Foundation facilitates the project and supports its goals of improving scientific publishing and access to research.
+• The Substance Consortium model allows for cooperation without control among member organizations.
+• There are efforts to replicate this model for other projects, such as Dat, with a similar consortium structure.

Grant Funding： What Happens When You Pay for Open Source Work？_summary.txt

@@ -0,0 +1,91 @@
+• Max Ogden is the creator of DAT, a decentralized tool for distributing datasets.
+• He has worked in the Node.js ecosystem and was involved in starting Node School and publishing modules on NPM.
+• Max was one of the first Code for America fellows and received an award at Auscon that led to him being recruited by Code for America.
+• Before joining Code for America, Max worked at a company doing qualitative market research but felt unfulfilled.
+• He credits his team with providing support and mentorship, which allowed him to learn and grow as a programmer.
+• Max notes that the Portland tech culture is unique in valuing personal and family time over work.
+• The transition from working on the X API to Code for America was a significant change in approach, from just providing data to developers to collaborating with government officials.
+• The human side of code was learned through this process, including understanding and respecting government culture.
+• The importance of embedding people within government to inspire change and introduce new ideas.
+• The negotiation workshop at Code for America taught the speaker about effective communication and respect for others' points of view.
+• The model of Code for America was influential in changing the speaker's approach from focusing on technical solutions to addressing social and incentives problems.
+• The program allowed people from the tech industry to work in government for a year, giving them a new perspective and authority to make changes.
+• The speaker's year-long fellowship in Boston involved implementing open source software and creating a new procurement policy for city support.
+• The project led to significant cultural changes within the city hall, including a shift towards modern and progressive approaches.
+• One of the biggest outcomes was establishing a way for the city to contract with open source vendors for support.
+• The speaker later worked on a different project involving public school data and realized the need for better dataset management.
+• They started exploring the idea of creating a version control tool for datasets, which eventually became the debt project.
+• The project transitioned from focusing on government data to scientific data and scientists, after a fortuitous meeting at the Mozilla festival.
+• Discussion of dataset sharing and syncing data for scientific users
+• Meeting at the Mozilla festival in 2013 leading to grant funding opportunity
+• Grant funding process and smaller funding options through organizations like Knight Foundation
+• Overview of the Knight Prototype Funds program and its benefits
+• Explanation of grant writing and the process of securing funding
+• Charitable trusts and foundations set up by eccentric billionaires to evade taxes
+• Philanthropic private foundations in the US, often run by white male billionaires
+• Comparison with European government grants, which are more prevalent due to high taxes
+• Differences between US and EU grant programs, including size and complexity of grants
+• Importance of building relationships with funders for successful grant writing
+• Grant writing as a process that requires time and effort to develop relationships with funders
+• Contrast between grant funding and venture capital (VC) funding
+• Benefits of grant funding, including no pressure to make compromises or judgment calls.
+• Importance of meeting funders face-to-face through community events
+• Value of attending conferences focused on specific issues rather than just technical topics
+• Key to grant funding is looking at projects holistically, not just technically
+• Building relationships with investors/funders is crucial for success
+• Intersectionality and seeking inspiration from different sectors can be creatively stimulating and lead to new connections
+• The speaker was approached by Josh Greenberg from the Sloan Foundation to work on scientific projects
+• The speaker has a history of unpaid open source work and taking pay cuts for non-profit work
+• The speaker's current salary is above average for nonprofits, but below what they could earn at a startup
+• The Sloan grant has enabled the speaker to build a team and focus on scientific reproducibility
+• Scientific reproducibility issues arise when researchers publish papers without sharing underlying data and code
+• The Sloan Foundation's mission includes supporting science and technology in the modern world
+• The first grant established a team and required a commitment to working with scientists
+• The speaker had to figure out what solutions to build by getting embedded into the problem.
+• Grants to develop software for data sharing workflows in scientific labs
+• Partnership with four in-depth labs from different fields (astrophysics, DNA research, social sciences)
+• Overcoming challenges of data size and file formats specific to each field
+• Importance of grants as a way to create incentives for developing open-source software in science
+• Hiring talented developers, including Matthias Spuse, to work on the project despite limited budget
+• Approaches to attracting top talent, such as DMing them on Twitter
+• Importance of attending open source conferences to meet funders and community members
+• Interdisciplinary approach to software development and considering the communities affected by it
+• Focusing on key areas such as science, journalism, and government for funding opportunities
+• Working in a non-traditional startup environment with world-class team members given high degree of freedom
+• Emphasis on open-source work and direct impact on community
+• Incentivizing team members to explore future of scientific data sharing through grant money
+• Discussing paying people to work on open source projects
+• The challenges of changing incentive structures and staying on mission for an organization
+• Conference-driven development as a strategy
+• Importance of team members having personal deadlines and goals
+• The value of remote teams and convening in person
+• The need for team members to have ownership and credit for their work
+• Personal evangelism and speaking on behalf of the community
+• The speaker discusses traveling to collaborate on projects with a colleague from another city
+• They describe their process for planning and working on open-source projects, including a two-phase approach with an intensive project planning phase followed by parallel work
+• The speaker mentions the benefits of decentralized and asynchronous collaboration, including cost savings
+• Grant funding is discussed as a way to support travel and convening events, which can be beneficial but also require pitching and reporting
+• The speaker's team is trying to establish itself as a unique entity that blends open-source principles with nonprofit status and paid staff, and they're seeking a clear label for themselves
+• The conversation turns to the role of grants in funding open-source work, including Stripe's open-source program and private philanthropies like the Gates Foundation
+• The importance of using technology as a tool to achieve social impact
+• Distinguishing between grants that improve technologies and those that aim to improve social outcomes
+• Exploring the concept of public software and open source software as a public good
+• Drawing a distinction between nonprofits and for-profits, with nonprofits often focused on specific social missions
+• The role of grant funding in supporting technology development and its trade-offs in terms of detachment from social issues
+• Challenges of traditional grant writing process
+• Difficulty of predicting project outcomes and timelines
+• Importance of flexibility and agility in funding projects
+• Misconceptions about open source funding and its potential benefits
+• Cultural differences between grant-making organizations and open-source communities
+• Need for grants to prioritize social impact and problem-solving over technical details
+• Technical debt and inflexibility in software development
+• Open source as an advantage for social causes
+• Challenges of pitching open source projects to grant writers
+• Institutional level support for open source work in government
+• Procurement reform in government and its potential impact on open source funding
+• New organizations within the federal government promoting open source initiatives
+• Grant landscape shifting towards supporting efficient government services and competing with traditional vendors
+• The Substance Consortium model for open-source collaboration and project support
+• eLife, a scientific journal, and the development of eLife Lens, an open-source editing tool
+• Collaborative Knowledge Foundation's role in facilitating the Substance Consortium and promoting open-access publishing tools
+• The DAT project's potential to adopt a similar consortium-based model for distributed file system infrastructure support

Liberal Contribution and Governance Models_summary.txt

@@ -0,0 +1,47 @@
+• Open source transition from older tools to GitHub and Git
+• Rod Vagg's personal experience with open source, including his low-level technical background and lack of initial involvement in online communities
+• The role of confidence and community in contributing to open source projects
+• Liberal contribution policies and their underlying mechanics
+• Transitioning into a liberal contribution mindset and the potential future of project governance
+• The speaker created the LevelUP project to explore Node add-on area (C++ add-ons)
+• He opened up the project early for feedback and collaboration
+• Max Ogden provided valuable suggestions that helped shape the project's direction
+• The project adopted an "open open source" approach, where contributors have equal ownership and a seat at the table
+• This approach evolved into a set of principles and rules for contribution
+• Some of these rules, such as no false pushes and non-master branches, are considered soft or outdated
+• The emphasis has shifted towards general openness and flexibility in contribution mechanics
+• Mechanisms for collaboration and decision-making in open source projects
+• Liberal contribution policies and how they differ from traditional approaches
+• The use of pull requests as invitations for discussion and implicit approval
+• Onboarding process for new contributors and the importance of getting through the initial gate
+• Consensus-seeking vs. consensus and the role of strong technical opinions
+• Importance of allowing people to say no and participate in discussions
+• Goal of making open source projects more like a Wiki, with contributions being valued regardless of size
+• Release process vs contribution mechanics
+• Differentiating between casual and regular contributors
+• Importance of culture in open source projects
+• Tension between established core group and newcomers
+• Arguments against liberal contribution policies
+• The role of responsibility and inclusion in fostering contributions
+• Long-term evolution and relevance of open source projects
+• Fear of openness and the masses
+• Wisdom of crowds vs chaos
+• Maintainer bottleneck: accepting contributions to alleviate administrative burden
+• Fears of scope creep and outside contributors changing project vision
+• Tension between personal interest and shared interests in open source projects
+• Benefits of liberal contribution policies, including increased ownership and maintenance help from community members
+• Fear of scope creep and the importance of maintaining project culture
+• Liberal contribution model's suitability for evolutionary changes rather than revolutionary ones
+• BDFL (Benevolent Dictator For Life) model's drawbacks, including detachment from users and potential for project stagnation
+• The value of open contribution and user engagement in a project's development
+• Different phases of project development, with varying approaches to openness and contribution
+• Differentiating between BDFL (Benevolent Dictator For Life) model and leadership by respect
+• Importance of leadership in open-source projects, especially early on
+• Emergence of leaders through contributions and expertise, rather than entitlement or authority
+• Distinction between entitlement and respect in open-source governance
+• Meritocracy as a system that can lead to complacency and stagnation if not continually evaluated and respected
+• Need for effective onboarding and off-boarding processes in open-source projects
+• Difficulty in offboarding contributors from projects they've internalized
+• Challenges of welcoming diverse contributions in discussion-heavy cultures
+• Time commitment aspect: valuing input from those who can assert themselves continually vs. casual or infrequent contributors
+• Recognizing and incorporating valuable input from outsiders who don't have the time to engage fully

Measuring Success in Open Source_summary.txt

@@ -0,0 +1,48 @@
+• Discussing open source metrics and interpreting data around dependencies and usage
+• Limitations of current open source ecosystem measurements
+• Individual project metrics and measuring success
+• Relevance of GitHub stars in determining a project's actual usage
+• Using package management data to connect the dots between projects and understand actual usage
+• BigQuery and analyzing file content for more detailed insights into how projects are used
+• The importance of being able to measure how much people are using open-source software
+• Challenges in collecting usage data for certain languages and package managers, such as C and npm
+• The release of BigQuery dataset that makes it possible to query and analyze open-source software usage
+• The potential applications of the dataset for researchers, policy makers, and maintainers of open-source projects
+• Concerns around user privacy and the need for responsible data sharing
+• Examples of how the dataset can be used to answer common support questions and provide insights into software usage.
+• Discussion on the limitations of GitHub data and metrics
+• Exposure of download data and other consumption metrics on GitHub
+• Potential risks of exposing referrer data and user privacy concerns
+• Importance of qualifying metrics, such as differentiating between popularity and quality
+• Challenges in comparing metrics across different package managers and ecosystems
+• Comparison between Go package manager and npm/PIP
+• Standardization of package managers across languages
+• Limitations of module systems in supporting small packages
+• Impact of Node's resolution semantics on package management
+• Evolution and changes in module systems over time
+• Challenges of building a new package manager without learning from previous ones
+• Balancing trendy vs established projects in software development
+• Importance of project health over popularity when choosing tools or libraries
+• Difficulty in finding reliable information on project stability and maintenance
+• Long-term implications of bit-rot on software and need for forward-thinking
+• Challenges in handing off open source projects to new maintainers
+• Shift towards peer production model in open source, where users filter and choose what works best for them
+• Metrics of success and health in open source projects
+• Defining project health through human observation vs. codified metrics
+• Importance of community contribution and participation in open source projects
+• Distinction between project activity and collaborativeness/participativeness
+• Use of data from package managers, issue trackers, and contributor activity to assess project health
+• Need for business users of open source to have a clear understanding of project maintenance and risk
+• Potential solutions from organizations like the Linux Foundation's Core Infrastructure Initiative
+• Metrics for project health
+• Badging program for secure projects
+• Importance of measuring usage data in open-source libraries
+• Role and contribution of maintainers and contributors
+• Automated tools for identifying active contributors and suggesting them for commit rights
+• Gamification techniques to encourage contributions (e.g. leaderboards)
+• Discussing recognition and rewards for various types of contributions to open-source projects
+• The evolution of contributor roles as projects grow, shifting from code commits to user support
+• Trends in open-source data, including increasing package numbers and growth areas
+• Challenges in filtering and measuring health of open-source projects due to information overload
+• Potential solutions, such as Homebrew's added metrics and the Software Heritage project
+• Future expectations for product changes and improvements to address common issues

Open Source and Business_summary.txt

@@ -0,0 +1,43 @@
+• Building businesses from open-source projects
+• Turning side projects into full-time work
+• Experimenting with steady revenue sources
+• Raising venture capital
+• Open-source vs. commercial strategies for business growth
+• Challenges of maintaining open-source products as a business grows
+• Balancing community involvement and commercial goals
+• The relationship between companies (Disqus/Sentry, Joyent/npm) and open-source projects they developed.
+• David's experience developing Sentry while at Disqus and his views on the benefits of open-source.
+• Isaac's experience working with Sentry at Joyent, including its infrastructure service and use by small/large businesses.
+• David's departure from Joyent and npm, including tension around recruiting tool status and concerns about Joyent's ability to support npm.
+• Alternative options for npm (foundation, VC funding) and their perceived drawbacks.
+• The Node Foundation and its relation to Joyent, Sentry, and other companies.
+• JavaScript community's openness to business models
+• npm and Sentry's revenue streams (SaaS, enterprise products)
+• Importance of transparency when working with open-source communities
+• Comparison of business models between Sentry, npm, and other companies like GitHub, WordPress, and GitLab
+• Evolution of pricing models in open-source communities
+• Copying and pasting someone else's business model as a starting point
+• Importance of getting to market quickly with an imperfect pricing model
+• Value of being bootstrapped or having early sponsorship for cash flow positivity
+• Shift in open source business models from old school enterprise companies to SaaS
+• Focus on communities and services rather than just open source software
+• Leveraging internet-connected tools and services to build open source businesses
+• The term "open source business" is not well-defined and its meaning varies among companies.
+• Companies use open source as a way to attract developers, build platforms, and recruit talent.
+• The market for open source businesses has shifted from top-down decision-making to bottom-up, where developers drive decisions.
+• Open sourcing projects can be beneficial for companies like npm and Sentry, which focus on the developer market.
+• Proprietary software still plays a significant role in many industries, but open source is becoming increasingly prevalent.
+• Companies are using open source as a way to build businesses around existing products, rather than building proprietary solutions.
+• Isaac Schlueter's approach to open sourcing Sentry has been successful due to his ability to drive the project's direction.
+• npm and Sentry have different approaches to open source, with npm focusing on community contributions and Sentry focusing on external contributors for specific issues.
+• The challenges of maintaining a community-driven codebase and balancing governance approaches as it grows
+• The importance of having a clear governance structure and rules for decision-making to prevent anarchy and maintain community health
+• The role of npm in the community, including its responsibilities and efforts to ensure transparency and avoid abuse of power
+• The relationship between companies and communities, with discussions on whether companies can truly be part of a community or if they are always external patrons
+• Examples from npm and Sentry on how their employees interact within projects, representing themselves as individuals rather than solely as the company
+• The value of hiring team members who are already familiar with and invested in the project, and the benefits of this approach for building a unified voice and product direction.
+• Investors trust open source companies to know what they're doing
+• Open source plays to investors' strengths in developer-lead enterprise products with network effects
+• Community management is not the primary concern of investors, but rather monetization of user engagement
+• Building businesses around open source projects requires adapting to unique challenges and opportunities
+• Conveying the value of open source to users can be a challenge for companies like Sentry

Open Source, Then and Now (Part 1)_summary.txt

@@ -0,0 +1,56 @@
+• Changes in open source since Karl Fogel's book was first published 10 years ago
+• Influence of Git and GitHub on development workflows and culture
+• Shift in perception of open source and whether it has "won"
+• Challenges remaining in the open source community
+• History of Producing Open Source Software, including its creation and reception
+• Karl Fogel's experience writing the book and his role as a partner at Open Tech Strategies
+• Evolution of roles within open source projects, such as community management
+• Intersection of technical and social skills in successful open source project leadership
+• The idea that open source projects are meritocracies with no structure or social hierarchy
+• The need for community management and people skills in open source projects
+• Addressing the "tyranny of structurelessness" and the dominance of certain personalities
+• The importance of compromise, communication, and managing competing interests in open source projects
+• Recognizing that programmers often lack soft skills and need guidance on community building and social dynamics
+• Discussing challenges such as creating a welcoming atmosphere, addressing toxicity, and finding incentives for healthy project development
+• Reflecting on whether any progress has been made in the past 10 years and what still needs to be addressed
+• Changes in open source projects from individual developers to corporations
+• Shift from Subversion to Git as a version control system and GitHub's rise as a platform
+• Need for updates to address new trends in open source development
+• Importance of acknowledging the shift to business-to-business open source projects
+• Governments' slow adoption of open source and need for education on its benefits
+• How GitHub has changed the landscape of open source, making it easier to contribute and manage projects
+• Shared namespace and unification of identity
+• Extension of Git language and tools for collaboration
+• Standardized contribution experience through pull requests
+• Friendliness and visual interface of GitHub
+• Ease of contribution and collaboration for new publishers
+• Empowerment of open source maintainers through streamlined process
+• Critique of previous tools (Trac, JIRA) as being more complex
+• GitHub's open source code can be used for bug tracking, but feature requests are often declined due to prioritizing simplicity for most users.
+• The term "open source" was coined in 1997 as a way to resolve terminology confusion and avoid ideological debates around free software.
+• The distinction between "free software" and "open source" is seen by some as a post-facto creation, with the two terms being used interchangeably.
+• Companies like GitLab can benefit from GitHub's publicly available decisions and innovations, allowing them to experiment with new approaches without alienating their own customers.
+• Open source has not "won" in the sense that proprietary software still dominates the market surface, but its volume is increasing as more users interact with open-source systems behind the scenes.
+• The distinction between infrastructure software and consumer-facing software
+• Open source's success on the infrastructure side but not necessarily on the principle of freedom
+• The importance of control over personal life and devices running proprietary software
+• Hacker/maker movements addressing vulnerabilities through modifications and customizations
+• Separation between production and consumption of software, with open source winning in production but not necessarily in consumption
+• Utilitarian arguments for open source, including privacy and security
+• The influence of writing useful code on the success of the free software movement
+• The importance of system porosity and allowing users to contribute to its development
+• The changing definition of software developers and the growing accessibility of coding
+• The impact of network effects on proprietary platforms and their tendency to control user behavior
+• The potential for future generations to demand more freedom and openness from digital systems
+• The cooptation of the term "open source" and its various meanings among different groups and individuals
+• Misuse of "open source" terminology and its implications
+• Definition of open source and its relationship to license and freedoms
+• Network effects and their impact on collaboration and community
+• Forking and its role in promoting open source dynamics
+• Trade-offs between user convenience and contributor autonomy
+• Role of user base size and motivation in facilitating forked projects
+• The tension between Google's control over the Android code base and manufacturers' need to fork it
+• Users of Android are often not the same as users of the Android code base (manufacturers)
+• Forking can lead to a disconnect between user needs and manufacturer needs, putting Google in a difficult position
+• Software becoming increasingly tied to hardware devices makes hacking and development more difficult for users
+• A dystopian future where few users have the resources or expertise to contribute to software development is possible

Open Source, Then and Now (Part 2)_summary.txt

@@ -0,0 +1,47 @@
+• Shifts in open source communities and governance due to rising activity and casual contributors
+• Standardization of processes across projects, driven by increased scale and diversity
+• Comparison between BDFL (Benevolent Dictator For Life) models and democratic governance in large open source projects
+• Sustainability of projects with single decision-makers and lack of growth in contributor capacity
+• Importance of documentation and usability for attracting and retaining casual contributors
+• Counterexamples to the idea that open source projects on GitHub are overly complex and hard to contribute to
+• Discussion of FreeBSD as an alternative to Linux with a more accessible community
+• The importance of documentation, mentorship, and a culture of contribution in making a project easier to participate in
+• The role of GitHub in increasing contributions by providing a clear funnel for new contributors
+• Examples of projects that have successfully transitioned from proprietary to open source on GitHub
+• The benefits of open sourcing code, including increased contributions and community engagement
+• Changes in the landscape of open source contributions over the past ten years
+• Shift from Contributor License Agreements (CLAs) to Developer Certificate of Origin (DCOs)
+• Decrease in popularity of CLAs, especially those with asymmetrical rights
+• Increased use of DCOs as a simpler and more lightweight alternative
+• Complexity of governance policies in open source projects
+• Need for governance only when there are non-replicable resources at stake (e.g. developer attention)
+• Governance can be seen as a form of persuasion to convince developers to stay with the project
+• Projects often develop formal governance structures after a charismatic founder leaves
+• Governance models are used as a default when there's no clear leader, especially for organizational participants
+• Governance is "soft" in open source projects and not always necessary
+• Different governance models (BDFL vs. meritocracy) may have varying effects on project culture and contribution policies
+• The distinction between governance and contribution policies is important
+• Large projects are often governed by a single leader, while smaller projects may lack clear leadership structures
+• The browser is now the dominant platform for programming, with most companies developing web-based applications using JavaScript.
+• This has created a huge universe of JavaScript libraries and projects that are open to contributions from individual programmers.
+• Companies use open source releases as a strategic move to gain market advantage by releasing high-quality libraries first, which can then be used by competitors.
+• Large-scale multi-company projects, such as TensorFlow, rely heavily on corporate funding and have limited opportunities for individual contributors to make significant changes.
+• The middle ground of the open source ecosystem is thinning out, with fewer apps being developed in languages other than JavaScript.
+• Many existing projects are struggling to sustain themselves due to lack of resources or governance models that no longer work.
+• As the world moves towards more complex and distributed systems, older projects may need to adapt or risk becoming less relevant.
+• The concept of "tragedy of the commons" and its relevance to open source projects
+• How extensibility mechanisms (e.g. plugin systems, add-ons) allow for continued innovation even if the core project is mature and difficult to contribute to
+• The idea that as energy moves out to these satellite projects, the central project may struggle to maintain itself
+• Concerns about the sustainability of core projects when compared to smaller, more agile projects in their ecosystems
+• The possibility of a zero-sum game where developer resources are diverted from maintaining core projects to working on new ones
+• The difficulty of evaluating whether a project is getting sufficient resources and whether its governance policies are adequate
+• Sustainability of open-source projects and ecosystems
+• The issue with treating sustainability as an afterthought rather than addressing problems directly
+• Nonprofit sector funding models and volunteer-based vs paid work
+• Centralized vs decentralized project management and resource allocation
+• Long-term thinking and institutional support for open-source projects
+• Government engagement in open source and its potential to provide stability and long-term planning
+• Government and open source are incompatible due to risk-aversion among officials
+• Government projects have more exposure when using open source, increasing the risk of failure being publicized
+• The culture of government is not conducive to open source development, which values iteration and potential failure
+• A previous example (Solyndra) demonstrated how government investments can be unfairly scrutinized and criticized for failed ventures

Open source and licensing_summary.txt

@@ -0,0 +1,41 @@
+• Heather Meeker's background and how she transitioned from a paralegal to a practicing lawyer
+• The history of open source licensing and its significance
+• Mixing commercial and open source licenses
+• Standardization of open source licenses over time
+• How the open source landscape has changed since 1996, including the shift away from license proliferation and towards standardization
+• Licensing proliferation and standardization in open source
+• Differences between various licenses (Apache 2.0, GPL, MIT, BSD)
+• Value of open source licensing as a benefit for standardization
+• Challenges of staying up-to-date with changing laws and regulations
+• Importance of self-education and networking for open source lawyers
+• Criticism of formal law education's ability to teach practical skills
+• Heather Meeker's book "Open Source For Business" and its purpose
+• The niche topic of open source licensing and its audience
+• The importance of updating technical information in books and resources on open-source licensing
+• Misconceptions about dynamic linking and GPL compliance among developers
+• Distinction between static and dynamic linking, particularly in C or C++ programming languages
+• How high-level scripting languages lack the concept of static vs. dynamic linking
+• Advanced understanding of GPL compliance among Linux kernel developers
+• Shift from technical expertise to community practice in understanding open-source licensing
+• Changes in developer self-education on open-source issues and licensing
+• Conventional wisdom suggests new developers don't care about licensing issues, but Heather Meeker emphasizes the importance of having some license.
+• Heather Meeker recommends using established licenses like BSD, MIT, Apache, or CC0 for open-source code and advises dedicating it to the public domain if no restrictions are desired.
+• Changing licenses can be complex and is often not recommended unless necessary due to major updates.
+• Licenses do not transfer ownership of intellectual property; they grant permissions for use.
+• There is a distinction between copyright ownership and licensing, with authors retaining rights while granting others permission to use their work under certain conditions.
+• The tension exists between cultural expectations and the legal reality surrounding open-source software, including maintenance responsibilities.
+• Distinction between copyleft and permissive licenses
+• Debate around hybrid models combining open source and proprietary elements
+• Fair Source License and Business Source License as examples of hybrid models
+• Discussion on what constitutes open source and license restrictions
+• Dual-license models, such as using AGPL with a commercial license for proprietary use
+• Analysis of the semantics and material differences between different licensing approaches
+• Dual licensing can introduce a "license bug" into the world
+• Transparency is key when implementing dual licensing practices
+• The model has fallen out of favor due to high transaction costs and limited profitability
+• GPL licenses aim to inject sustainability through contributions and modifications
+• Sustainable open source models often involve community projects with multiple stakeholders and funding sources
+• A company running an open source project on its own may not be sustainable, unless selling hardware or services related to the software
+• New emerging areas of interest include open data, open hardware, and intersection of open source with standards licensing
+• The future of technology and innovation
+• Discussion wrap-up and appreciation for the conversation