Delivery team
Mission
Enable any Sourcegraph customer or user to trial or run (in production) Sourcegraph in a way that is compatible with their environment, supports their level of technical expertise, and allows them to easily access the value that our product provides. Make it as easy as possible to access this value, and to maintain it going forwards by easily staying up to date with Sourcegraph’s latest developments.
Members
- Beyang Liu, Product Manager
- Beyang Liu, CTO, co-founder, Board of Directors
- Stephen Gutekanst, Internal Contributor / Software Engineer
- Justin Dorfman, Open Source Program Manager
- James Cotter, Software Engineer
For more detailed information on the Delivery team members, check out our README page which expands on our profile.
Strategy
Find out about our team’s vision, guiding principles, current status quo, and strategic plans
Responsibilities
- Deployments methods and configuration
- Customer deployments and docs
- Org-wide areas of ownership
Sourcegraph releasesreleases are owned by the Release Guild and the Delivery provides support to the Release Guild.
Contact
- #delivery channel, or
@delivery-support
in Slack. Please follow our support guidelines below. - team/delivery label and @sourcegraph/delivery team on GitHub.
Support
If in doubt about the process, please ask in #delivery. Delivery teammates shold consult our support-rotation guide to handle inquiries.
Requesting our support
Feel free to direct simple questions to us in #delivery in Slack. As a rule of thumb, anything that is not documented in our handbook or docsite usually indicates it is not a simple question (e.g. feature requests) and should follow our support request guidelines below.
- This channel is regularly checked and well-monitored
- So please do NOT directly message or CC an engineer—this is to try and protect their focus
- Instead, if it’s urgent, please @ either the PM or the EM in the question in the channel and we’ll ensure it gets the best response
Support request guidelines
Support requests related to our areas of ownership should follow this process:
- Make sure there is an issue—if there’s not, please create one and include:
- A short description of the ask
- A more detailed explanation of the background, the context and the challenge that needs solving
- Any guidance related to the impact this is having
- Any extra information that could help us solve or prioritize this
- Ensure lable
team/delivery
is added to the issue - Ensure that the issue is added to the ”Delivery” board in GitHub
- Anything without a status is checked and triaged weekly - so this is enough for feature requests or less urgent issues
- If you think this needs eyes 👀 sooner
Principles
We inherit Sourcegraph’s engineering principles and practices.
We also have a set of guiding principles that help inform our decision making about our stretegic and prioritization choices.