The search core team owns all parts of Sourcegraph that map an interpreted search query to a set of results:
- Indexed and unindexed search (Zoekt & Searcher)
- Diff/commit search
- Result ranking
- Open source indexing, current at over 2.5M repos!
To learn more about our goals, see the Search Core strategy page.
We seek to follow a set of guiding principles when welcoming new teammates and working as a team.
The Search Core team has a customer support rotation: each week, one team member will be responsible for fielding questions and requests from Customer Engineering and Customer Support.
The engineer on support rotation can be contacted using the Slack alias
The support rotation can be viewed on OpsGenie: search core schedule.
Should an engineer be unable to fulfill support responsibilities for any reason (for example, due to upcoming time off), they should swap with a teammate.
We track support issues from customers on this board
- The search core team plans its work continuously (we don’t do sprints/iterations).
- Supporting existing customers is critical to our success and can be prioritized ahead of roadmap work.
- Our OKR and status updates are tracked using GitHub under the Code Graph tab.
- The teams holds syncs twice weekly (Mon, Thu).
- Before team syncs, teammates add their status and plans to the team sync meeting notes.
- The team discusses the updates live during the sync.
- Updates should be in prose and communicate progress made and pain points.
We use a backlog project board to capture work items we’ve identified.
- We have a retrospective every two weeks, on Monday. This is a time for us to look back and discuss progress and consider changes to process.
- Our action plans and learnings are captured in a document.
- If we are going to have a sync retrospective, we use a Jamboard to capture everyone’s thoughts. The theme for the Jamboard can rotate.
- If we are going to have an async retrospective, we use the Google Doc above to capture our retro.
Our team is geographically and timezone diverse. The handbook has a large page dedicated to it and it is worth reading. This section is intended to augment the handbook. Since our team works across many timezones, setting boundaries for notifications becomes really important to protect your free time. You are empowered to do this and here are a couple of suggestions:
- Set your working hours in Google. This makes it easier for your teammates to see when you are normally online.
- Set your notification schedule in Slack.
- When you need focus time, enable Mac Focus time and/or set Slack to Do not Disturb.
- Google Calendar supports focus time. Block out time on your calendar in 2, 4 or 6 hour intervals where you only work on a particular task. Enable your Focus time (F6 key on Mac keyboard) and set Slack to DND.
- Enable Google Calendar in Slack to sync up your Slack status with your Google Calendar.
- Setup email filters for GitHub notifications.
- Mute conversations in Slack to reduce notifications or leave the channel.
- The Slack notification pane on the left side has an option to only show channels that are unread. This hides the channels with no new content and speeds up catching up in Slack.
- If things like Google Mail and Calendar are not cutting it for you, try other tools. Some people really like using Spark for email and Fantastical for their calendar. To do list tools like Things and ToDoist are popular and also integration tools like Zapier can be really helpful. Ask in Slack, you will get suggestions.
- For support rotation picking up incidental work. Tasks in support backlog to capture this, more intentional work around support and papercuts versus trying to work normally and getting interrupted.
- Focus on more feature flag driven development to simplify on-premise changes and speed up MTTR for Cloud.
Most of the work related to releasing our code fits the general description of Engineering processes.
However, there is an important thing to mention. Since Zoekt lives in a separate repo, we need to periodically pull changes from the Zoekt repo to the main Sourcegraph repo. This can be done either manually by altering the go.mod and go.sum files in the main repo, or by merging the corresponding PR opened by the bot.
This is good enough to see our changes in an upcoming release, but if you want to see them immediately at Sourcegraph Cloud, another step is needed. Sourcegraph Cloud is continuously deployed from the main repo code, and we alter some parts of it by providing an intentionally wrong version number in the deployment script. The reason is we do not depend on the rollout schedule this way; each update of the version number triggers a rollout. For information on how to bump the Zoekt images and deploy the newer versions, refer to Continuous Deployment Process, Manually deploying a service to sourcegraph.com, and Our update script.
On Boarding - visit the page
- Learning Go
- Architecture diagram
- Sourcegraph Documentation
- Super helpful intro video
- How gitserver works
- Zoekt Bedtime Reading:
Our private resources are available in the Google doc