CommunityData:Meetup September 2019: Difference between revisions
From CommunityData
m (Benjamin Mako Hill moved page CommunityData:CDSC Meetup September 2019 to CommunityData:Meetup September 2019: make naming consistent) |
|||
| (20 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
We're meeting in Evanston on September 26-28! We will be meeting in | We're meeting in Evanston on September 26-28! We will be meeting in <span style="color: blue; font-weight: bold;">Frances Searle Building, Room 1-483</span>. If you're calling in, we'll be at http://meet.jit.si/cdsc as per our custom. | ||
We'll be taking group notes at [https://etherpad.wikimedia.org/p/cdsc-201909 in a shared Etherpad for the event]. You can see [https://pad.riseup.net/p/CDSC-Spr19 the pad we created last time] for an idea of what this might look like. | |||
[[File:Crazy 2.png|500px|thumb|right|[[People|CDSC members]] at NU September 2019 meetup. Photo by innocent stranger.]] | |||
== Agenda== | |||
{{notice|The PDFs linked below are password protected. See Mako's email for the username/password.}} | |||
'''Thursday, September 26''' | '''Thursday, September 26''' | ||
* Seattle folks trickle into Evanston/Chicago | * Seattle folks trickle into Evanston/Chicago | ||
* | * Optional + self-organizing dinner because multiple people (Nate, Charlie) are landing late. | ||
'''Friday, September 27''' | '''Friday, September 27''' | ||
* 8:30AM / Arrive + Breakfast (bagels, yogurt, fruits, snackies) @ Frances Searle Building, Room 1-483 | * 8:30AM / Arrive + Breakfast (bagels, yogurt, fruits, snackies) @ Frances Searle Building, Room 1-483 | ||
* | * 9am - Introductions | ||
** Slot A1: | * 9:30AM - 12:00PM / C&F Sessions (30-45 min slots) | ||
** Slot A2: | ** Slot A1: Charlie [[https://communitydata.science/~mako/retreat_material_201909/healspersecond-modteam_network_proposal-20190923.pdf PDF]] (Discussants: Regina, Nick, Salt) | ||
** Slot A3: | ** Slot A2: Sohyeon [[https://communitydata.science/~mako/retreat_material_201909/sohw-grfp_research_plan-20190932.pdf PDF]] (Discussants: Regina, Nate) | ||
** Slot A4: | ** Slot A3: Sejal [[https://communitydata.science/~mako/retreat_material_201909/sejal-knowledge_gaps_proposal-20190923.pdf PDF]] (Discussants: Jim, Charlie, Emilia) | ||
* 12:00PM - 1:30PM / Lunch Break: Tomate Fresh (tacos + salad) | ** Slot A4: Jeremy [[https://communitydata.science/~mako/retreat_material_201909/jdfoote-retreat_material-20190923.pdf PDF]] (Discussants: Nick, Kaylea) | ||
* 1:30PM - 4:30PM / C&F Sessions (45 min slots) | * 12:00PM - 1:30PM / Lunch Break: [http://www.tomatefreshkitchen.net/ Tomate Fresh] (tacos + salad) | ||
** Slot B1: | * 1:30PM - 4:30PM / C&F Sessions (30-45 min slots) | ||
** Slot B2: | ** Slot B1: Nick [[https://communitydata.science/~mako/retreat_material_201909/nhagar-reddit_news_attention-20190923.pdf PDF]] (Discussants: Nate, Salt, Charlie) | ||
** Slot B3: | ** Slot B2: Kaylea [[https://communitydata.science/~mako/retreat_material_201909/kaylea-identity_and_experience-21090923.pdf PDF]] (Discussants: Floor, Soheyon, Jim) | ||
** Slot B4: | ** Slot B3: Jackie [[https://communitydata.science/~mako/retreat_material_201909/jackie-bias_proposal-20190924.pdf PDF]] (Discussants: Floor, Kaylea, Emilia) | ||
* Wrap up 4:30PM - 5: | ** Slot B4: Mako & Aaron [[https://communitydata.science/~mako/retreat_material_201909/mako_ashaw-cdsc_staff_role-20190923.pdf PDF]] (Discussants: All Y'all) | ||
* Wrap up 4:30PM - 5:30PM | |||
* 6:30PM / Dinner: [http://rhcponline.com/ Red Hot Chili Pepper Evanston] | * 6:30PM / Dinner: [http://rhcponline.com/ Red Hot Chili Pepper Evanston] | ||
| Line 39: | Line 38: | ||
* 5:30PM - 8:00PM / Dinner: Catering from TBD @ Aaron's place | * 5:30PM - 8:00PM / Dinner: Catering from TBD @ Aaron's place | ||
=== | === Critique and Feedback Sessions === | ||
For the '''critique and feedback''' sessions we're expecting everybody who wants to participate to submit (a) something in writing (e.g., a paper, a [[Matsuzaki outline]], an extended abstract) and (b) a list of questions or types of feedback you want. Please only submit something you want feedback on! | |||
If you want to participate, you need to email something to collective@communitydata.cc by the end of day on ''' | If you want to participate, you need to email something to collective@communitydata.cc by the end of day on '''Monday September 23'''. Not everybody needs to participate but anybody who does participate should only submit one thing. | ||
We're expecting that everyone attending will have read all the material submitted and will bring notes to the meeting. When we meet, everyone who has submitted something will get at least half an hour (more if possible). | We're expecting that everyone attending will have read all the material submitted and will bring notes to the meeting. When we meet, everyone who has submitted something will get at least half an hour (more if possible). | ||
| Line 53: | Line 48: | ||
When we meet, these sessions will be run with ''no presentations'' and ''no formal introductions''. The plan to just jump in and start answering the questions and talking about thing we've all already read." | When we meet, these sessions will be run with ''no presentations'' and ''no formal introductions''. The plan to just jump in and start answering the questions and talking about thing we've all already read." | ||
These are our norms: | |||
* '''Take the entire group as an audience''': the best feedback is beneficial or thought-provoking to the group as a whole, prompts group discussion/consideration, asks a question, etc. | * '''Take the entire group as an audience''': the best feedback is beneficial or thought-provoking to the group as a whole, prompts group discussion/consideration, asks a question, etc. | ||
* If the author is your only audience, '''be practical and actionable for the project's current stage'''. Early-stage work is expected to be a little unpolished and crunchy, and proposing a large new branch of analysis for a nearly-complete work should be approached with a scoping statement (Must this be done for the work to be valid? Or are you proposing a follow-up line of inquiry to be stated in the Future Work section?) | * If the author is your only audience, '''be practical and actionable for the project's current stage'''. Early-stage work is expected to be a little unpolished and crunchy, and proposing a large new branch of analysis for a nearly-complete work should be approached with a scoping statement (Must this be done for the work to be valid? Or are you proposing a follow-up line of inquiry to be stated in the Future Work section?) | ||
| Line 59: | Line 55: | ||
* '''Avoid vaguebooking'''. "Framework needs some work" or "Lacking some flow" isn't as useful as "I don't think you're getting a lot out of using Foucault, Latour, and Habermas here, and explaining them is pretty heavy -- maybe you can get away with just invoking Benkler and moving on" and experience-grounded comments like "When you transitioned from section 2 to section 3, and half-way through section 4, I ended up flipping back to the abstract to figure out what was going on". | * '''Avoid vaguebooking'''. "Framework needs some work" or "Lacking some flow" isn't as useful as "I don't think you're getting a lot out of using Foucault, Latour, and Habermas here, and explaining them is pretty heavy -- maybe you can get away with just invoking Benkler and moving on" and experience-grounded comments like "When you transitioned from section 2 to section 3, and half-way through section 4, I ended up flipping back to the abstract to figure out what was going on". | ||
* '''Don't narrate the typo you found on line 156''': feedback best conveyed via a marked-up draft should be delivered via a marked-up draft. | * '''Don't narrate the typo you found on line 156''': feedback best conveyed via a marked-up draft should be delivered via a marked-up draft. | ||
== Who's Coming to What? == | == Who's Coming to What? == | ||
| Line 97: | Line 90: | ||
|- | |- | ||
| [[Salt]] | | [[Salt]] | ||
| | | no | ||
| unsure | | unsure | ||
| yes | | yes | ||
| Line 126: | Line 119: | ||
| Regina | | Regina | ||
| No | | No | ||
| | | No | ||
| yes | | yes | ||
| yes | | yes | ||
| Line 276: | Line 269: | ||
* Make reservations / catering orders for any restaurants | * Make reservations / catering orders for any restaurants | ||
==== | ==== Notes ==== | ||
* | * Breakfast items + snacks obtained | ||
* | * Catering orders in (Friday & Saturday lunches, Saturday dinner) | ||
* | * RHCP Friday dinner reservation made | ||
=== Activity planning === | === Activity planning === | ||
Latest revision as of 01:25, 13 October 2019
We're meeting in Evanston on September 26-28! We will be meeting in Frances Searle Building, Room 1-483. If you're calling in, we'll be at http://meet.jit.si/cdsc as per our custom.
We'll be taking group notes at in a shared Etherpad for the event. You can see the pad we created last time for an idea of what this might look like.
Agenda[edit]
|
The PDFs linked below are password protected. See Mako's email for the username/password. |
Thursday, September 26
- Seattle folks trickle into Evanston/Chicago
- Optional + self-organizing dinner because multiple people (Nate, Charlie) are landing late.
Friday, September 27
- 8:30AM / Arrive + Breakfast (bagels, yogurt, fruits, snackies) @ Frances Searle Building, Room 1-483
- 9am - Introductions
- 9:30AM - 12:00PM / C&F Sessions (30-45 min slots)
- 12:00PM - 1:30PM / Lunch Break: Tomate Fresh (tacos + salad)
- 1:30PM - 4:30PM / C&F Sessions (30-45 min slots)
- Wrap up 4:30PM - 5:30PM
- 6:30PM / Dinner: Red Hot Chili Pepper Evanston
Saturday, September 28
- 8:30AM / Arrive + Breakfast (yogurt, fruits, snackies) @ Frances Searle Building, Room 1-483
- 9:00AM - 12:00PM / Unconference
- 12:00PM - 1:00PM / Lunch delivery: Potbelly Sandwiches + some salad
- 1:00PM - 2:00PM / Unconference wrap-up
- 2:30PM - 4:30PM / Fun social activity: Kayaking @ NU Sailing Center
- 5:30PM - 8:00PM / Dinner: Catering from TBD @ Aaron's place
Critique and Feedback Sessions[edit]
For the critique and feedback sessions we're expecting everybody who wants to participate to submit (a) something in writing (e.g., a paper, a Matsuzaki outline, an extended abstract) and (b) a list of questions or types of feedback you want. Please only submit something you want feedback on!
If you want to participate, you need to email something to collective@communitydata.cc by the end of day on Monday September 23. Not everybody needs to participate but anybody who does participate should only submit one thing.
We're expecting that everyone attending will have read all the material submitted and will bring notes to the meeting. When we meet, everyone who has submitted something will get at least half an hour (more if possible).
When we meet, these sessions will be run with no presentations and no formal introductions. The plan to just jump in and start answering the questions and talking about thing we've all already read."
These are our norms:
- Take the entire group as an audience: the best feedback is beneficial or thought-provoking to the group as a whole, prompts group discussion/consideration, asks a question, etc.
- If the author is your only audience, be practical and actionable for the project's current stage. Early-stage work is expected to be a little unpolished and crunchy, and proposing a large new branch of analysis for a nearly-complete work should be approached with a scoping statement (Must this be done for the work to be valid? Or are you proposing a follow-up line of inquiry to be stated in the Future Work section?)
- Don't dogpile -- time is short, so even positive plus-ones should be brief: don't repeat what others have said, don't feel the need to chime in or pile on a critique: it is assumed that you read the paper and are supportive of the author.
- Avoid vaguebooking. "Framework needs some work" or "Lacking some flow" isn't as useful as "I don't think you're getting a lot out of using Foucault, Latour, and Habermas here, and explaining them is pretty heavy -- maybe you can get away with just invoking Benkler and moving on" and experience-grounded comments like "When you transitioned from section 2 to section 3, and half-way through section 4, I ended up flipping back to the abstract to figure out what was going on".
- Don't narrate the typo you found on line 156: feedback best conveyed via a marked-up draft should be delivered via a marked-up draft.
Who's Coming to What?[edit]
Please add your name below if you think that you'll be attending any of the meetup's events! Also, if you'll be traveling and/or have food requirements, please fill out your information in the Travel Plans section Accommodations + Food section.
If you are planning on presenting during the critique and feedback sessions, answer "yes" to the "C&F" box with optional details next to your name on the table below! Not everybody will present so don't feel pressure to sign up.
For reference:
- C&F is Critique + Feedback sessions are expected to be Friday;
- Saturday will probably have flexible (co-)working sessions;
- A fun social outing is probably going to be scheduled Thursday evening after dinner or on Saturday.
| Attendee | C&F Session Submission? | Thursday Dinner | Friday Dinner | Saturday Sessions | Saturday Fun Event |
|---|---|---|---|---|---|
| Sohyeon | maybe? | no | yes | yes | yes |
| Mako | No | yes | yes | yes | (doesn't like fun but will attend anyway) |
| Salt | no | unsure | yes | yes | yes |
| Nate | Probably No | yes | yes | yes | yes |
| Kaylea | yes | No (arriving too late) | yes | yes | No (departing too soon) |
| Jeremy | Probably Not | yes | yes | yes | yes |
| Regina | No | No | yes | yes | yes |
| Nick | yes | yes | yes | yes | yes |
| Charlie | no | yes | yes | yes | yes |
| Aaron | No | yes | yes | yes | yes |
| Sejal | yes | yes | yes | yes | yes |
| Jim | No | yes | yes | yes | yes |
| Floor | No | yes | yes | yes | yes |
Accommodations[edit]
Our current plan is to book 1-2 AirBnBs for sleeping arrangements. If you are listed in "Who's Coming to What" then I will assume that you need somewhere to sleep (other than Mako, who I think is going to stay with Aaron).
Dietary Restrictions[edit]
[No need to add yourself here if you are unrestricted.]
| Name | Dietary notes |
|---|---|
| Mako, Charlie, Floor, Aaron | Vegetarian (👍: milk, eggs) |
| User:Kaylea | don't eat fish (sushi and shellfish ok); don't eat eggs (chocolate cake ok) |
| Sejal | Allergic to seafood (esp. prawns) |
| Aaron | Allergic to sesame, nuts (except almonds and peanuts...which are inexplicably fine) |
Travel Plans[edit]
If you are traveling in from outside, add your name and arrival details here (days, times and flights if you have them, status (purchased/in-progress), any notes).
Copy /paste format, fill in with your details:
- [NAME]
- 🛬Date - [WEEKDAY], September [DAY] [time and flight information]
- 🛫Date - [WEEKDAY], September [DAY] [time and flight information]
- Status: [PURCHASED / NOT PURCHASED]
- Mako
- 🛬 Date - Wednesday September 25 23:40 (AS 1026 SEA→ORD)
- 🛫 Date - Monday September 30 6:00 (AS 27 ORD→SEA)
- Status: Purchased
- Notes: Staying for a couple extra days to work on projects.
- Charlie
- 🛬Date - Thursday, September 26 18:20 (Arrival) [AS 22 SEA→ORD]
- 🛫Date - Sunday, September 29 13:40 (Departure) [AS 39 ORD→SEA]
- Status: Purchased
- Jeremy
- 🚗 - Probably Thursday morning to Saturday evening
- Sejal
- 🛬Date - Thursday, September 26 12:35 pm (AS 28 SEA→ORD)
- 🛫Date - Sunday, September 29 7:25 pm (AS 21 ORD→SEA)
- Status: Purchased
- Kaylea
- 🛬ARR - Thursday, September 26 United 277, 10:46 p.m.
- 🛫DEP - Saturday, September 28 United 262, 7:50 p.m.
- Status: Purchased
- Nate
- 🛬Date - Thursday, September 26 18:25 (AS 10 SEA→ORD)
- 🛫Date - Sunday, September 29 08:00 (AS 1011 ORD→SEA)
- Status: PURCHASED
- Emilia
- Status: CALLING IN (TOO MUCH RECENT TRAVEL)
- Regina
- 🛬Date - Thursday, September 26 4:14 pm (AA 2377 SAN→ORD)
- 🛫Date - Sunday, September 29 07:50 am (UA 1846 ORD→SEA)
- Status: PURCHASED
- Salt
- 🛬Date - Thursday, September 26 United 227 22:46
- 🛫Date - Sunday, September 29 United 635 8:08
- Status: PURCHASED
Evanston People To-do[edit]
Lab duties[edit]
Logistics Planning[edit]
- Get attendance list + travel details of people flying in
- Get dietary restrictions
- Decide retreat schedule
- Figure out what the social event will be
- Determine restaurants/ordering food
- Reach out to any potential speakers if we want to have research presentations
- Schedule C&F sessions
Accommodations[edit]
- Jeremy will coordinate
Meal planning[edit]
- Obtain list of dietary restrictions
- Plan breakfast/lunch/dinner/snacks
- Make reservations / catering orders for any restaurants
Notes[edit]
- Breakfast items + snacks obtained
- Catering orders in (Friday & Saturday lunches, Saturday dinner)
- RHCP Friday dinner reservation made
Activity planning[edit]
- Outline work-related events
- Decide on non-work events
- Decide on where we will hold the event(s)
Ideas of fun things to do[edit]
- Paintball
- Axe-throwing: Bad Axe (2 locations); Ragnorak Axe Throwing; BATL
- Escape room
- Fun workshops like pottery or painting or cooking, etc.
- Adler planetarium
- architecture tours along the river/lake
- something lake-related
- Shameless plug: If anyone feels excited about the idea of an early Friday morning workout with fun people, come join the November Project at the Bean @6:00am
- These electric boats are super fun, but max capacity 12
- Kayaking at Skokie Lagoons
- Biking on Green Bay Trail
- Hiking at Openlands Lakeshore Preserve. I biked there today. It's pretty gorgeous, if that's a thing. We could also have a campfire with smores - have to check if this is allowed. Outside is free. Just saying.
- Chicago Botanic Gardens
- Illinois labor history tour(!)
- Chicago Architecture Foundation walking tours: Underground Pedway tour; L train/public art tours; Evanston lakefront tour; Food/neighborhood pub tours
Previous Meetups[edit]
We meet roughly twice a year and you can see what we've done in the past at:
