-
Notifications
You must be signed in to change notification settings - Fork 172
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
distribution: switch to GitHub updates on Friday & clarify what updates are for #1066
Conversation
@@ -118,33 +118,82 @@ come prepared to talk about the following: | |||
|
|||
## Weekly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the docs!
Co-authored-by: Robert Lin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for documenting all this (and for accommodating time zones differences!)
Co-authored-by: Robert Lin <[email protected]>
Co-authored-by: Robert Lin <[email protected]>
Prior to this change, I have been summarizing what our team did each week (example) so that @nicksnyder and @christinaforney have insight.
As discussed in our weekly team sync, this PR switches the Slack update we would usually post on Friday to posting an update on our GitHub tracking issue instead (which is in line with what other teams at Sourcegraph do).
Additionally, this attempts to clarify what exactly we aim to discuss in our weekly sync vs. our async status updates.
@bobheadxi @ggilmore @uwedeportivo @davejrt (and @daxmc99 if you like) please all review and approve / leave feedback, so I know you've seen the changes.