add all 2017 summaries

Conversational Development and Controversy_summary.txt

@@ -0,0 +1,14 @@
+• GitLab's Master Plan and conversational development
+• Recent controversy around removing and reposting security research data on GitHub and GitLab
+• Progress on executing the Master Plan, with 80% of envisioned features now in the product
+• Discussion of online IDEs and whether they are a good fit for GitLab
+• Thoughts on container schedulers and dev environments being similar to production environments
+• Groot's research on vulnerable servers caused GitLab to initially remove the list
+• The decision to remove the list was later reversed after considering the interests of users and server owners
+• The publication of the list led to 650 servers being fixed, showing that transparency can be effective in prompting action
+• Sid Sijbrandij discusses the complexities of responsible disclosure policies and the gray areas that can arise
+• He emphasizes the importance of having a unified voice as a company, but also values individual expression and open conversation
+• The interview concludes with a discussion about GitLab's presence at OSCON and their support for conferences and open-source projects
+• Partnership with O'Reilly for OSCON London 2016
+• Upcoming event: OSCON 2017 in Austin, Texas
+• Discount code for OSCON 2017: "changelog20" for 20% off registration

Focused on a Safe and Inclusive Node Community_summary.txt

@@ -0,0 +1,45 @@
+• Role of education community manager at NodeJS Foundation
+• Inclusivity Working Group and its challenges
+• Conference organizing as a hobby and its human-related difficulties
+• Open source tooling for conferences, such as website and review system development
+• The state of available open-source tools for conference organization
+• How To Conf repo documentation on running JavaScript events
+• Challenges with maintaining and updating existing conference websites and tools
+• Discussion about the conference lanyards and badges
+• Comparison between different types of conference swag (lanyards vs. wooden engraved badges)
+• FutureStack conference mentioned as an example of a company doing hardware badges well
+• Sponsorship management challenges at conferences
+• Language barriers in programming and international collaboration
+• Accessibility and consideration for speakers with non-native languages
+• Difficulty communicating due to language barriers at conferences
+• Importance of inclusivity and diversity in conference planning
+• Challenges of creating a diverse speaker lineup without tokenizing under-represented groups
+• Need for community involvement and support in making conferences feel safe and inclusive
+• Childcare options and accommodations as important details for attendees with family responsibilities
+• Trust and liability concerns when hosting events with children
+• Security measures at the conference venue
+• The importance of inclusivity and creating a welcoming environment for attendees
+• Comparing single-track conferences (like How To Conf) to multi-track conferences (like Node Interactive)
+• Plans for sharing best practices and lessons learned from past conferences
+• Inclusivity strategy and future plans for the Node community
+• Community growth, outreach, and onboarding new contributors
+• Rebooting documentation efforts to align with community values
+• Guidelines or resources for new community members to find help and support
+• Creating a community org within the Node Foundation to facilitate collaboration and representation
+• Empowering local communities to take ownership of their projects and initiatives
+• Providing coordination and resources for event organizers, including sponsorship and logistical support
+• Establishing governance structures and providing guidance on organizational setup
+• Considering localized community managers or "lieutenants" to facilitate communication and support between the central community and local groups
+• Challenges of traveling and attending events due to costs and physical demands
+• Use of video conferencing tools such as Skype and Google Hangouts
+• Importance of building relationships and trust with community members for successful collaborations
+• "Speaker fatigue" and "organizer fatigue" in running local meetups and events
+• Need for empowering local communities through Node Foundation backing and education initiatives
+• Benefits of face-to-face interactions and conversations
+• Challenges of education and inclusivity efforts due to physical location-based models
+• Ways to contribute to Node's inclusivity efforts, including working groups, community organizations, and volunteering at meetups.
+• Conducting a survey to gather data on Node users and their experiences
+• Focusing resources on addressing user struggles with getting started or documentation
+• Developing a certification exam for Node professionals, with a low-cost goal and browser-based testing
+• Challenges in hosting the exam in China due to regulations and requirements
+• Targeting end of Q1 for English version certification exam release

How China does Node_summary.txt

