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

Go team quiet week: issue tracker responses will be delayed #48615

Closed
rsc opened this issue Sep 24, 2021 · 2 comments
Closed

Go team quiet week: issue tracker responses will be delayed #48615

rsc opened this issue Sep 24, 2021 · 2 comments

Comments

@rsc
Copy link
Contributor

@rsc rsc commented Sep 24, 2021

The issue tracker will be quiet from September 24 to October 4, to let Go team members and contributors disconnect and either recharge for a bit or do focused, deep work.

Here at Google, we have been encouraging people to make sure to take time off during this incredibly stressful year and a half. We’ve observed that one problem with taking a week or two off is that various discussions, meetings, golang-dev@ threads and issues happen while we are away, creating a backlog to work through on return. And even if you’re not taking time off, keeping up with this stream of interruptions can make it difficult to focus on individual work. I’m sure you’ve all seen this in your own jobs.

We have established regular "quiet weeks", once per quarter, with as few interruptions as possible and, for people taking time off, as little to catch up on as possible. The goals for a quiet week are:

  1. Create time for people to disconnect and take a real break, without feeling like they will need to catch up on what they missed when they return.

  2. Create time for people who keep working to do deep work, without all the usual interruptions like meetings and online discussions.

The week (plus weekends) starting Friday, September 24 and ending Monday, October 4 is one of our quiet weeks. We’ve cancelled all our meetings for this week and committed to not having team-wide email or chat discussions either. The same applies to public Go conversations that we are typically part of: for this week, we will not be participating in golang-dev@ nor non-trivial GitHub issue tracker conversations (like proposals or anything trying to arrive at a decision).

We will also be disconnecting as much as possible during the quiet week from other community forums like Gopher Slack, r/golang, and golang-nuts@. The conversations there are mostly not driven by the Go team, so they won’t be as affected, but just know that we won’t be trying to keep up with those either.

When we return on October 4, we will pick up where we left off.

– Russ Cox, for the Go team

@dougmellon
Copy link

@dougmellon dougmellon commented Sep 24, 2021

Thank you to everyone who has contributed. Enjoy the time - well deserved.

@rsc
Copy link
Contributor Author

@rsc rsc commented Oct 4, 2021

Welcome back everyone!

@rsc rsc closed this Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants