open source product management (feat. npm)

Nov 19, 20141 like1,490 views

I make the npm CLI go, in my role as the CLI team lead for npm, Inc. I go over what npm is, the challenges it faces, and how I (and the rest of my team and the company) manages the special challenges of doing product management as part of a community rather than a business owner within an enterprise. Also I tell a couple totally obscure in-jokes.

open source
product management
with npm
@othiym23 / Forrest L Norvell
npm, Inc.

npm is many things
• project
• company
• team
• philosophy & ethos
• product family

npm is many
softwares
• registry
• website
• CLI

npm CLI team duties
• meet npm, Inc.’s business
objectives
• fix bugs
• support current npm users
• keep npm moving forward

make npm the most useful
tool it can be for the most
people

open source product management (feat. npm)

• 356 support tickets
• 222 bugs
• 236 feature requests

traditional product
management
• own the roadmap
• sell the strategic vision
• mediate between business
owners, developers, & other
stakeholders

say no a lot, but
be stubborn about
what you say yes to

open-source product
management
• balance competing demands
• consensus-seeking
• but sometimes you have to say
no

npm is not an
infinitely extensible
miracle pegacorn

• looked at a lot of different
requests
• came up with a global solution
for many local problems
• try to keep each goal
supporting the others

npm’s roadmap
• scoped packages
• multi-stage install / dependency
tree realization
• npm as API
• better Windows support
• client-side development support

the npm release
process
• new release every Thursday
• new releases published to
npm@next for about a week of
burn-in
• `npm@latest` for safe production
release, `npm@next` if you want
to help test the next release

supporting npm
• the CLI team doesn’t have much
time for support
• `npm report` will make
crowdsourcing that easier, but
it’s a ways out
• answering questions with the
`support` label is ❤️ by me

using the npm issue
tracker: labels
1. bug, support, feature request
2. next-patch, next-minor, next-major
3. documentation, patch-welcome,
and novice

using the npm issue
tracker: best practices
• don’t add your bug to a closed issue
• …but please do add specific details
that helped you
• no such thing as too much
information, but gists are useful
• use cases are useful, +1s are
terrible

PATCHES WELCOME
• pull requests with tests are
landed as quickly as
practicable
• no patch is too small
• …but some patches are too big

developing npm
• `npm test` while developing
• `npm run test-all` before
submitting PR
• update the docs, plz
• people who add tests are my
favorite people

thanks for listening /
thanks for helping /
thanks for being you

The document discusses working with npm packages. It provides guidance on how to find suitable npm packages based on quality, GitHub activity, and downloads. It outlines steps for modifying existing packages such as forking the repository, making changes locally or as a pull request. The document also describes how to create and publish a new npm package by initializing it with npm, adding metadata to the package.json file, and publishing updates to npm.

Jaap : node, npm & gruntBertrand Chevrier

Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It uses an event-driven, non-blocking I/O model that makes it lightweight and efficient for data-intensive real-time applications that run across distributed devices. The document discusses Node.js' architecture, its use of JavaScript for simplicity, and how it is inspired by other technologies like Twisted and EventMachine. It also covers related tools like NPM for package management and Grunt for automating tasks.

Multiple django applications on a single server with nginxroskakori

Deployment taken seriously with Octopus Deploy and TeamCityTomas Jansson

Tomas Jansson presented on how to implement continuous deployment using Octopus Deploy, TeamCity, and PowerShell. The goal is to have an automated deployment process that builds, tests, and deploys code changes from version control to environments multiple times a day. TeamCity is used for continuous integration to build and run tests on code changes. Octopus Deploy provides a dashboard to manage deployments to environments like QA and production. It supports promotion of deployments between environments using a NuGet package. PowerShell scripts are run during the deployment process for tasks like configuration transformations. A demo showed how these tools can be configured to achieve continuous deployment.

Frontend Build Tools - CC FE & UXJWORKS powered by Ordina

This document discusses several frontend build tools: Grunt, a JavaScript task runner that automates tasks through plugins; Bower, a dependency management tool for installing frontend packages; Yeoman, a scaffolding tool that generates project structures using generators; and Gulp, an alternative to Grunt that uses streaming for faster, more efficient builds. It provides an overview of what each tool is used for and how to set them up, with code examples for Grunt, Bower, and Yeoman workflows.

