Skip to content

Latest commit

 

History

History
31 lines (24 loc) · 2.52 KB

note-taking-guidelines.md

File metadata and controls

31 lines (24 loc) · 2.52 KB

High level objectives for Code Ecologies public notes

  • Summarize the breakout discussions, particularly resources and next steps, for the benefit of those who could not attend.
  • Publish all notes to the notes folder of this public repository the same day as the event, December 15th.
  • Use a common format for all notes documents, described in detail below.
  • Err on the side of respecting the privacy of participants who do not want their comments attributed to them.
  • Without compromising the above, attempt to name participants who do want credit for their words.

Technical details

Format and submission of notes

At the beginning of each breakout, before the discussion begins, one person should create a Google doc, and share it with any other participants who also want to help with note taking.

At the end of the session, one person should send a link to the organizers via this form. We will take on the task of converting to markdown and publishing the notes to this public github repository.

To the extent you are able, please try to give the notes a little bit of structure with headings, list items, etc.

Naming notes documents

Please give your document the same title as the breakout if the facilitator has given it an official name. If there is no official session name, use your judgment to describe the theme of the discussion, perhaps asking other participants for their ideas regarding a short summary description!

Substantive details

What to capture

Try to repeat the speaker's words rather than rephrasing your interpretation of their meaning. However, of course it will be impossible for most people to create a transcript of an unplanned real-time discussion. Do your best to summarize the key points that participants in the discussion are making.

Privacy

By default, avoid naming who said what, unless the participant indicates that they do want to be named/credited for a particular comment. If possible, at the beginning of the session when folks introduce themselves, prompt them to say a word about whether they affirmatively do want to be credited for their contributions to the discussion. Even for people who are comfortable with their name being published, use your judgment to leave out highly personal details that belong in the room and not on the public internet.

As a note-taker, prioritize respecting privacy first, and capturing as much insight as possible in the limited time second, over writing down speakers' names.