-
“Having everyone together on the GitHub platform is a great advantage for innersource.”
-
"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."
-
“It’s more efficient for the developers, because you eliminate the need to learn a whole new set of tools if you move from one project or team to another.”
-
“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.”
-
“By actively participating in the open source community, we’re able to tap into millions of users offering immediate feedback and improvements for our software.”
-
“If an issue is found, we’re informed immediately. We go over anything the tool has highlighted, and we make sure that it’s resolved before releasing a stable release.”
-
“Actions updates the pull request checklist the moment the check fails or succeeds. You’re able to get something out the door quickly without having to wait five or 10 minutes for an external service to update the pull request check so you can merge.”
-
“It’s right there, and it’s completely integrated. You don’t have to go traipsing off to some other tool and then sign into another thing. When I need to have a look at the status of our job and log sets, it’s right there.”
-
“GitHub, in terms of cost and performance, is head and shoulders above everything else.”
-
“During the process, we’re available for any issues or questions. We want to ensure the team is only publishing source code that everyone is behind—open source is about discovering what you need but also giving something back.”
-
"We chose GitHub not only because it was more affordable but because we’re able to contribute to the greater open source community."