add all 2017 summaries

Crowdfunding Open Source (Vue.js)_summary.txt

@@ -0,0 +1,35 @@
+• Evan You's background and how he got started with open source
+• The creation and early development of Vue.js, its initial purpose as a lightweight alternative to Angular
+• How the project evolved over time, from being an experiment to a full-fledged framework for building applications
+• The role of crowdfunding and Patreon in supporting Evan's work on Vue
+• The growth and adoption of Vue, including its popularity in China and the importance of community contributions
+• The features and flexibility of Vue, such as its progressive architecture and incrementally adoptable design
+• The benefits of project maintainers being active on social networks to build connections with users
+• The impact of language barriers and cultural differences on open source contributions from non-US/European/Australian developers
+• The challenge of sustaining oneself financially as an open source project maintainer, with a focus on Evan You's experience using Patreon
+• Strategies for balancing work and personal life as a full-time open source developer
+• The Vue.js team has grown from a few contributors when Evan You started the Patreon campaign to around 20-ish people today.
+• The team is loosely organized and operates on a volunteer basis, with no formal structure or assigned tasks.
+• Despite the lack of formal organization, the team effectively triages issues and filters out minor ones for Evan You to focus on critical issues.
+• The Patreon campaign was set up to fund Evan You's time, but there are concerns about quantifying and allocating contributions to individual team members.
+• The project has a growing community with contributors taking on more responsibility and creating new content.
+• There is a discussion around whether the Patreon campaign should be used to directly compensate contributors or if it should remain focused on funding Evan You's work on Vue.js.
+• Some contributors, like Chris, have been approached by publishers for book deals and other opportunities due to their reputation as core team members.
+• Vue is an open-source project without a formal company or foundation backing it
+• Evan You has maintained control and direction over the project despite its size and success
+• The project's funding model relies on Patreon, with contributors supporting his work rather than the project as a whole
+• Babel, another popular open-source project, faces similar challenges in securing dedicated resources and funding
+• There is a perception that companies are increasingly involved in and supportive of open-source projects, but this may not be the case
+• The distinction between corporate and community-funded open source is becoming more blurred
+• Companies often prioritize their own interests over supporting open-source projects, even when they benefit from them
+• Corporate sponsorship and its potential impact on open-source projects
+• Distinguishing between community-driven and company-backed open-source projects
+• The pros and cons of corporate backing for open-source projects
+• The challenges of maintaining a project's stability and legitimacy without corporate support
+• The importance of evaluating a project's maintenance and contribution history over its corporate backing
+• The shift towards companies opening source their projects to establish industry standards, bypassing traditional standardization processes
+• Risks of specifying software requirements before thorough field testing
+• Benefits of open-source projects and feedback loops in software development
+• Measuring growth and adoption of an open-source project (e.g., Vue)
+• Challenges of tracking user engagement and funding for open-source projects
+• Importance of community feedback and metrics in evaluating a project's success

Documentation and Quitting Open Source_summary.txt