@@ -0,0 +1,21 @@
+• The Great Firewall of China's impact on software development and internet access
+• Shiya Lou's experience transitioning between US and Chinese software development environments
+• Language barrier affecting Chinese developers' ability to access foreign documentation and resources
+• Use of VPNs to bypass censorship and surveillance in China, but instability and constantly changing services
+• Cnpm (China's npm) as an example of adapting Node.js ecosystem for Chinese developers due to language and firewall barriers
+• Language barriers and limitations in China
+• Importance of being "China-friendly" for businesses targeting the Chinese market
+• Speed and latency issues due to external servers outside of China's borders
+• Need for companies to consider hosting servers within China to improve speed
+• Challenges of complying with regulations and laws specific to China
+• Discussion on the Great Firewall of China and its impact on internet access
+• Shiya Lou explains how the firewall was implemented after protests in 2008 and has since been expanded to block certain websites and services
+• Alternative search engines available in China, such as Baidu and 360 Search
+• Differences between Google's results in China versus those outside of China
+• Challenges of accessing Chinese servers and websites from outside of China due to the Great Firewall
+• Discussion on Cnpm (Company npm), a mirror of npm that allows for faster package downloads in China
+• Shiya Lou's personal stance on working with the government to bypass parts of the firewall, which he is against
+• Concerns about language barrier for developers in China
+• Importance of English language skills for Chinese developers to keep up with global programming knowledge
+• Comparison of Ruby creator Yukihiro Matsumoto's use of Japanese and English in programming contexts
+• Openness to having non-English speaking guests on a podcast, such as Matsumoto

Keeping Node Core Small_summary.txt

@@ -0,0 +1,31 @@
+• Keeping Node Core small and modular
+• Limiting features added to Core to prevent breakage and promote stability
+• Encouraging more modules and less in-Core functionality
+• Addressing issues with pre-packaged dependencies and the inability to choose specific module versions
+• Considering removing certain libraries from Node Core, such as URL and Promises
+• Discussing solutions for handling dependencies and breaking changes when removing or changing libraries
+• Adding a WHATWG compliant URL parser to Node's internals for consistency
+• Vendoring in third-party modules instead of duplicating functionality
+• Deprecation and removal of Node's built-in URL library
+• Using npm-installed versions of libraries for userland code instead of built-in ones
+• Punycode module being deprecated and possibly removed due to low usage
+• Concerns about breaking changes if removing or deprecating the URL library
+• Criteria for determining what should be in Node Core vs userland modules
+• Deprecating and removing outdated or obsolete modules
+• HTTP/2 module, including potential performance benefits and implementation challenges
+• Pre-built binaries for Node ecosystem to facilitate easier installation of native dependencies
+• URL library deprecation and replacement with a better version
+• Websocket APIs and their relationship to Node Core vs userland modules
+• Node HTTP API and its complexity
+• Tradeoffs between performance, implementation ease, and maintenance costs
+• HTTP/2 protocol implementation and its implications for Node
+• Streams module: design issues, user problems, and alternative solutions
+• Soft deprecation approach for deprecated modules (e.g. Streams)
+• Potential movement of streaming capabilities to libuv
+• Maintenance and documentation strategies for Node Core
+• Changing the API to force correct usage of Streams
+• Potential breaking changes causing issues in dependent modules
+• Documentation updates as a solution
+• Educational process (blog post, etc.) to inform users about the change
+• Plans to eventually remove Streams from Node Core
+• Readable Streams documentation improvement

Node at Microsoft, ChakraCore, and VM Neutrality_summary.txt

@@ -0,0 +1,27 @@
+• The importance of Node to Microsoft
+• VM neutrality and its benefits for developers
+• Chakra and ChakraCore: a high-performance JavaScript engine and its relationship to Node
+• Why Microsoft forked Node and created ChakraCore
+• IBM's involvement with Microsoft in promoting Node with VM neutrality
+• ChakraCore is the core part of the Chakra JavaScript engine
+• Chakra engine powers Edge browser and Windows 10
+• ChakraCore is cross-platform and open source
+• Open sourcing ChakraCore allowed for community engagement, innovation, and growth
+• The decision to open source was motivated by a desire to help the community, allow developers to use the technology, and reach a wider audience
+• Technical steps to open source were minimal due to existing work on modern hosting API and supporting Windows 10 IoT platform
+• Chakra is used in various Microsoft products including Azure DocumentDB, Outlook.com, and others
+• Future plans include taking Chakra cross-platform
+• Chakra engine available on Linux and Ubuntu x64 versions, with a Mac OS X preview
+• Goal of parity between Windows and other platforms for functionality, performance, and characteristics
+• Time-travel debugging innovation being developed in collaboration with Microsoft Research
+• Open sourcing of ChakraCore code on GitHub, with MIT license and open documentation
+• Community involvement encouraged through GitHub issues, roadmap transparency, and contribution opportunities
+• Cross-platform development efforts for Node ChakraCore and Nappy (Node.js API) layer stability guarantee
+• Ways to get involved: try new technology, file issues, report problems, contribute code, or join the API Working Group
+• Node Core project and API Working Group discussed
+• Nappy (N-API) project mentioned, goal is to create stable Node API for module developers
+• Need community help to convert native modules onto new API
+• VM neutrality and its importance
+• Microsoft's involvement in Node and ChakraCore
+• Azure as a cloud platform for Node development
+• Efforts to improve developer experience with VS Code, TypeScript, Docker, and app insights

Node, IoT, and Robotics_summary.txt

@@ -0,0 +1,27 @@
+• Rachel White's role as a Technical Evangelist at Microsoft
+• Node.js and its applications in IoT, robotics, and web development
+• NodeBots and Edge (Microsoft's platform for building IoT applications)
+• Rachel's personal projects, including a Twitter bot that uses facial recognition and creates funny images
+• The importance of making learning fun and the value of autodidact learning
+• Overcoming impostor syndrome and embracing one's strengths in problem-solving rather than memorization
+• Impostor syndrome and feeling like one doesn't belong in their role
+• Overcoming impostor syndrome through embracing mistakes and imperfections
+• The importance of accepting and learning from mistakes in the creative process
+• Fear of failure and success holding people back from pursuing their goals and ideas
+• Embracing imperfection and not being afraid to try new things
+• Rachel White's experiences with giving technical talks and demos at conferences
+• Discussion of hardware and internet of things
+• Encouraging non-programmers to learn programming through examples like Andy Reitano's NESpectre project
+• Role of gaming as a breeding ground for software developers
+• Importance of breaking down complex concepts into simple terms for non-technical audiences
+• Rachel White's experiences with NodeBots and creating fun hardware projects
+• Her personal experience with an RFID chip implanted in her hand
+• Rachel White discusses her RFID chip implant, which can be read and written by Android devices.
+• She expresses hope for the future of Node, focusing on making secure systems and private information.
+• Rachel emphasizes the importance of innovation and utilizing technology in ways that benefit people beyond enterprise needs.
+• She mentions the Tessel microcontroller, a platform with Node pre-installed, which simplifies hardware development and has sparked community growth.
+• The conversation touches on hackathons, exposing new programmers to Node, and Rachel's enthusiasm for making cool and weird projects outside of daily work.
+• The importance of creative process and personal meaning in artistic creation
+• Release of art into the world means relinquishing control over its reception
+• Code can be considered a form of art due to creation from nothing
+• Importance of considering how others will perceive one's work

Node.js Backstory and Future_summary.txt

@@ -0,0 +1,47 @@
+• io.js fork from Node in 2014
+• Formation of the Node Foundation with Linux Foundation and initial governance model
+• Merger of io.js back into Node and iteration on governance policies for LTS releases
+• Growth of contributors, diversification of contributor base, and increasing overall contributor count
+• Shift from proof-of-concept to sustainability strategy and increased focus on community contributions beyond just code
+• Comparison with other platforms such as Swift, Rails, Phoenix, and Elixir on community structure and contributor diversity
+• Measuring Node.js growth and success against its own ecosystem, rather than comparing it to other languages
+• Node.js user community has quadrupled in size since the io.js fork, reaching 5.7 million users
+• Growth is attributed to JavaScript itself, with many people using Node.js for various applications beyond server-side development
+• The community is broadening its view of what Node.js is used for, including IoT, frontend frameworks like React, and desktop applications
+• Challenging issues include keeping things simple and easy-to-use, and providing educational materials for new users
+• The Linux Foundation's support has enabled new initiatives such as childcare services and diversity efforts at the NodeConf conference
+• The community has benefited from institutional support, allowing them to provide resources that were previously unavailable.
+• Discussing the importance of inclusivity and diversity in community conferences
+• The use of colored stickers to indicate preferences for photography or approachability
+• The role of Tracy in pioneering diversity and inclusivity work in community conferences
+• The benefits of VM neutrality, including increased competition among VM developers and improved performance for users
+• The open sourcing of ChakraCore and its potential impact on the Node.js ecosystem
+• The collaboration between Microsoft and other companies to improve Node.js development and user experience
+• Creating a stable API in Node.js to enable VM neutrality
+• Importance of the Node Foundation in bringing together stakeholders for long-term support
+• Transition from BDFL governance model to open governance model with the creation of io.js
+• Growing community needs and limitations of Joyent's stewardship of Node.js
+• Value of Rod Vagg's leadership in establishing a more inclusive and open governance model
+• Increased committer numbers (from 5 to almost 100)
+• VM neutrality benefits for IoT development, including new JavaScript VMs on-device
+• Node serial testing matrix is slow and outdated
+• Importance of security in the Node ecosystem
+• Lift Security's Node Security Project and its integration into the Node Foundation
+• Creation of a new working group for responsible disclosure of security vulnerabilities
+• Concerns about the diversity and quality of packages in the Node ecosystem
+• Need for formal education and certification programs for developers
+• Plans to develop a baseline Node.js certification program with The Linux Foundation
+• Discussion of Athan Reines' open source project, Standard Lib, for data science in JavaScript
+• Challenges in Node.js for math and scientific computing due to lack of language-level tools
+• Efforts by Mikeal Rogers and the Node Foundation to resolve standards issues through TC39 meetings
+• Importance of reaching a system like R and Python have for scientific computing in JavaScript
+• Modular ecosystem development for 3D computing using WebGL, Regl, and ndarray
+• Comparison with SciPy and R's approach to binding Fortran libraries
+• Nurturing developers working on open source projects through community building and outreach
+• Passionate individuals at academic institutions driving Node.js adoption
+• Need for a venue for developers to share knowledge and experiences
+• Growth of the Node community and its challenges
+• Importance of supporting module developers and experimental projects
+• Diversity in the Node community as an important consideration
+• Focusing on serverless capabilities and resource utilization improvements
+• Potential for more assertive messaging about Node's strengths

The State of HTTP2 in Node_summary.txt

@@ -0,0 +1,32 @@
+• State of HTTP/2 implementation in Node
+• Impact of HTTP/2 on Node's performance profile and APIs
+• Decision on whether to include HTTP/2 in NodeCore or as a module
+• Definition of web fundamentals and criteria for inclusion in Core
+• Importance of keeping NodeCore small and focused on basic web protocol support
+• New features and complexities introduced by HTTP/2, such as stateful header compression and multiplexing
+• Discussion around Node.js and HTTP/2 protocol
+• Importance of security in Node.js with HTTP/2
+• How HTTP/2 supports better security through compliance to specification
+• Browsers requiring TLS for HTTP/2 connections
+• Limitations of Node's current TLS performance
+• Excitement about developers using HTTP/2 and its potential
+• New features and applications enabled by HTTP/2, such as push streams
+• Criticisms of the HTTP/2 protocol, including staple header compression limitations
+• Binary coding vs stateless compression for headers
+• Complexity of HTTP/2 protocol (flow control, prioritization)
+• Server affinity issue with HTTP/2 and proxy software vendors
+• Performance benefits of HTTP/2 (efficient socket use, reduced failures)
+• Tradeoffs between HTTP/2 features (e.g. header compression, TLS) and API complexity
+• Breaking changes to Node's API for HTTP/2 adoption
+• The challenges of adopting HTTP/2 as it requires deliberate design and implementation.
+• Potential use cases for HTTP/2 include server-to-server communication within protected environments.
+• James Snell is working on the HTTP/2 implementation, but it's open-source and contributed by multiple developers.
+• The Node organization is developing HTTP/2 under a GitHub repo (github.com/nodejs/http2).
+• It may be possible to use both HTTP/1 and HTTP/2 simultaneously, with clients negotiating which protocol to use per socket.
+• Deprecating HTTP/1 is considered premature due to its fundamental role in the Node ecosystem.
+• Implementing HTTP/2 as a native module is being explored as an alternative to integrating it into Core.
+• Request for help from the community
+• James Snell mentions stabilizing and testing aspects of a project
+• Areas where help is specifically needed (tests, performance benchmarks)
+• Repository link provided for reference
+• Conversation importance due to Node Interactive's closure

The State of HTTP⧸2 in Node_summary.txt

@@ -0,0 +1,47 @@
+• Introduction to Spotlight series on Node.js
+• Interview with James Snell about H2 implementation for Node.js
+• Discussion of current state and challenges of implementing H2 in Node.js
+• Debate over whether H2 should be a module or part of Node's core
+• Importance of keeping Node's core small and focused
+• Defining what belongs in Node Core vs. separate modules
+• Importance of keeping Node Core small and focused on web fundamentals
+• URL parsing as an example of a functionality that could be moved to a separate module
+• Discussion on H2 protocol and its differences from H1, including binary framing, stateful header compression, and implications for web application design and performance
+• Security as a top priority for the next year
+• H2 protocol will be designed to be highly spec-compliant and prioritizes security over performance
+• H1 was not fully compliant with the specification, which led to several security issues
+• H2 servers will require TLS connections by default due to browser implementation requirements
+• Node's reputation as a TLS terminator is a limitation that needs improvement for better performance
+• H2 enables new extensibility models and possibilities for new kinds of protocols
+• New proposals for other layered protocols are emerging within the working group
+• WebSockets' relationship with H1 is being considered as a precedent
+• The framing model in H2 will allow for experimentation without the pain of introducing WebSockets like before
+• Potential innovations could come out of it, but require collective experience and testing
+• Criticisms of the H2P protocol include:
+  • Inefficient header compression (staple header compression)
+  • Repetitive headers leading to waste in transmission
+  • HPAC's stateful compression model adds complexity
+  • Maintaining state tables can be resource-intensive
+• Additional complexity in H2 compared to H1
+• Flow control and prioritization in H2
+• Impact on proxy software vendors and protocol criticism
+• Server affinity issue with H2
+• Performance benefits of using H2 efficiently (e.g. better request handling)
+• Memory usage trade-off for increased performance
+• H2 protocol offers a significant savings of header bytes, potentially saving users money on bandwidth costs
+• The adoption of H2 requires careful consideration due to trade-offs in security and API compatibility with H1
+• Status messages are removed in H2, which may break existing applications that rely on them
+• Designing an application specifically for H2 is necessary to take advantage of its capabilities
+• H2 is more suitable for internal server-to-server communication rather than user-facing web servers
+• The H2 project is currently being worked on by a single developer with plans to grow the team and accept open-source contributions
+• H2 protocol implementation and integration into Node.js
+• Discussion about deprecating the H1 protocol in favor of H2
+• Decision to offer both H1 and H2 as options for developers
+• Implementation challenges and future plans for HTTP development in Node.js
+• Consideration for a module-based approach for H2 implementation
+• Discussing the size and complexity of an ecosystem
+• Need for input on code direction
+• Best ways to provide feedback and get involved (repo, open issues, pull requests)
+• Code stabilization and distinct areas needing help (tests, performance benchmarks)
+• Linking repo in show notes
+• Closing down Node Interactive