Understanding Non Blocking I/O with PythonVaidik Kapoor

Video recording of the talk: https://www.youtube.com/watch?v=t0VljE9kq1Q As an engineer working on any web stack, you may have heard about Blocking and Non-Blocking IO. You may as well have used any framework or library that supports Non-Blocking IO. After all, they are very useful as you don’t want to block execution of other tasks while one task is waiting to complete a network call to another service (like HTTP call to an API or may be a TCP call to your database). Non-Blocking IO while doing tasks and not wait for IO. This also helps us handle a lot many connections than we possibly could with Blocking IO. Python supports Non-Blocking IO, but we always use some existing 3rd party library that hides all the gory details and makes it all look like black magic to the uninitiated. But there is nothing like black magic. This presentation will be an introductory talk focused at explaining how Non-Blocking IO works, which is the basis of libraries like Gevent, Tornado and Twisted. We will learn about how Non-Blocking IO can be implemented using the most basic modules that form the base for the above mentioned libraries. Hopefully after this talk, Non-Blocking IO will not be an unsolved mystery for you anymore.

Octopus Deploy Tech Fest 2014adriantwright

This document discusses continuous deployments using Octopus Deploy. It begins with background on the speaker and an outline of topics to be covered. The speaker then discusses the importance of automation and challenges organizations face achieving it. Key benefits of Octopus Deploy highlighted include its flexibility, ability to improve development processes and visibility, support for .NET and other technologies, excellent customer support, and feature-rich capabilities. The presentation concludes with a demo of setting up continuous deployment of a sample application with Octopus Deploy.

S&T What I know about Node 110817Dan Dineen

Node is a JavaScript runtime environment that allows JavaScript to run on the server. It uses Google's V8 JavaScript engine and allows developers to build fast and scalable network applications using JavaScript. Node installs with NPM (Node Package Manager), which is used to install dependencies and share JavaScript code as reusable modules. Many modern web development processes use Node and NPM together to compile assets, run tasks, and share code.

Infrastructure development on windows ldn cd meetup Owain Perry

ZendCon 2015 - DevOps for Small TeamsJoe Ferguson

Joe Ferguson discusses how small development teams can implement DevOps practices. He recommends using version control for all code and configurations, developing on the same environments that are deployed (using Vagrant), implementing continuous integration and testing, and automating common tasks through aliases, scripts, and cron jobs. The talk provides many specific tools and resources for setting up version control, continuous integration, testing, and automation for small teams.

Making your first contribution to ForemanDominic Cleal

This document provides guidance on how to make contributions to the Foreman project. It discusses managing issues in Redmine, setting up a development environment, crafting code patches, submitting pull requests, and the review process. Specific issues are listed that could be worked on, related to Foreman core, the Foreman installer plugin, and the Hammer CLI. The goal is to welcome and guide new contributors.

Introduction to using Grunt & Bower with WordPress theme developmentJames Bundey

ZendCon 2015 - Laravel Forge: Hello World to Hello ProductionJoe Ferguson

With the recent release of Laravel Forge, Envoyer and Homestead, it has never been easier to go from nothing to something with an easy to use PHP Framework. This talk will cover creating a basic Laravel application using the Laravel specific Vagrant box "Homestead", connecting to a server (Linode, Rackspace, Digital Ocean), and deploying the application via Forge. The talk will also cover tips and tricks on customizing Homestead to fit custom needs as well as how to use Forge & Envoyer to deploy new versions of our application.

Grunt js and WordPressWP Australia

DevOps tools for everyone - Vagrant, Puppet and Webminpostrational

Web Leaps ForwardMoh Haghighat

The document discusses the history and development of HTML5 and JavaScript performance. It covers how: 1) JavaScript performance improvements through just-in-time compilers and other optimizations led to a 100x increase in speed over time, enabling complex web applications. 2) The introduction of asm.js allowed native C/C++ code to be compiled to highly optimized JavaScript, closing the performance gap with native apps. 3) Recent efforts are bringing parallelism to web runtimes and the SIMD.js API in order to better utilize multi-core processors and continue improving JavaScript performance.

JUST EAT: Tools we use to enable our culturePeter Mounce

