Mission

Our mission is to maintain and evolve the methods by which code is pulled into Sourcegraph from code hosts, in a way that supports all required functionality while maximizing performance, reliability, and ease of use.

We also have temporary custody of Authentication, with the aspiration being to split the team to give auth a dedicated team to own it. As a result, unless otherwise specified, the rest of this page relates to Repo Management and code host work.

Vision

Guiding principles

• We aim to provide consistent support for the code hosts we support
• We cannot cater to every customer’s wants and needs, and trying to would undermine our ability to serve all of Sourcegraph’s current and future customers
• As a result, we prioritize work that will best support that majority (current and future), sometimes compromising what we can offer to individual customers whose needs are not aligned with our strategic decisions
• Our work underpins almost every feature Sourcegraph offers, and so our work is of value to all users of Sourcegraph
• More directly our work is utilized by any user setting up code host connections - this can be any kind of Sourcegraph user, ranging from IC developers to central administrators (often called “site admins”)
• Many customers will utilize more than one code management system and so oftentimes have more than one code host to set Sourcegraph up with
• Customers do not want to have to take code host differences into account, so we aim to make the setup, management, and capabilities of our code host support consistent, despite the technical differences between them
• We aim to ensure our setup of code hosts is simple enough for any engineer but also ensure that we provide documentation that is sufficiently clear that any user could follow it to set up code hosts
• Many customers have a large number of repos and a number of large repos, and so performance, scalability, reliability, and resilience are as important as the ease of setup
• We also serve the rest of the Sourcegraph engineering team, who use the code host connections and replicated code to provide their own functionality
• As a result, we aim to make sure that the support of code hosts is as consistent as the different code hosts allow in terms of facilitating the functionality Sourcegraph offers

Top customer, support, sales and marketing issues

⚠️ Please see below in Strategy and plans for more information on which problems are actually in scope of the team.

Note that these are order by approximate known revenue impacted - but that the figures are likely not to be representive of the total value, and so the order in which these get address may not correlate with the order here. Click on the product gap link to find out the up to date impacted revenue amount.

Goals

TODO

🎯 Goal 1

🎯 Goal 2

🎯 Goal 3

Themes

TODO

What’s next and why

More detailed plans related back to the themes and goals. If your time frame covers more than a quarter, it would be valuable to give some indication of time within the plans in this section, to help others appreciate the likely ETA of value.

ℹ️ The plans for this team are currently being worked out and the following summarizes the current plans.

Note that the time periods are rolling time periods and the plans here are reviewed and updated monthly.

What we’re not working on

What are we explicitly not working on? Are there frequent requests from customers or other teams we are choosing not to take on? Making that explicit makes other teams understand the strategy and reduces back and forth.
If there is a time component (e.g. “We’re not working on this this Q but likely to pick it up next Q”), call it out.

TODO