This repo is adapted from Awesome reading group. The idea is to read 2-3 papers and organize 1-hour meetings once in two weeks. No one is expected prepare slides and/or read the papers in depth.
Please feel free to give any feedback on current organisation as a new issue to this repository - it can be adapted to our needs.
Details still to be decided
https://zoom.us/j/xxxxxxxxxxxxxxxx
1 - ADD and VOTE on papers as comments in the voting issue You may only put the title and the link to the paper, or add any comments to help people to understand why it is worth reading.
2 - The top voted comment from "voting issue" gets selected The corresponding comment gets deleted from the voting issue and a new issue is created with the date of discussion:
3- Read the selected paper according to one's time/knowledge
4- Attend the reading group
4'- Sprints, in future, once we have gotten a rhythm
-Sometimes the reading group can go beyond a single paper: eg. conference proceedings, several papers around the same subject, etc. The idea of the sprint is to grasp the as much papers as possible in a short time. We block 2h slot for this. The sprint happens in two phases:
during 45 min everybody goes through papers, selects the titles they are interested it, try to read through to get an idea of the paper, and give it a note on 1-10 scale for 'worth reading in details'. You may add a short comment about 'why it is interesting, worth reading, what it is about' or any reminder for yourself.
after 45 min of individual reading we sort the papers based on 'collective' score they got, and go through them one by one. People who have voted for the papers should 'convince' others that the papers is worth reading into more details. This is a way to get a pretty broad coverage of the conference proceedings, even in the case when nobody attended the conference.
Examples of successful sprints are those made after conference acceptance notifications.
5- After discussion add your thoughts as a comment on the issue of the discussion day (NOT the voting issue)
6-watch the repo so you get email updates with new meetings