Just Eat is an online takeaway company that has been operating since 2001 in Denmark and 2005 in the UK. They have adopted a DevOps culture where each team owns their own features and infrastructure. To enable this distributed system on Windows at scale without an Active Directory, they rely on tools like persistent chat, real-time monitoring, alerting, and centralized logging to improve collaboration and debugging in production. Their most important aspects are culture, autonomy for teams, and pragmatic use of tools based on merit.

Workshop For pycon13Steven Pousty

This document provides an agenda and overview for an OpenShift workshop on Python development. The workshop will introduce OpenShift and demonstrate how to create Python applications using the OpenShift platform-as-a-service. Attendees will learn to create applications from the command line and web console, add databases like MongoDB, and use tools like Git for version control. The document outlines assumptions about attendees' experience and what will be covered, including supported technologies, available resources, and terminology for the workshop.

What grunt?Lucio Martinez

Grunt is a task runner that can be used to automate repetitive tasks like minification, compilation, unit testing, and linting. It uses plugins, or tasks, that are run from a Gruntfile configuration. Common tasks include concatenating files, compiling LESS/Sass to CSS, linting JavaScript, optimizing images, and more. Tasks can be combined and customized to set up efficient development and production build processes. Grunt runs tasks defined in the Gruntfile configuration to minimize assets, concatenate files, reduce requests, and optimize the final code and assets that are delivered to users.

Helpful pre commit hooks for Python and Djangoroskakori

Rubygem Dev And WorkflowDr Nic Williams

This document discusses how to package Ruby code for distribution. It recommends using RubyGems for packaging and distributing gems, with GitHub or RubyForge for source code management and hosting. It also recommends using continuous integration services like RunCoderun to automatically test code on commits. The workflow involves packaging code as a gem, hosting it on a public install site like RubyForge, storing the source code in a public GitHub repository, and using a service like RunCoderun to run tests whenever the code is updated.

Modern Development ToolsYe Maw

