Sourcebot Bug/FR Policy

No repository file, test, or entry point is named. Treat this as a policy reference rather than a defined implementation task; confirm the relevant documentation location and a specific documentation change before starting.

Hey everyone!

We care deeply about the feedback you all provide to help make Sourcebot the best dev tool possible. Responding to your bug and FR issues are a core part of this, so we wanted to create this policy to outline our commitments to responding to these requests.

We hope that this policy is fair and makes sense. If it’s not, please let us know how we can do better by replying to this issue.

Bugs

We want Sourcebot to be a high quality dev tool, so we’re committing to a zero-bug policy. As a result, we’re setting the following SLAs:

• New bugs will be triaged within 8 hours. Triaging a bug means assigning an owner and setting the priority.
• High priority bugs will be resolved within 2 days and low priority bugs within 7 days.
• If a bug is too marginal to address the bug will be closed as “not planned”. Please feel free to reopen the bug with additional details if you don’t agree with our decision.
• If resolving a bug is blocked on the user providing additional information, and they don’t do so within the SLA, the bug will be closed as “not planned”. The bug may be reopened if additional details are provided, in which case the SLA is reset.

Feature Request

Feature requests (FRs) are a core part of how you all can make Sourcebot a better dev tool for everyone. As opposed to bugs, we don’t have strict SLAs for FRs. We review FRs every week and commit to the top ones we can fit in our next engineering sprint.

If you really want an FR to be shipped, please make sure to react to it! That helps us see which FRs are the most requested.

General Inquiry

This could be either a GitHub issue, email, or Slack message that is a general question about the product or docs.

Ideally, 99% of these questions should be answered by our docs. Please check there before submitting a question. We will likely just point you to our docs when answering the question.

In the rare case where our docs don’t answer your question, we will reply within 24 hours and update our docs to include this information for the next user.