Skip to content

Conversation

@markwilkie
Copy link
Member

@markwilkie markwilkie commented Feb 23, 2022

@markwilkie markwilkie requested a review from a team February 23, 2022 17:27
MattGal
MattGal previously approved these changes Feb 23, 2022
Copy link
Member

@MattGal MattGal left a 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)
Copy link
Member

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.

riarenas
riarenas previously approved these changes Feb 23, 2022
AlitzelMendez
AlitzelMendez previously approved these changes Feb 23, 2022
@@ -0,0 +1,23 @@
# Hybrid Availability Expectations
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Contributor

@michellemcdaniel michellemcdaniel Feb 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@markwilkie
Copy link
Member Author

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no apostrophe on Teams

Suggested change
Optional: Add your in-office days to your Teams' status
Optional: Add your in-office days to your Teams status

@markwilkie markwilkie merged commit 422c9bd into main Feb 28, 2022
@markwilkie markwilkie deleted the mawilkie-availability branch February 28, 2022 23:17
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.

8 participants