Extensibility team

The extensibility team owns our code host and third-party integrations (including our browser extension) and our Sourcegraph extensions.

Members

Mission

Our mission is to bring the value of Sourcegraph to everywhere you work with code and to bring the value of other developer tools into Sourcegraph.

Vision

Sourcegraph powers your first stop for any information about your code, for any tool or website you use.

  1. Build a healthy ecosystem of Sourcegraph extensions, built by developers everywhere, who want to bring the power of existing developer tools they love into our platform.
  2. Build new paths to get value from Sourcegraph on other websites and IDEs.
  3. All of Sourcegraph’s most powerful features are easily available on most any code host while using any browser thanks to native integrations and browser extensions.

Responsibilities

The extensibility team has many ownership areas, but not all of them are under active development at the same time. We nonetheless list them all here as a source of truth for deciding if an issue, feedback, or comment is relevant to the extensibility team. You can find our current priorities in our goals page.

  1. Sourcegraph extensions
    • Providing a Sourcegraph extension API that enables developers to bring data from their favorite developer tools into their Sourcegraph workflow.
    • Build and maintain useful Sourcegraph extensions.(Sourcegraph-maintained extensions).
    • Documentation and tutorials that enable third-party developers to create actively useful extensions.
    • Building and maintaining the extensions registry, discovery paths, and extensions developer toolsets, to create an ecosystem around Sourcegraph extensions.
  2. Code host integrations
    • Add native support for Sourcegraph in code hosts (for example: GitLab native integration) when possible, so all users of a Sourcegraph instance can get features like code intelligence on their code host without individual setup.
  3. Browser extensions
    • Develop and maintain browser extensions that surface code intelligence and other Sourcegraph features on code hosts (for example: Github).
  4. IDE and other third-party code view integrations
    • Develop and maintain IDE integrations that bring Sourcegraph functionality right to your IDE
    • Explore and develop features for other popular code-view websites like https://pkg.go.dev/ and messaging platforms like Slack

Contact

Goals

Goals

Growth plan

We are not planning on growing the Extensibility team further in 2021.

Tech stack

We use a modern, flexible tech stack. Here are some of the technologies we use to deliver on our goals:

Processes

Backlog

We use backlogs for tracking bugs, small features, and unplanned work. You can find the extensibility backlog on Github. Please note that we don’t use the backlog for tracking work that is expressly planned in our roadmap.

To add an issue, tag it team/extensibility to notify the Extensibility team and put it in the “to triage” column of the board. Unless you’re directly asked, only extensibility team members should move issues out of the “to triage” column on the board. A team member will confirm the issue is team-related and then move it to the appropriate column.

Tracking Issues

The team makes use of tracking issues for tracking progress on the implementation of new features. The teammates should ensure that a tracking issue is created when starting work on features that are expected to take longer than a single iteration to deliver.

Product Feedback

Specific product feedback about well-defined, small features can be found directly in the backlog boards. More general product feedback that applies to larger features or that needs more research and planning to be actionable is kept in Productboard

Iterations

The team creates a focused plan each iteration, by agreeing on an appropriately small set of iteration goals.

We plan our work in 2-week iterations.

The individual tasks and progress of the current iteration can be found as GitHub issues in our GitHub project board. At the beginning of an iteration, we fill the “To do” column with all issues we want to accomplish by the end of the iteration and make sure they have estimates and assignees. Each issue should be as small as possible. Over the course of the iteration, we strive to close issues with small, iterative pull requests that we review and merge timely (generally a day). By the end of an iteration, all issues should be in the “Done” column and the board gets emptied.

Iteration planning

To ensure the team can be productive right from the start of an iteration we start planning for our next iteration as soon as a new iteration starts.

  1. First week of the iteration
    1. The EM & PM will add tasks that should be considered for the iteration throughout the week.
      1. Tasks are collected under the “Prioritized List of Issues” column of our extensibility backlog.
      2. The PM will focus on adding items that are aligned with our roadmap so that we keep working towards our goals
      3. The EM will focus on adding bugs and tech debt issues to ensure we maintain a high quality code base and product.
    2. The EM & PM work on getting all tasks to a “Ready for dev” status.
      1. A “Ready for dev” status means that all the necessary information has been captured or prepared so that the engineer taking up the issue can essentially start working on it immediately.
        1. This does not involve figuring out implementation detail, as we do not tell engineers how to execute a task, but rather tell them the problem and make the requirements clear, and then ask them to figure out the best way to implement the solution.
        2. We don’t block on design dependencies for a task, but try to identify any dependency early on and communicate this requirement to the product designer.
    3. The PM identifies and communicates design input needed from the Product Designer and works to prioritize it with them.
  2. Second week of the iteration
    1. By Wednesday, the EM and PM should have ensured that:
      1. All planned work has refined issues in GitHub and are added to the ‘On Deck’ column on the backlog board
      2. All issues are in a “Ready for dev” state
      3. All issues have effort estimates and have been prioritized
      4. The team’s available capacity for the next iteration is known.
        1. A teammate’s capacity is calculated at 80% of the iteration days - vacation days.
    2. On Wednesday, the teammates are invited to review the planned iteration scope and to provide feedback.
    3. On Thursday, the EM and PM will have a sync call to finalize the next iteration’s scope. In determining the iteration scope, they will factor in:
      1. The priority
      2. The effort estimate
      3. The available capacity of the team
      4. Any leftover issues that won’t be complete from the prior iteration, and whether those issues should still be prioritized next iteration or moved to a backlog category.
      5. Feedback from the teammates
    4. The PM will prepare the current iteration project in GitHub with the relevant issues.

Progress monitoring

We monitor the progress of the work in an iteration in the following ways:

  1. Iteration: The overall iteration progress is monitored through a GitHub project board (See Iterations.)
  2. Tracking issue: If a feature is made up out of multiple issue, we use a tracking issue to keep track of its progress. (See Tracking issues.)
  3. Pull request: The implementation of a feature is tracked through a checklist in the description of the pull request. (See PR template.)

Updates

We do regular updates to communicate our progress to members of the team and to external stakeholders.

Retrospectives

After each iteration, we hold a sync retrospective meeting to reflect on the past iteration. We use this meeting to:

  • Review the previous retro’s action items to ensure we hold teammates accountable for actioning them
  • We give Shoutouts! to teammates to show appreciation for something they did that we appreciated.
  • Discuss things that went well in the past iteration and that we should do more of / invest more into it.
  • We discuss the things that could have gone better and what we can learn from it to improve.
  • We talk about processes that we should revisit/refine/propose to improve our efficiency?

We capture and assign actions to teammates to action. Teammates should consider actions coming out of the retrospective as a very high priority.

Teammates contribute to the retrospective asynchronously during the iteration by adding their thoughts to our retrospective document. Teammates are highly encouraged to comment on points raised before the sync meeting in the document.

We rotate who leads the retrospective to allow all teammates an opportunity to lead the session. Teammates can find the rotation schedule at the top of the retrospective document.

Code reviews

The team follow’s the default code review guidelines with the following addition:

  1. If the author would like any of the requested reviewers to merge the PR after approval they add the label merge-on-any-approve
  2. If the author would like their PR to be merged once all of the requested reviewers have approved it they add the label merge-on-all-approve

Pair programming

We use pair programming extensively. We’re huge believers in pair programming in remote work contexts, so we aim to pair for 15 hours a week.

Weekly Sync

The team holds weekly syncs.

The meeting notes of team syncs can be found in this doc.

Before team syncs, teammates and stakeholders should write down under “Agenda” in the meeting notes document anything that they’d like to bring up for discussion with the whole team.