This repository has been archived by the owner on Oct 9, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
2017 07 31.md
Brian Tingle edited this page Aug 8, 2017
·
8 revisions
Monday 31 June 2017, 9:00:00 am PDT, 11:00:00 am CDT, 12:00:00 noon EDT, 5:00:00 pm BST, 6:00:00 pm CEST, 16:00:00 UTC (GMT).
- Moderator/Gatekeeper:
- Notetaker:
- Connection information: Meeting Link is https://stanford.zoom.us/j/386303946 or click
Details
below for more connection information (calling in, mobile connections, international numbers, etc.)
Join from PC, Mac, Linux, iOS or Android: https://stanford.zoom.us/j/386303946
Or iPhone one-tap (US Toll): +14086380968,386303946# or +16465588656,386303946#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+886 277 417 473 (Taiwan Toll)
+1 855 703 8985 (Canada Toll Free)
Meeting ID: 386 303 946
International numbers available: https://stanford.zoom.us/zoomconference?m=ASuUAQjV9YXnKeslCiUZNE3Ja5cqdVFx
Or an H.323/SIP room system:
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
Meeting ID: 386 303 946
SIP: [email protected]
- Christina Harlow
- Chrissy Rissmeyer
- Brian Tingle (absent, took a vacation day)
- Adam Soroka
- Ryan Johnson
- Suzanne Pilsk
- Julie Hardesty
- send out call for use cases using communication structure
- figure out analysis method for cases gathered
- update work plan timeframe
- Questions, Comments, Issues
- Confirm Next Call
- finalized text for email (https://github.com/LD4/ld4-community-recon/issues/43)
- Christina will add links (Github link at bottom of call), put this in communication page, and ping people in communication contact list
- Leave this call out until August 15 and then start reviewing what is there - use cases are still welcome afterwards
- need to add email addresses? yes, Christina will add Arwen and Christina’s email addresses to call for alternate way to offer use case
- Everyone look through this table and sign up as a contact, also add any community that isn’t listed here but should be
- Christina will email meeting notes and fix call template and then notify us that call is ready to be sent (today)
- Edit text if needed for a community but keep as consistent as possible
- send out by Wednesday this week
- probably lots of out of office so might need to extend call for use cases
- stick with August 15 and might extend after that - possibly second call in the fall if needed
- Everyone in this group add use cases by August 15
- affinity mapping exercise - group things together
- de-duplicate similar use cases
- labels in Github and anyone can apply; google spreadsheet with categories in columns - Chrissy will investigate options
- by next call - do a pass of issues that are not your own, comment if you think it’s a duplicate and propose a couple of labels, possibly based on categories listed already in work plan
- still on track to work through this by end of October
- labels created for 3 categories in the work plan area
- Christina will add use case call text to communication page and ping everyone listed as communication contact
- Send out call to identified lists by Wednesday, August 2
- Christina will review https://github.com/LD4/ld4-community-recon/issues/43 and integrate any suggested changes into the text (add Github link and email addresses for Arwen Hutt and Christina Harlow)
- Everyone add lists and volunteer as contact on https://github.com/LD4/ld4-community-recon/wiki/External-Communication-Channels
- Everyone add use cases by August 15
- Chrissy will investigate options for affinity mapping of use cases
- Everyone identify duplicate use cases and apply 1-2 labels for each use case by next call (August 14)
- Resolve any remaining technical issues
- Move notes from #56 to wiki