Difference between revisions of "CommunityData:Meetup September 2019"

From CommunityData
Jump to navigation Jump to search
(→‎Who's Coming to What?: Putting table in ~chronological order)
Line 57: Line 57:
 
|-
 
|-
 
! Attendee  
 
! Attendee  
! C&F Session
+
! C&F Session Submission?
! Saturday Sessions
 
 
! Thursday Dinner
 
! Thursday Dinner
 
! Friday Dinner
 
! Friday Dinner
 +
! Saturday Sessions
 
! Fun Event (TBD)
 
! Fun Event (TBD)
 
|-
 
|-
Line 79: Line 79:
 
| [[Salt]]
 
| [[Salt]]
 
| yes
 
| yes
 +
| unsure
 
| yes
 
| yes
| unsure
 
 
| yes
 
| yes
 
| yes
 
| yes
Line 97: Line 97:
 
|yes
 
|yes
 
|yes
 
|yes
 +
|-
 +
| [[user:Jdfoote|Jeremy]]
 +
| Probably Not
 +
| yes
 +
| yes
 +
| yes
 +
| yes
 
|}
 
|}
  

Revision as of 12:03, 31 July 2019

We're meeting in Evanston on September 26-28! We will be meeting in XYZ. If you're calling in, we'll be at the CDSC Jitsi.

Last year, we also used shared note taking (this is link to last year's).

Overview

Overview of the meetup.

Any notes about events and logistics go here.


Agenda

Thursday, September 26

  • Afternoon: Seattle folks arrive in Evanston

Friday, September 27

  • 8:30am: Arrive + Breakfast (bagels or similar) @ ...

Saturday, September 28

  • 8:30am: Arrive + Breakfast (bagels or similar) @ ...


Research Presentations

FROM MARCH 2019 "For the first time, we're planning to invite a small number of more formal talks from CDSC affiliates and visitors. There are two goals with these presentations: (a) introduce yourself and your research interests to the group; (b) present finished research to teach us something new! We've got a maximum of ~20 minutes per presentation (and it's a hard maximum) but you are welcome to use less time—especially if you are interested in presenting unfinished work in a C&F session."

Critique and Feedback Sessions

FROM MARCH 2019 "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 Friday, March 22. 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."

Proposed 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.

Unconference

...

Who's Coming to What?

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 Fun Event (TBD)
Sohyeon ? yes yes yes yes/tbd
Mako No yes yes yes yes
Salt yes unsure yes yes yes
Nate Probably No yes yes yes yes
Kaylea yes yes yes yes yes
Jeremy Probably Not yes yes yes yes

Accommodations + Food

Hosting Options

Example Person: Can host two people, one on futon, one on a comfy couch. Both in my living room.


Hosting

Guest Tentative Host Notes
User:Mako Aaron Guest room? (Sound OK Aaron?)

Dietary Restrictions

[No need to add yourself here if you are unrestricted.]

Name Dietary notes
User:Mako Vegetarian (👍: milk, eggs)
User:kaylea don't eat fish (sushi and shellfish ok); don't eat eggs (chocolate cake ok)

Travel Plans

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):

  • 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.

Evanston People To-do

Lab duties

Logistics Planning

  • 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

Meal planning

  • Obtain list of dietary restrictions
  • Plan breakfast/lunch/dinner/snacks
  • Make reservations / catering orders for any restaurants

Where to maybe eat

  • Farmhouse
  • Found Kitchen and Social House
  • The Cellar at the Stained Glass
  • Nakorn
  • Red hot chilli pepper
  • ...

Activity planning

  • Outline work-related events
  • Decide on non-work events
  • Decide on where we will hold the event(s)

Ideas of fun things to do

  • Axe-throwing
  • Escape room
  • Walking or food/restaurant tour
  • Fun workshops like pottery or painting or cooking, etc.
  • Adler planetarium
  • architecture tours along the river/lake
  • something lake-related
  • something low key Yatch 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

Previous Meetups

We meet roughly twice a year and you can see what we've done in the past at: