The Web org owns and maintains several areas of the product that is taken care of by the following teams:
- Frontend platform: the maintenance and expansion of the Sourcegraph web application. We also define and maintain the standards and tooling for how we do web development at Sourcegraph.
- Extensibility: our code host and third-party integrations (including our browser extension) and our Sourcegraph extensions.
- Code insights: empowering data-driven decisions in engineering organizations.
- API docs: making Sourcegraph the standard developer reference and code search for the open-source universe.
As of March 2021, the Web org is made up of multiple teams, and some members who work across multiple teams:
- Jean du Plessis (Director of Engineering)
- Frontend platform
- Alicja Suska (Product Designer)
- Patrick Dubroy (Engineering Manager)
- Tom Ross
- Felipe Janer
- Valery Bugakov (moves to Code Insights in FQ2)
- Extensibility
- Joel Kwartler (Product Manager) is the acting PM for this team until we can hire a dedicated PM for it (apply here). Once that happens, Joel will focus entirely on code insights.
- Alicja Suska (Product Designer)
- Jean du Plessis is the acting Engineering Manager for this team
- Code Insights
- Joel Kwartler (Product Manager)
- Alicja Suska (Product Designer)
- Felix Becker (Engineering Manager)
- V. K. starting 2021-03-22
- FQ1 backend engineer
- Valery Bugakov (joins from Frontend Platform in FQ2)
- API docs
- Jean du Plessis is the acting Engineering Manager for this workstream
- Frontend platform
Updated 2020-03-08
The strategy is currently a work in progress and can be viewed here: Web Org FY22 Strategy
(Only accessible to Sourcegraph teammates until finalized.)
Each team is afforded the freedom to operate as best they see fit to achieve their goals.
The following processes apply to all teams in the Web org.
We recognize that frequent, open communication is key to the success of every team, especially in an all-remote environment. We default to asynchronous communication in Slack and GitHub issues over other mediums (video calls, emails, etc) as we are respectful of our teammates' time.
In addition to team specific channels, we communicate in the following org-wide channels in Slack:
#web-org-teams: Our daily standups (facilited through Geekbot) go into this channel as well as all non-work related commmunication. Random conversations, banter, jokes etc. are all welcome here.
#web-org-onboarding: This channel is dedicated to questions or thoughts that new teammates have while they onboard. It's a safe space to simply think out load and the goal is to identify things that we can improve and things we should make more clear in the handbook.
#web-org-leadership: This channel is for the Engineering Managers, Product Managers and Product Designers to discuss higher-level matters impacting the whole org.
We have a shared Web Events calendar where the Web org teams can add all their team specific events so everyone can easily see the events.
Collaborating across timezones requires regular communication to keep each other updated on our progress, and coordinate work handoff if needed. We also use this opportunity to build camaraderie between team members by sharing some non-work related aspects of our lives with each other.
We use Geekbot to facilitate all this and these updates are purely for coordination within the team (as opposed to for external stakeholders). At the start of each working day, Geekbot will ask each teammate a set of questions and the responses will be posted in the [#web-org-teams] Slack channel.
All teammates are expected to be part of this channel, and should read the updates, to learn what your teammates have been working on, and check if they need your help.
Each Engineering Manager of the teams in the org is responsible for sending out a status update by the Monday following the team's retrospective.