Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document and update eng team structure and hiring plan #1026

Merged
merged 7 commits into from
Jun 4, 2020
Merged

Conversation

nicksnyder
Copy link
Contributor

@nicksnyder nicksnyder commented Jun 3, 2020

This PR bundles a few changes:

  1. Document who is on what team. This serves as our org chart. We can discuss re-orgs via PR in the future 🙃
  2. Document our hiring needs for each team (instead of various Google Docs here and there).
  3. Update our team structure to reflect that we are orienting work around Sourcegraph Cloud. You should read this as "core services now owns a superset of what they owned before" and the hiring plan is designed to reflect that.
  4. Remove philosophical documentation around how our team is organized because (1) we decided to have engineering managers manage cross-functional engineers on a single mission, and (2) I think it is more effective to just document where we are today (and then evolve that over time).

TODO

  • Update Slack channels, GitHub groups, GitHub labels, CODEOWNERS, etc. for Core services -> cloud change.

@nicksnyder nicksnyder requested a review from a team as a code owner June 3, 2020 03:10
@nicksnyder nicksnyder requested review from a team June 3, 2020 03:10
handbook/engineering/cloud/index.md Show resolved Hide resolved
Co-authored-by: Ryan Slade <ryanslade@gmail.com>
Co-authored-by: Adam Harvey <aharvey@sourcegraph.com>
@tsenart
Copy link
Contributor

tsenart commented Jun 4, 2020

@nicksnyder: Anything left to do here?

@nicksnyder
Copy link
Contributor Author

@tsenart I renamed things in Slack, GitHub and CODEOWNERS to the best of my ability. If you see anything I missed, please take care of it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants