Editing CommunityData:Meetup September 2019
From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 37: | Line 37: | ||
* 2:30PM - 4:30PM / Fun social activity: Kayaking @ NU Sailing Center | * 2:30PM - 4:30PM / Fun social activity: Kayaking @ NU Sailing Center | ||
* 5:30PM - 8:00PM / Dinner: Catering from TBD @ Aaron's place | * 5:30PM - 8:00PM / Dinner: Catering from TBD @ Aaron's place | ||
=== 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 === | === 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. | |||
If you want to participate, you need to email something to collective@communitydata.cc by the end of day on ''' | |||
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 48: | Line 52: | ||
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." | ||
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. | * '''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 55: | Line 58: | ||
* '''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. | ||
=== Unconference === | |||
... | |||
== Who's Coming to What? == | == Who's Coming to What? == | ||
