305 GitHub Testimonials

"When you open source a project it encourages conversations and idea sharing that will help let the daylight in and spur innovation."

“In my entire career, I’ve never had technical support as good as GitHub."

“In the past, the feedback loop was longer. Eventually, it might trickle down from Jira and someone might pick it up.”

“It’s more than just source code control."

“We’re not just consuming, but also actively contributing back to the open source communities that we come from.”

“We’re getting developers from across the industry, different perspectives, diverse perspectives. We love to see the growth of developers. It’s social, and we’re a social company.”

“It feels like it’s been a community from the start and that’s the way Meta is as well.”

“We want to make sure that developers using the projects are getting the resources, documentation, and tutorials that they need to actually do the work successfully.”

“We want to make sure that people at Meta who are responsible for maintaining these projects can see the data and information they need to keep projects going.”

“We were able to build a tool that integrates with the API, and it’s now used by a majority of developers in PyTorch when they’re developing these multi-step changes on the project.”

"Instead of requesting changes in an email, we can open a pull request on GitHub. There are some products in Deutsche Börse where this practice has reduced email volume by half."

"We are already seeing our early community open source their own code to encourage growth in the group and have fun with people building on top of their code, Lynda said. For example, one Jibo developer produced an If This, Then That (IFTTT) capability for Jibo and shared the project. Another developer built upon that, creating a home automation capability for Jibo, which allows our little guy to turn on lights, televisions, and more. Of course, GitHub is at the center of this effort."

"As we got to know GitHub better, we began to develop process around the tool, and became more rigorous about release drafts, pull request labels, and milestones. As our engineering organization grew, we relied more heavily on teams and roles to control the flow of features."

“Teams share their work with the larger developer community on GitHub, whether it’s samples, or small projects, or SDKs.”

“We want to collaborate with other companies and individuals to bring transparency and compliance to open source licensing. And we’d love to make sure that any information we find goes back upstream. If a project with an MIT license has GPL license code, for example, we’d like to let the maintainers know, so they can update their license information if they choose to.”