@@ -0,0 +1,42 @@
+• Ryan Bigg's background in Ruby on Rails
+• His contributions to Rails documentation, including crowdfunded project for documenting Rails 3
+• Transition into community management role for Spree open source project
+• Experience with burnout and finding a balance between contributing to open source and maintaining one's well-being
+• Ryan Bigg discusses his experience as a community manager for Spree, including the challenges of managing a user-facing application and dealing with fanboyism.
+• The burnout he experienced in that role was partly due to the pressure to continually be "amazing" and maintain high expectations from users.
+• He notes that documentation is often seen as less important than code contributions, but emphasizes its importance for making open source projects more accessible.
+• Ryan Bigg shares his own experience of learning to write documentation and encourages others to do the same, arguing that it's a skill that can be developed with practice.
+• The conversation touches on the theme of code vs. non-code contributions, with Nadia Eghbal pointing out the false dichotomy between developers who only write code and those who only contribute in other ways.
+• Ryan Bigg discusses his own experience of contributing to projects in multiple ways (code, documentation, community management) and emphasizes the value of being able to explain technical concepts clearly.
+• Ryan Bigg discusses the importance of documentation and encourages people to try writing it, even if they don't feel good at it
+• He shares his experience with maintaining small and large open-source projects, including Rails, and notes that responsibility for documentation changes depending on project size
+• He talks about his burnout and decision to quit contributing to open source in 2015, due to feeling overwhelmed by email and community work
+• Ryan describes how he was able to focus on a specific project (Multitenancy with Rails) after quitting open-source contributions
+• He discusses his role as community manager at Spree and notes that it wasn't part of his job to do open-source work, but rather extra tasks that he couldn't fit into his regular workday
+• Difficulty in finding maintainers for open-source projects
+• Burnout and the need for stepping away from project responsibilities
+• Importance of clear communication about needs and boundaries
+• Challenges in handing off projects and finding suitable maintainers
+• Role of community involvement and guidance in open-source development
+• Balancing contribution levels to avoid burnout and maintain mental health
+• Mentoring and guidance for new open source contributors
+• Burnout in open source projects: causes, effects, and perceptions
+• Maintaining a work-life balance in open source contributions
+• Community dynamics and entitlement among open source maintainers
+• Healthy project management practices and transition procedures
+• Recognizing and discussing burnout as a normal part of contributor life cycles
+• Encouraging younger open source maintainers to seek help and pass on projects
+• Burnout among first-generation open source maintainers due to overwork
+• Paying open source developers and its impact on project direction and ethics
+• Balancing personal enjoyment with professional obligations in open source work
+• Long-term maintenance and feature requests as contributors' interests change
+• Ryan Bigg discusses his experience as a celebrity in the Rails community, where he is recognized by some people but not others
+• He shares a personal anecdote about meeting a woman at a meetup who had transitioned from being a real estate agent to a Rails developer after reading one of his books
+• The conversation turns to managing workload and avoiding burnout, with Ryan Bigg suggesting that having a supportive partner or friend can help prevent burnout
+• He advises developers not to feel obligated to work themselves to the point of exhaustion, and to prioritize their own well-being and happiness
+• The group discusses how recognizing when one is getting grumpy and taking steps to eliminate the causes of that grumpiness can be an important part of maintaining a healthy work-life balance
+• Ryan Bigg jokingly suggests that if he were paid to contribute to open source, he might return to contributing more regularly.
+• The importance of having time to contribute to open source projects
+• Companies not valuing contributions to open source projects unless they directly benefit from them
+• Allocating company resources (time and money) to contribute to open source projects as an investment in the company's future
+• The vital role that open source projects play in supporting businesses, with examples of companies using popular open source technologies such as Rails, React, and Webpack.

Maintaining a Popular Project and Managing Burnout_summary.txt

