CommunityData:Meetup October 2022

We're meeting in Seattle on October 14 - 15! 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
Thursday, October 13

Evening Social Event

Friday, October 14

9:00 Coffee + Snacks

9:30 Sessions Begin

Lightning Talk Block One

Lightning Talk Block Two

Lightning Talk Block Three

Lightning Talk Block Four

Lightning Talk Block Five

Evening Meal + Social Event

Saturday, October 15

Social Activities On Your Own

Sunday, October 16

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 Friday, October 7. 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?
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 and/or on Friday.

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

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

Copy /paste format, fill in with your details:


 * [NAME]
 * 🛬Date - [WEEKDAY], October [DAY] [time and flight information]
 * 🛫Date - [WEEKDAY], October [DAY] [time and flight information]
 * Status: [PURCHASED / NOT PURCHASED]


 * Floor
 * 🛬Date - Monday, October 10th [7:25a-10:01am; UA580]
 * 🛫Date - Sunday, October [DAY] [5:59p-11:55p; DL1116]
 * Status: PURCHASED
 * Will arrange my own accommodation on the first three nights and the last night; so would like to crash somewhere Thu - Sat.


 * Sohyeon
 * 🛬Date - Monday, October 10th [7:25a-10:01am; UA580]
 * 🛫Date - Sunday, October 16 [5:59p-11:55p; DL1116]
 * Status: PURCHASED
 * Have arranged own accommodation for the first three nights; so looking to crash somewhere Thu, Fri, Sat nights.

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

Accommodations
Nate and Ellie are leading this. They will organize AirBnBs for people who want to stay in an AirBnB with other group members and link people able to offer accommodations to people coming in from out of town willing to stay at someone's home. People can get their own places to stay by themselves if they want as well.

If you are willing to host someone from out of town, please add yourself to the form below. Name, couch / guest room, location

If you need accommodations, please fill out the form below.

Meal planning

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

Activity planning

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

Session ideas
Please add your initials to vote for sessions / activities.

Goals: help newcomers feel welcome; reinforcing and establishing a safe, shared exchange of ideas, that it's okay to pitch out-there ideas; not every idea needs to turn into a project; stuff that is hard to do remotely (making people feel like they're part of the club)


 * Housekeeping stuff / keeping people up to speed on things like Hyak (NT; BMH; MDB; JF)
 * Time for open-ended conversation on a set of topics or prompts
 * Ways to facilitate interaction and intellectual exchange
 * Half-baked off (BMH; MDB; JF; RC)
 * Lightning talks on everyone's work (so we all know what everyone else is doing) (NT; FF; SD; BMH; KC; MDB; JF; YF; RC)
 * A reading group of fun / canonical texts (BMH; MDB; YF, RC)
 * Social activities (NT; FF; SD; BMH; KC; MDB; JF; YF; RC)
 * Things that make a good newcomer experience (NT; FF; BMH; YF)
 * Expressing and communicating work and ideas (e.g. Matsuzaki outlines) (KC; RC)
 * The lifecycle of research, how we develop research questions, etc (MDB)
 * Things we wish we knew when we start(ed) grad school (BMH; JF; YF)
 * The CDSC way of being a scholar; how to be in a lab/the CDSC; what makes CDSC special/unique; (NT; FF; SD; BMH; KC; MDB; YF)
 * C&F / workshops (small number? plan for after newcomer workshop) (BMH; JF)
 * invite a guest(s) (SD; BMH; MDB)
 * coworking sessions/unconference (FF; BMH; KC)

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


 * CommunityData:Meetup December 2019
 * CommunityData:Meetup March 2019
 * CommunityData:Meetup September 2018
 * CommunityData:Meetup April 2018
 * CommunityData:Meetup July 2017