Editing CommunityData:Critique and Feedback Session
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 1: | Line 1: | ||
== | === Procedures and Norms === | ||
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 | If you want to participate, you need to email something to collective@communitydata.cc by the end of day on the Monday before the weekend of the C&F session. 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. | 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. | ||
Line 18: | Line 16: | ||
* '''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. | ||