Difference between revisions of "CommunityData:Meetup September 2019"

From CommunityData
(basic outline for sept 2019 meetup planing)
 
m (re-organizing some of the sections)
Line 3: Line 3:
 
Last year, we also used [https://pad.riseup.net/p/CDSC-Spr19 shared note taking] (this is link to last year's).
 
Last year, we also used [https://pad.riseup.net/p/CDSC-Spr19 shared note taking] (this is link to last year's).
  
== Organization ==
+
== Overview ==
Overview of the meetup schedule.
+
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 ===
 
=== Research Presentations ===
Line 32: Line 46:
 
...
 
...
  
== Who's Coming? ==
+
== 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 [[#Accommodations|Accommodations section]].
 
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 [[#Accommodations|Accommodations section]].
  
Line 49: Line 63:
 
|}
 
|}
  
== Agenda ==
+
== Accommodations + Food ==
 
 
Any agenda notes go here.
 
 
 
'''Thursday, September 26'''
 
* Afternoon: Seattle folks arrive in Evanston
 
 
 
'''Friday, September 27'''
 
* 8:30am: Arrive + Breakfast (bagels or similar) @ [[Community Data Science Lab (UW)]] (CMU306)
 
 
 
'''Saturday, September 28'''
 
* 8:30am: Arrive + Breakfast (bagels or similar) @ [[Community Data Science Lab (UW)]] (CMU306)
 
 
 
== Accommodations ==
 
  
 
=== Who's Hosting Who? ===
 
=== Who's Hosting Who? ===
Line 90: Line 91:
 
| <strike>Restriction</strike>
 
| <strike>Restriction</strike>
 
|}
 
|}
 +
  
 
== Travel Plans ==
 
== Travel Plans ==
Line 99: Line 101:
 
** Status: Purchased
 
** Status: Purchased
 
** Notes:
 
** Notes:
 
  
 
== Evanston People To-do==
 
== Evanston People To-do==

Revision as of 18:25, 24 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 SEPT 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 SEPT 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 Accommodations section.

If you are planning on presenting during the critique and feedback sessions, add a "C&F with optional details next to your name on the list below! Not everybody will present so don't feel pressure to sign up.

Links in the table below are all protected by a username/password that should be in your email.

Attendee C&F Session Thursday Dinner Friday Dinner Event

Accommodations + Food

Who's Hosting Who?

Guest Tentative Host Notes
Name Name The hosting option

Description of hosting options here

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

Dietary Restrictions

[No need to add yourself here if you are unrestricted.]
Name Dietary notes
Name Restriction


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

  • Name
    • 🛬 Date - Arriving ...
    • 🛫 Date - Departing ...
    • Status: Purchased
    • Notes:

Evanston People To-do

Lab duties

Meal planning

  • Plan breakfast/lunch/dinner/snacks
  • Make reservations / catering orders for any restaurants

Activity planning

  • Outline work-related events
  • Decide on non-work events

Ideas of fun things to do

Where to eat

Previous Meetups

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