Why TypeScript moved to GitHub in 2014

Key Concepts

• Open Source Engagement: The shift from a pseudo-open source model to full, active participation in the open-source community.
• Pull Requests: A method for contributing code changes to a project, central to modern open-source development.
• Trustworthiness in Open Source: The importance of reputation and community trust for successful open-source projects.
• GitHub as a Hub: The significance of GitHub as the primary platform for open-source development and community interaction.
• Internal vs. External Processes: The distinction between development workflows used internally within a company versus those used with external contributors.

Early "Open Source" Approach & Its Limitations

Initially, Microsoft’s approach to open source was described as a limited form of openness. Source code was made available in a repository, and users could file issues. However, this process lacked genuine engagement. The team would essentially “lop it over the fence” – release the code, then retrieve the reported issues and import them into an internal bug tracker. This meant that all subsequent development and bug fixing occurred within Microsoft’s internal processes, effectively isolating external contributors. The speaker humorously suggests this lack of true engagement contributed to the project’s initial lack of traction, stating, “maybe that’s why it was crickets.” [laughter]

The Trust Factor & The Move to GitHub

A significant factor hindering early success was Microsoft’s perceived lack of trustworthiness within the open-source community. The speaker explicitly states, “our trustworthiness as and ours being Microsoft's trustworthiness in open source at that time was not particularly high.” Recognizing this, and acknowledging that “you got to go where the action is,” Microsoft made a strategic decision in 2014 to migrate the project’s repository to GitHub.

Embracing Full Open Development

The move to GitHub wasn’t merely a change of hosting platform; it represented a fundamental shift in development methodology. Microsoft committed to a fully open development process, ensuring that all development, including feature additions, was conducted through pull requests. A pull request is a mechanism where contributors submit changes to the codebase, which are then reviewed and integrated by the project maintainers. Issues were also tracked openly on GitHub, fostering transparency and collaboration. The speaker emphasizes that “our process was no different from external contributors.”

Results & Project Growth

This complete engagement with the open-source community proved transformative. The speaker directly links the change in approach to the project’s subsequent success, stating, “it wasn’t until then that the project actually started taking off and that people started showing an…” (the sentence is incomplete in the transcript, but the implication is increased participation and growth). The adoption of standard open-source practices, facilitated by GitHub, built trust and encouraged wider community involvement.

Logical Connections

The transcript clearly outlines a cause-and-effect relationship. Initial limited open-source attempts failed due to a lack of genuine engagement and a pre-existing trust deficit. Addressing these issues by moving to GitHub and adopting a fully transparent, pull-request-based development process directly resulted in increased community participation and project growth.

Synthesis

The core takeaway is that simply releasing source code is insufficient for successful open-source engagement. True success requires building trust within the community, actively participating in open development workflows (specifically utilizing pull requests), and embracing transparency. Microsoft’s experience demonstrates the importance of aligning internal processes with established open-source practices and choosing platforms like GitHub that facilitate community interaction.