'When it comes to where the CLI lives or who manages it, that's still a work in progress'
On the phone, Bogensberger insisted he cares about NPM's infrastructure, noting that the company's site reliability engineering team has at least doubled in size. "We're bolstering the team and our process and tooling to make the registry the best it can be," he said. "Over the last six months, we've been able to attract some phenomenal people to the company. We've got seasoned people at every level. The growth of the registry is not slowing down."
Asked about the state of the CLI and claims The Register has heard that the company has been trying to shift oversight of the code to a foundation, Bogensberger said that's been a matter of discussion for some time. The sticking point, we're told, is that NPM Inc wants assurances that the client code will always point people to the npm registry to fetch files.
"When it comes to where the CLI lives or who manages it, that's still a work in progress," said Bogensberger, who stressed that it's important not to create confusion. "If we do the wrong thing, we disrupt build systems around the world. We need to make sure we don't introduce something that can cause confusion."
"The great thing about open source is differing opinions are welcome," he said. "Anybody who's negative about different opinions doesn't get open source."
In open-source companies, however, opinions about work conditions and management may not go over so well. ®