[Quality Meetup #20] Michał Górski - Continuous Deployment w chmurzeFuture Processing

W dzisiejszych czasach praca z chmurą pozwala niesamowicie zmniejszyć koszta wejścia na rynek z rozwiązaniami typu PoC i MVP oraz w późniejszych etapach rozwoju produktów skalować oprogramowanie według potrzeb. Niestety nie jest to złoty środekt i rozwiązując stare problemy, tworzy nowe. Dlatego, oprócz zapoznania się z technologią serverless, czy Infrastructure as a Code, spróbujemy przede wszystkim stworzyć bezpieczne środowisko, pozwalające na Continuous Deployment.

Getting Started with Docker (For Developers)ColdFusionConference

Getting started with Octopus DeployKaroline Klever

How do you automate the non-existing deployment routines of an organization with over 100 different customers, each having their own environments? How do you convince the leaders, developers and customers to give you the resources needed in order to automate everything? Is it really possible to introduce a deployment routine that works for everyone? In less than six months, Karoline transformed the deployment routines at Epinova by introducing Octopus Deploy to the organization. She will take you through the steps needed to get started, the pitfalls along the way, and success that Octopus Deploy has become. In this workshop we will start out by installing an Octopus Deploy server and tentacle on your laptop, before looking at the basic concepts of Environments, Machines, Roles and Projects. You will create a project of your own and deploy this using Octopus Deploy before we round off by looking at the advanced topics of Script modules, Step templates, Variable sets and Retention Policies. At the end of this workshop, you'll have all the knowledge you need in order to create a more efficient and failproof deployment process for your project. Keep calm and deploy to production!

Vagrant, Chef and TYPO3 - A Love AffairMichael Lihs

Bringing Open-Source Practices to Your Day JobBen Coe

Nodeconf npm 2011Florent Jaby ヅ

The document provides an overview of the Node Package Manager (npm). It discusses how npm works to reduce friction in the software development process by making it easy for developers to install packages and dependencies without conflicts. It describes npm's vision of avoiding "dependency hell" and its strategies for achieving this like ensuring consistent interfaces and reducing excessive metadata requirements. The document also summarizes key npm commands, how installations work, and future plans like binary distributions, an automated testing system called npat, and build farms to test packages on multiple platforms.

More Related Content

What's hot (20)

Octopus Deploy Tech Fest 2014adriantwright

S&T What I know about Node 110817Dan Dineen

Infrastructure development on windows ldn cd meetup Owain Perry

ZendCon 2015 - DevOps for Small TeamsJoe Ferguson

Making your first contribution to ForemanDominic Cleal

Introduction to using Grunt & Bower with WordPress theme developmentJames Bundey

ZendCon 2015 - Laravel Forge: Hello World to Hello ProductionJoe Ferguson

Grunt js and WordPressWP Australia

DevOps tools for everyone - Vagrant, Puppet and Webminpostrational

Web Leaps ForwardMoh Haghighat

JUST EAT: Tools we use to enable our culturePeter Mounce

Workshop For pycon13Steven Pousty

What grunt?Lucio Martinez

Helpful pre commit hooks for Python and Djangoroskakori

Rubygem Dev And WorkflowDr Nic Williams

Modern Development ToolsYe Maw

[Quality Meetup #20] Michał Górski - Continuous Deployment w chmurzeFuture Processing

Getting Started with Docker (For Developers)ColdFusionConference

Getting started with Octopus DeployKaroline Klever

Vagrant, Chef and TYPO3 - A Love AffairMichael Lihs

Octopus Deploy Tech Fest 2014adriantwright

S&T What I know about Node 110817Dan Dineen

Infrastructure development on windows ldn cd meetup Owain Perry

ZendCon 2015 - DevOps for Small TeamsJoe Ferguson

Making your first contribution to ForemanDominic Cleal

Introduction to using Grunt & Bower with WordPress theme developmentJames Bundey

ZendCon 2015 - Laravel Forge: Hello World to Hello ProductionJoe Ferguson

Grunt js and WordPressWP Australia

DevOps tools for everyone - Vagrant, Puppet and Webminpostrational

Web Leaps ForwardMoh Haghighat

JUST EAT: Tools we use to enable our culturePeter Mounce

Workshop For pycon13Steven Pousty

What grunt?Lucio Martinez

Helpful pre commit hooks for Python and Djangoroskakori

Rubygem Dev And WorkflowDr Nic Williams

Modern Development ToolsYe Maw

[Quality Meetup #20] Michał Górski - Continuous Deployment w chmurzeFuture Processing

Getting Started with Docker (For Developers)ColdFusionConference

Getting started with Octopus DeployKaroline Klever

Vagrant, Chef and TYPO3 - A Love AffairMichael Lihs

Similar to open source product management (feat. npm) (20)

Bringing Open-Source Practices to Your Day JobBen Coe

Nodeconf npm 2011Florent Jaby ヅ

State of the CLI- Kat MarchanNodejsFoundation

Practical Methods for Adopting DevOps - Michael StahnkePuppet

The document outlines 5 methods for adopting DevOps practices in large organizations with siloed IT teams: 1) Standardize variable infrastructure to reduce failures, 2) Break down silos through collaboration between teams, 3) Share knowledge of failures to prevent recurrences, 4) Experiment with new tools and processes in test environments, 5) Continuously improve processes by addressing root causes rather than symptoms. The methods advocate reducing variability, integrating operations into software development, conducting root cause analyses, and allowing engineers to experiment.

Get lean tutorialMarty Haught

This document provides a summary of a tutorial on lean concepts and techniques for Ruby on Rails projects. The tutorial covers lean principles like minimizing effort, measuring progress, and delivering features rapidly. It discusses how concepts like the minimum viable product, continuous delivery, and kanban can help Rails projects. Examples are provided and exercises encourage participants to apply these lean ideas to sample projects. The goal is to introduce lean thinking and give attendees a starting point for making their work more efficient.

Building an Open Source AppSec PipelineMatt Tesauro

Diving into SngularJSfrancisspor

apidays LIVE New York - Navigating the Sea of Javascript Tools to Discover Sc...apidays

Building a custom cms with djangoYann Malet

1. The document outlines the process and methodology for building a custom content management system (CMS) with Django. It discusses planning the project through iterative sprints, dealing with migrating legacy data from existing systems, and determining when to customize Django versus using or contributing to existing third-party apps. 2. When migrating legacy data, the document notes it is important to make the migration process easy to run frequently as the data model evolves. Tips include using other servers to avoid slowing down development and handling inconsistent or complex legacy data fields. 3. In determining whether to customize Django or use third-party apps, the document recommends starting with app templates and reusable apps but being willing to fork early if

Building Open-Source React ComponentsZack Argyle

Building Open-source React ComponentsZack Argyle

Lessons from DevOps: Taking DevOps practices into your AppSec LifeMatt Tesauro

Bruce Lee once said “Don’t get set into one form, adapt it and build your own, and let it grow, be like water“. AppSec needs to look beyond itself for answers to solving problems since we live in a world of every increasing numbers of apps. Technology and apps have invaded our lives, so how to you lead a security counter-insurgency? One way is to look at the key tenants of DevOps and apply those that make sense to your approach to AppSec. Something has to change as the application landscape is already changing around us.

perlbrew yapcasia 2010Kang-min Liu

This document describes perlbrew, a tool for installing and switching between multiple Perl versions. It allows installing Perls from tarballs or git, and builds them with customizable options. Perlbrew lists installed Perls, allows switching between them, and keeps Perl installations and libraries isolated. It has benefits like easier cleanups and isolated environments for different apps. The tool is actively developed on GitHub with contributions from many.

Matt tesauro Lessons from DevOps: Taking DevOps practices into your AppSec Li...Matt Tesauro

CONFidence 2015: Lessons from DevOps: Taking DevOps practices into your AppSe...PROIDEA

Matt Tesauro presented on applying DevOps practices to application security. He discussed how traditional software development left little time for security testing. DevOps, Agile, and continuous delivery further squeeze testing windows. The solution is automated security testing integrated into software pipelines. Tesauro outlined key features of application security pipelines like iterative improvement, reusable processes, and a focus on automation to optimize security resources. Pipelines improve visibility, consistency, and flow of security work.

Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...AgileNetwork

This document discusses marrying Agile and DevOps approaches to get phenomenal results. It begins with an introduction of the author and their experience. It then poses common questions around when to adopt Agile vs DevOps and how they relate. The document outlines differences between traditional and Agile/DevOps mindsets and practices. It provides examples of lessons learned and challenges overcome during one organization's transformation journey. Finally, it discusses steps to get started with a DevOps approach and lists examples of effective DevOps practices.

Implementation AssistanceOdoo

This document proposes OpenERP implementation assistance services to help a client configure and implement the OpenERP ERP system themselves. The proposal outlines a 6-phase implementation plan including needs analysis, online training, configuration, optional customization and data import, and a 1-year maintenance contract. The client is responsible for designating a project manager, allocating their time, and exporting any required data from existing systems.

Choosing Automation for DevOps & Continuous Delivery in the EnterpriseXebiaLabs

Continuous Delivery Decision pointsKelly Looney

This document discusses continuous delivery decision points and environments. It notes that as DevOps shifts focus from build/deploy automation to continuous delivery, test environments are proliferating and need to be provisioned and managed efficiently. It also emphasizes that collaboration around testing is important, and teams must make strategic decisions about promoting code changes to subsequent stages or iterating further. Maintaining properly designed automated and manual tests is key to making these decisions. Organizational culture and leadership must also support empowering developers and teams to deliver changes incrementally.

Making security-agile matt-tesauroMatt Tesauro

Bringing Open-Source Practices to Your Day JobBen Coe

Nodeconf npm 2011Florent Jaby ヅ

State of the CLI- Kat MarchanNodejsFoundation

Practical Methods for Adopting DevOps - Michael StahnkePuppet

Get lean tutorialMarty Haught

Building an Open Source AppSec PipelineMatt Tesauro

Diving into SngularJSfrancisspor

apidays LIVE New York - Navigating the Sea of Javascript Tools to Discover Sc...apidays

Building a custom cms with djangoYann Malet

Building Open-Source React ComponentsZack Argyle

Building Open-source React ComponentsZack Argyle

Lessons from DevOps: Taking DevOps practices into your AppSec LifeMatt Tesauro

perlbrew yapcasia 2010Kang-min Liu

Matt tesauro Lessons from DevOps: Taking DevOps practices into your AppSec Li...Matt Tesauro

CONFidence 2015: Lessons from DevOps: Taking DevOps practices into your AppSe...PROIDEA

Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...AgileNetwork

Implementation AssistanceOdoo

Choosing Automation for DevOps & Continuous Delivery in the EnterpriseXebiaLabs

