Permalink
Switch branches/tags
release-1.4.3-beta2 release-1.4.3-beta1 release-1.4.3-beta0 release-1.4.2 release-1.4.2-beta0 release-1.4.1 release-1.4.1-beta1 release-1.4.1-beta0 release-1.4.0 release-1.4.0-beta3 release-1.4.0-beta2 release-1.4.0-beta1 release-1.4.0-beta0 release-1.3.5 release-1.3.5-beta1 release-1.3.5-beta0 release-1.3.4 release-1.3.4-beta1 release-1.3.4-beta0 release-1.3.3 release-1.3.3-beta1 release-1.3.2 release-1.3.2-beta1 release-1.3.1 release-1.3.1-beta1 release-1.3.1-beta0 release-1.3.0 release-1.3.0-beta7 release-1.3.0-beta6 release-1.3.0-beta5 release-1.3.0-beta4 release-1.3.0-beta3 release-1.3.0-beta2 release-1.3.0-beta1 release-1.2.7-beta0 release-1.2.6 release-1.2.6-beta0 release-1.2.5 release-1.2.4 release-1.2.4-beta5 release-1.2.4-beta4 release-1.2.4-beta3 release-1.2.4-beta2 release-1.2.4-beta1 release-1.2.3 release-1.2.3-beta1 release-1.2.2 release-1.2.2-beta1 release-1.2.1 release-1.2.1-beta1 release-1.2.1-beta0 release-1.2.0 release-1.1.2-beta7 release-1.1.2-beta6 release-1.1.2-beta5 release-1.1.2-beta4 release-1.1.2-beta3 release-1.1.2-beta2 release-1.1.2-beta1 release-1.1.1 release-1.1.1-beta4 release-1.1.1-beta3 release-1.1.1-beta2 release-1.1.1-beta1 release-1.1.0 release-1.1.0-beta3 release-1.1.0-beta2 release-1.1.0-beta1 release-1.0.14-beta5 release-1.0.14-beta4 release-1.0.14-beta3 release-1.0.14-beta2 release-1.0.14-beta1 release-1.0.13 release-1.0.13-beta1 release-1.0.12 release-1.0.12-beta1 release-1.0.12-beta0 release-1.0.11 release-1.0.11-beta0 release-1.0.10 release-1.0.10-beta3 release-1.0.10-beta2 release-1.0.10-beta1 release-1.0.10-beta0 release-1.0.9 release-1.0.9-beta1 release-1.0.9-beta0 release-1.0.8 release-1.0.8-beta0 release-1.0.7 release-1.0.7-beta0 release-1.0.6 release-1.0.5 release-1.0.5-beta1 release-1.0.5-beta0 release-1.0.4 release-1.0.4-beta1 release-1.0.4-beta0 release-1.0.3
Nothing to show
Find file Copy path
305a18d Sep 29, 2018
2 contributors

Users who have contributed to this file

@billygriffin @myqpalzm147
56 lines (42 sloc) 3.66 KB

What is GitHub Desktop and who is it for?

Purpose

As we triage issues, evaluate pull requests, and discuss new features, the GitHub Desktop team is making decisions based on our vision for the GitHub Desktop product. The purpose of this document is to transparently share our collective view of what GitHub Desktop is and who we’re optimizing for when making decisions. Our goal is to be able to point back to this document to ensure there are fewer surprises and that we’re consistent in our product decisions. This will likely evolve over time as we continue to learn more about our users and the problem space.

1. GitHub Desktop reduces frustration and makes Git and GitHub workflows* more approachable.

Our goal with GitHub Desktop is to remove frustration, awkward interactions, and “oh no” moments for as many people as possible. We aim to make common workflows* (defined at the end of this document) so simple that beginner and experienced developers alike are productive in working with Git and GitHub. Git can be intimidating, and we want GitHub Desktop to make interactions with Git easier and more approachable. GitHub Desktop is not a replacement for the functionality of Git, but a tool to enable you and your team to be more productive.

2. GitHub Desktop extends GitHub to your local environment.

GitHub Desktop is built and maintained by a team at GitHub and a group of amazing community contributors as an open source application. It is intended primarily to extend the features of GitHub, not to be an agnostic Git client or replicate the feature set of github.com. While we support very basic functionality that will allow the app to function with other hosting providers, we prioritize work that allows the end-to-end GitHub and GitHub Enterprise experience to shine and takes advantage of the fact that we can closely integrate with GitHub features.

3. GitHub Desktop prioritizes workflows for beginners and collaborative teams.

We want to create an inclusive and approachable way for developers to turn ideas into reality, and we see GitHub Desktop as critical in reducing the intimidation of working with Git on the command line. Users of all experience levels will continue to benefit from GitHub Desktop’s features but when we have to choose between workflows for advanced Git users and workflows for beginner Git users, we prioritize beginners. Additionally, we think it’s foundational to support solo development, but our unique value comes from combining the power of GitHub with the convenience of working locally so that you can collaborate with your team easily. This also means GitHub Desktop will likely not support workflows that are unique to your team, against documented best practice, or different from the vast majority of developers.

4. GitHub Desktop has a variety of people using it, but our core users are software developers.

GitHub has millions of possible use cases and we believe that nearly every industry should be using Git. We support its versatility, but when we have to make choices about whose workflows to prioritize, we prioritize those for software developers.

5. GitHub Desktop is a tool that enables you to learn while you get things done

GitHub Desktop should be a helpful tool for beginner developers, but it is not explicitly a teaching tool. It is fundamentally to help you get your work done faster and more effectively, in a way that is consistent with and encourages best practices.

    

*We define a workflow as a path that users take toward achieving a particular goal. An example is a “merge” workflow, where the goal is to bring work together that was done in different places.