@@ -0,0 +1,26 @@
+• Christopher Hiller became a maintainer of Mocha in 2014 after TJ, the previous maintainer, passed control over to him without guidance.
+• The project had a large number of open bugs and features that needed to be added, but initially, the biggest challenge was not technical but rather community-related.
+• Christopher realized he couldn't do everything himself and started reaching out for help, but found it difficult to get contributors on board.
+• A significant turning point came when he spent six months working on a refactor of the core system with little progress, leading him to focus on solving the community problem.
+• He learned through experience and experimentation, without a formal mentorship or guidance, and relied on reading articles and online resources for advice.
+• Maintenance of test frameworks as a challenge due to new frameworks emerging
+• Frustration with attention being drawn away from established frameworks like Mocha
+• Importance of community and brand loyalty in maintaining project popularity
+• Difficulty in managing influx of donations and deciding how to use funds effectively
+• Funding experiments, such as Open Collective, as potential solutions for sustaining open source projects
+• Managing funds from donations and sponsorships
+• Challenges of using money to incentivize contributions
+• Perverse incentives and conflicts that arise when paying contributors
+• Difficulty in finding a sustainable way to fund Mocha development
+• Importance of having a project with internal momentum and willing contributors
+• Challenges of justifying the importance of tools like Mocha to employers or sponsors
+• Open source project growth and sustainability
+• Lessons learned from past projects (Mocha and other examples)
+• Grant funding for open source projects (Mozilla's MOSS program and JS Foundation)
+• Project scope and maintenance: when to consider a project "done" and walking away as maintainer
+• Balancing personal goals with community needs
+• Mocha's toolchain and dependencies are not fully supported on Windows
+• The current scope of Mocha includes test format convention, execution, and reporting
+• Christopher Hiller wants to see a more useful, full-on test runner with better API documentation and a clearer boundary between core functionality and external libraries
+• Burnout and frustration led Christopher Hiller to take a break from the project, but he is now contributing again due to renewed interest from others
+• The project needs dedicated maintainers and contributors to move forward; if that doesn't happen, Christopher Hiller may consider quitting or scaling back his involvement

Open Source History, Foundations, Sustainability_summary.txt

@@ -0,0 +1,56 @@
+• History of open source sustainability and its beginnings
+• Early companies embracing open source (Sun, IBM) and those opposed to it (Microsoft)
+• Emergence of new companies like Red Hat and their role in promoting open source
+• The "Homebrew Computer Club" and Bill Gates' shift from sharing code to selling executables
+• The creation of the term "open source" by Tim O'Reilly and its initial acceptance
+• How the term "open source" was used to reframe the discussion around software development
+• The role of peer-to-peer computing and music sharing in popularizing open source
+• Confluence of events (Linux, copyright law changes) that contributed to open source's rise
+• The importance of legal obligation (copyleft) in contributing to open source (or not)
+• Permissive licensing was used by Mozilla as a Hail Mary in 1998 to drive adoption of their client software
+• Early open source projects like Mozilla had to reassure individual contributors about patent and copyright jurisdiction
+• The Free Software Foundation (FSF) advocated for copyleft licenses, which were seen as necessary to prevent exploitation of the code
+• As software shifted from client-server to peer-to-peer models, distribution and contribution requirements became less relevant
+• Permissive licensing can drive adoption, but may not result in high-quality contributions
+• The Apache model emphasizes gifts of code over required contributions, prioritizing quality over obligation
+• Enforcement activities by the FSF now focus on encouraging sharing of extensions and improvements rather than punishing freeloaders
+• The concept of "freeloaders" in open source development, where individuals or organizations benefit from the collective effort without contributing equally
+• Concerns about money flow in modern foundations and their impact on project priorities
+• Historical examples of patent pooling and its potential benefits for open source projects
+• The creation and importance of foundations like Apache Software Foundation and Mozilla
+• Mitchell Baker's experience as Lizard Wrangler at Netscape and her role in establishing the Mozilla foundation
+• The need for open source developers to stand up and push back against threats to their project's sustainability.
+• Microsoft's opposition to open source due to its impact on their developer base
+• Two types of programmers: inventors and those who work with tools provided by others (e.g. Microsoft)
+• The role of abstraction in programming and how it relates to the ease of working with code
+• Open source as a foundation for software development, with contributors often unaware of their influence and power
+• The importance of recognizing one's own influence and advocating for oneself within open source projects
+• The evolution of open source from a community-driven effort to a more institutionalized structure
+• The role of foundations in supporting large-scale open source projects
+• Companies' relationships with their open source employees, including the importance of giving them autonomy and support
+• Determining when a project needs a foundation or institutional support
+• Apple's failure to create an open source foundation for their R&D efforts led to conflicts with other open source projects
+• Foundations like Apache provided transparent governance and democratization of standards development
+• Node.js was moved to a foundation due to a community rebellion against its BDFL organization
+• Historically, foundations were designed to bring transparency and governance to projects, not just fundraise or pay maintainers
+• Open source foundations have become valuable entities that are now subject to taxation and regulatory scrutiny
+• Jim Zemlin streamlined the process of creating new foundations through his work at OSDL
+• Comparing different open source foundations (FSF, Software Freedom Law Center, Eclipse, Apache)
+• Discussion of Eclipse's origins as a competitive move by IBM against Sun
+• Characteristics of various foundations: FSF's restrictive approach, Apache's developer-driven governance
+• Disparities in what foundations offer to projects: support for marketing, PR, and fundraising
+• Importance of separating project governance from institutional governance
+• Future of open source: potential need for umbrella foundations that are less involved in projects, using tools like GitHub instead of hosting own development environments
+• Concerns about creating numerous foundations and potential tax issues
+• Definition of an "umbrella" foundation and its implications
+• Pros and cons of joining an existing umbrella foundation
+• Copyright aggregation and its role in protecting open source projects
+• Importance of contributor agreements and long-term legal viability
+• Challenges of establishing provenance for open source contributions
+• Tension between short-term sustainability and long-term legal protection
+• The GPL's legal challenges and the potential for a formal court challenge
+• The difficulties in enforcing open-source licenses across complex software stacks
+• The trade-offs between individual project maintainers' rights and contributors' rights
+• The influence of money on open-source projects and the motivations behind decisions
+• The evolution of governance models, including BDFL, consensus, and foundation-based approaches
+• The long-term viability of open-source software and its potential for continued growth

Open source and supercomputers (Spack)_summary.txt

@@ -0,0 +1,44 @@
+• Todd Gamblin's job role at Lawrence Livermore National Laboratory
+• Overview of Lawrence Livermore's missions and responsibilities
+• Todd's specific work on Spack, DevOps, and machine learning for parallel performance
+• The lab's history with open source, including the development of Linux for HPC machines and popular open-source projects like ZFS and Slurm
+• Collaboration across the DOE, universities, and other laboratories
+• Slurm is used on Linux clusters at Lawrence Livermore Lab, including a 1.5 million core IBM Blue Gene machine
+• ZFS file system is used in industry and has been ported by Lawrence Livermore Lab for use with Lustre parallel file system
+• Spack package manager was open sourced by Todd Gamblin as part of his work at Lawrence Livermore Lab, but it's not the first project he open sourced
+• CRAM tool splits jobs into smaller ones to manage large-scale computing tasks on the lab's clusters
+• The lab has a policy document from 2004 requiring software developed under Advanced Simulation Computing Initiative to be open source unless there are reasons not to
+• Todd Gamblin notes that while some projects may generate royalties, others like Spack are more suitable for open sourcing and sharing resources among computing sites
+• The lab's IP organization reviews software releases, including a tedious process involving burning CDs and filling out paper forms
+• Spack is a package manager for high-performance computing (HPC) environments, specifically designed to build and manage software on large machines.
+• The project was created by Todd Gamblin at Lawrence Livermore National Laboratory to address specific challenges in the HPC software ecosystem, such as complex dependency management and reliance on vendor libraries.
+• Spack is a "functional" package manager that builds software from source and assigns a unique hash to each dependency graph, allowing for reproducibility and versioning.
+• The project's primary audience is not the general public but rather a smaller community of HPC researchers and developers who require high-performance computing capabilities.
+• Contributing to Spack requires specialized knowledge of HPC environments and software development, limiting its contributor base.
+• Growing the contributor base could involve expanding outreach to industry partners and other stakeholders in the HPC community.
+• Structure of HPC communities with multiple roles (users, developers, center staff)
+• Spack deployment model vs cloud-based models
+• HPC centers' varying approaches to open source software and community building
+• Influence of industry on government's open source practices and adoption of GitHub
+• Challenges in implementing open source practices within government labs
+• NumFOCUS affiliation for the Spack project
+• Democratizing package management in HPC through Spack
+• Cultural differences between cluster maintainers and casual users
+• Spack's design choices (Python, Homebrew-based format) to make it easy for users to contribute
+• Comparison with other HPC package managers (EasyBuild)
+• Funding models for Spack (programmatic funding, grants from the Office of Science, LDRD)
+• Challenges in navigating funding opportunities and the gap between research funding and production funding
+• Importance of socializing projects to obtain programmatic funding
+• Challenges with maintaining software projects due to lack of funding stability
+• Importance of exit plans for research projects, including programmatic funding options
+• Differences in how government organizations and private companies approach software maintenance costs
+• Benefits and limitations of using grants versus programmatic funding for research projects
+• Strategies for sustaining software products through community building and contributor engagement
+• Impact of academic cycles on contribution rates to software projects
+• Success stories, such as Exascale, where focus is placed on developing software rather than just writing papers or getting funding
+• Development of software stack for large-scale scientific applications
+• Coordinating releases of multiple applications within the stack
+• Balance between open-source and proprietary components in the stack
+• Involving industry contributors and expanding HPC adoption to smaller companies
+• Addressing support needs for industry users and potential solutions (e.g. support contracts, small companies)
+• Lessons learned from open-sourcing Spack and importance of thinking beyond one's own use case