Continuous Delivery Decision pointsKelly Looney

Making security-agile matt-tesauroMatt Tesauro

Recently uploaded (20)

Artificial Intelligence (AI) basics.pptxaditichinar

Smart_Storage_Systems_Production_Engineering.pptxrushikeshnavghare94

fluke dealers in bangalore..............Haresh Vaswani

The Fluke 925 is a vane anemometer, a handheld device designed to measure wind speed, air flow (volume), and temperature. It features a separate sensor and display unit, allowing greater flexibility and ease of use in tight or hard-to-reach spaces. The Fluke 925 is particularly suitable for HVAC (heating, ventilation, and air conditioning) maintenance in both residential and commercial buildings, offering a durable and cost-effective solution for routine airflow diagnostics.

Metal alkyne complexes.pptx in chemistrymee23nu

Oil-gas_Unconventional oil and gass_reseviours.pdfM7md3li2

15th International Conference on Computer Science, Engineering and Applicatio...IJCSES Journal

Compiler Design_Lexical Analysis phase.pptxRushaliDeshmukh2

DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...charlesdick1345

IntroSlides-April-BuildWithAI-VertexAI.pdfLuiz Carneiro

Mathematical foundation machine learning.pdfTalhaShahid49

ADVXAI IN MALWARE ANALYSIS FRAMEWORK: BALANCING EXPLAINABILITY WITH SECURITYijscai

With the increased use of Artificial Intelligence (AI) in malware analysis there is also an increased need to understand the decisions models make when identifying malicious artifacts. Explainable AI (XAI) becomes the answer to interpreting the decision-making process that AI malware analysis models use to determine malicious benign samples to gain trust that in a production environment, the system is able to catch malware. With any cyber innovation brings a new set of challenges and literature soon came out about XAI as a new attack vector. Adversarial XAI (AdvXAI) is a relatively new concept but with AI applications in many sectors, it is crucial to quickly respond to the attack surface that it creates. This paper seeks to conceptualize a theoretical framework focused on addressing AdvXAI in malware analysis in an effort to balance explainability with security. Following this framework, designing a machine with an AI malware detection and analysis model will ensure that it can effectively analyze malware, explain how it came to its decision, and be built securely to avoid adversarial attacks and manipulations. The framework focuses on choosing malware datasets to train the model, choosing the AI model, choosing an XAI technique, implementing AdvXAI defensive measures, and continually evaluating the model. This framework will significantly contribute to automated malware detection and XAI efforts allowing for secure systems that are resilient to adversarial attacks.

Machine learning project on employee attrition detection using (2).pptxrajeswari89780

ELectronics Boards & Product Testing_Shiju.pdfShiju Jacob

Compiler Design Unit1 PPT Phases of Compiler.pptxRushaliDeshmukh2

Level 1-Safety.pptx Presentation of Electrical SafetyJoseAlbertoCariasDel

211421893-M-Tech-CIVIL-Structural-Engineering-pdf.pdfinmishra17121973

Smart Storage Solutions.pptx for production engineeringrushikeshnavghare94

DSP and MV the Color image processing.pptHafizAhamed8

railway wheels, descaling after reheating and before forgingJavad Kadkhodapour

Development of MLR, ANN and ANFIS Models for Estimation of PCUs at Different ...Journal of Soft Computing in Civil Engineering

Passenger car unit (PCU) of a vehicle type depends on vehicular characteristics, stream characteristics, roadway characteristics, environmental factors, climate conditions and control conditions. Keeping in view various factors affecting PCU, a model was developed taking a volume to capacity ratio and percentage share of particular vehicle type as independent parameters. A microscopic traffic simulation model VISSIM has been used in present study for generating traffic flow data which some time very difficult to obtain from field survey. A comparison study was carried out with the purpose of verifying when the adaptive neuro-fuzzy inference system (ANFIS), artificial neural network (ANN) and multiple linear regression (MLR) models are appropriate for prediction of PCUs of different vehicle types. From the results observed that ANFIS model estimates were closer to the corresponding simulated PCU values compared to MLR and ANN models. It is concluded that the ANFIS model showed greater potential in predicting PCUs from v/c ratio and proportional share for all type of vehicles whereas MLR and ANN models did not perform well.

Artificial Intelligence (AI) basics.pptxaditichinar

