-
Notifications
You must be signed in to change notification settings - Fork 56
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
Summit Topic: Node.js Community Committee: OKR building #203
Comments
@bnb How long would you like for this? |
@bnb right now there are two sessions for this on the second day. One for CommComm and one for Initiatives together. (2 hours total) We need 15min at the start of the day and trying to make some adjustments. |
That works! |
Thanks! I adjusted the schedule :)
…On Tue, Nov 26, 2019 at 3:25 PM Tierney Cyren ***@***.***> wrote:
That works!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#203?email_source=notifications&email_token=AKYQ3QJH3Y7NQRLQOMJPL3DQVWV5PA5CNFSM4JN6YZZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFHYRJI#issuecomment-558860453>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKYQ3QOIRV46RIF6AF6YFOLQVWV5PANCNFSM4JN6YZZQ>
.
--
Eva Howe
Operations Manager
This Dot Labs
eva@thisdot.co
|
Working doc for OKR discussion: |
@bnb are there any notes or other artifacts for this session? If so can you share them here? I am happy to make a PR and add them to the summit directory or feel free to raise one by yourself. Thanks! |
@christian-bromann documented here: https://hackmd.io/CcdbsSuOSyG2k8qFsEF2Zw?view Will be PRing this to the Node.js CommComm repo at some point soon-ish. |
Awesome, thanks @bnb ! |
Topic of the session
Node.js Community Committee: OKR building
Type of the session
Follow-up / Set-up sessions (if any)
Level
Pre-requisite knowledge
Describe the session
A session to plan out 2020 OKRs for the Node.js Community Committee (nodejs/community-committee#547)
Session facilitator(s) and Github handle(s)
@bnb
Additional context (optional)
The text was updated successfully, but these errors were encountered: