-
Notifications
You must be signed in to change notification settings - Fork 378
added availability guidelines #8506
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
Conversation
MattGal
left a comment
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.
LGTM.
| - [Hybrid Triage](hybridtriage.md) | ||
| - Stand Ups | ||
| - Stand Ups | ||
| - [Happy Hour](happyhour.md) |
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.
FYI: We're going to have a merge conflict here after my PR gets merged in.
| @@ -0,0 +1,23 @@ | |||
| # Hybrid Availability Expectations | |||
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.
OT: What's the thinking behind having this type of docs in Arcade? Seems like this is very much internal and for our team only? Whilst Arcade seems like a place for shared tooling?
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.
It kinda starts with a policy change at MSFT which is causing us to discontinue core-eng (our old "internal" repository). The knock on effect is "where" to put the docs, and Arcade seemed as good as any.
Arguably, the community that pays attention to Arcade would also be interested in how our team does things. In fact there's good precedence https://about.gitlab.com/handbook/ with gitlab for example...
We will (of course) need to continue to be diligent about keeping things secure.
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.
It was originally added to the internal wiki on AzDO on Feb 17th originally, and I shared the link in the team's General channel. Didn't get any feedback on it, so here we are: https://teams.microsoft.com/l/message/19:[email protected]/1645139027280?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=147df318-61de-4f04-8f7b-ecd328c256bb&parentMessageId=1645137015909&teamName=.NET%20Eng%20Services&channelName=General&createdTime=1645139027280
1c73c06
|
Ok - it seems this is ready to merge. Again though, it's a living doc and I anticipate updates as we learn more. |
| ## Days in Office: | ||
| There is no expectation that there be a set schedule for days in the office as we’re emphasizing flexibility. | ||
|
|
||
| Optional: Add your in-office days to your Teams' status |
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.
no apostrophe on Teams
| Optional: Add your in-office days to your Teams' status | |
| Optional: Add your in-office days to your Teams status |
An update to https://github.com/dotnet/arcade/tree/main/Documentation/TeamProcess/DevGuide
also snuck in the happy hour link....