Smart_Storage_Systems_Production_Engineering.pptxrushikeshnavghare94

fluke dealers in bangalore..............Haresh Vaswani

Metal alkyne complexes.pptx in chemistrymee23nu

Oil-gas_Unconventional oil and gass_reseviours.pdfM7md3li2

15th International Conference on Computer Science, Engineering and Applicatio...IJCSES Journal

Compiler Design_Lexical Analysis phase.pptxRushaliDeshmukh2

DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...charlesdick1345

IntroSlides-April-BuildWithAI-VertexAI.pdfLuiz Carneiro

Mathematical foundation machine learning.pdfTalhaShahid49

ADVXAI IN MALWARE ANALYSIS FRAMEWORK: BALANCING EXPLAINABILITY WITH SECURITYijscai

Machine learning project on employee attrition detection using (2).pptxrajeswari89780

ELectronics Boards & Product Testing_Shiju.pdfShiju Jacob

Compiler Design Unit1 PPT Phases of Compiler.pptxRushaliDeshmukh2

Level 1-Safety.pptx Presentation of Electrical SafetyJoseAlbertoCariasDel

211421893-M-Tech-CIVIL-Structural-Engineering-pdf.pdfinmishra17121973

Smart Storage Solutions.pptx for production engineeringrushikeshnavghare94

DSP and MV the Color image processing.pptHafizAhamed8

railway wheels, descaling after reheating and before forgingJavad Kadkhodapour

Development of MLR, ANN and ANFIS Models for Estimation of PCUs at Different ...Journal of Soft Computing in Civil Engineering

open source product management (feat. npm)

1. open source product management with npm @othiym23 / Forrest L Norvell npm, Inc.

2. npm

3. npm is many things • project • company • team • philosophy & ethos • product family

4. npm is many softwares • registry • website • CLI

5. the CLI team

6. me

7. npm CLI team duties • meet npm, Inc.’s business objectives • fix bugs • support current npm users • keep npm moving forward

8. make npm the most useful tool it can be for the most people

9. “useful”

10. pragmatism > rigor

11. simplicity > completeness

12. problems > solutions

13. ($ > !$)

15. • 356 support tickets • 222 bugs • 236 feature requests

16. traditional product management • own the roadmap • sell the strategic vision • mediate between business owners, developers, & other stakeholders

17. say no a lot, but be stubborn about what you say yes to

18. open-source product management • balance competing demands • consensus-seeking • but sometimes you have to say no

19. example: making npm more extensible

20. 1. lifecycle

21. 2. ADD M0AR HO0KZ

22. 3. yay!

23. nope

24. (2. add more commands, like git)

25. npm is not an infinitely extensible miracle pegacorn

26. turn the problem inside out

27. npm as a set of APIs plugged into a CLI

28. LET A THOUSAND PACKAGE MANAGERS BLOOM

29. CAVEATS

30. • looked at a lot of different requests • came up with a global solution for many local problems • try to keep each goal supporting the others

31. npm’s roadmap • scoped packages • multi-stage install / dependency tree realization • npm as API • better Windows support • client-side development support

32. you

33. the npm release process • new release every Thursday • new releases published to npm@next for about a week of burn-in • `npm@latest` for safe production release, `npm@next` if you want to help test the next release

34. supporting npm • the CLI team doesn’t have much time for support • `npm report` will make crowdsourcing that easier, but it’s a ways out • answering questions with the `support` label is ❤️ by me

36. using the npm issue tracker: labels 1. bug, support, feature request 2. next-patch, next-minor, next-major 3. documentation, patch-welcome, and novice

37. using the npm issue tracker: best practices • don’t add your bug to a closed issue • …but please do add specific details that helped you • no such thing as too much information, but gists are useful • use cases are useful, +1s are terrible

38. PATCHES WELCOME • pull requests with tests are landed as quickly as practicable • no patch is too small • …but some patches are too big

39. developing npm • `npm test` while developing • `npm run test-all` before submitting PR • update the docs, plz • people who add tests are my favorite people

40. thanks for listening / thanks for helping / thanks for being you

41. nice people matter

open source product management (feat. npm)

Recommended

More Related Content

What's hot (20)

Similar to open source product management (feat. npm) (20)

Recently uploaded (20)

open source product management (feat. npm)