Update Event Checklist
- Dominant language
- No language data
- Stars
- 20
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The following points should be added to/changed in the [Event Checklist](https://github.com/kossiitkgp/docs/blob/1108a05c7b139eda7f84b2f4f19811326e234c17/community/event-checklist.md).
- Updating the [workshops](https://github.com/kossiitkgp/workshops) repository.
- The fact that all workshops are consolidated into the single workshops repo.
> ✔️ Make a Github repo for the workshop with name as event name and year which contains - installation instructions, slides, references, recording and others. (For example refer - [1](https://github.com/kossiitkgp/git-and-github-workshop-2020), [2](https://github.com/kossiitkgp/REST-APIs-in-Flask-Workshop-2021), [3](https://github.com/kossiitkgp/Linux-Shell-Vim-Workshop-2021))
- Anonymous feedback forms. Make sure to read previous feedback and create a new anonymous feedback form for this year, add it to the slides along with a qr code for the same.
- Link to the poster design, printing, and pasting guidelines. Also, add a timeline for how early posters should be printed and stuck.
- Link to the room booking guidelines and add a timeline for that too.
- PRC email for publicity. (either iitkgp.pr@gmail.com or prctsg@iitkgp.ac.in) Below is a suggested format for the email
```
Hope this email finds you well
Kharagpur Open Source Society (KOSS) is organising [EVENT] on [DATE] at [VENUE].
Therefore, we request you to share this with the KGPian Student Community.
[EVENT DETAILS/WRITEUP]
Also attached to this email is the poster for the same.
```
- This was once suggested by Rajiv might as well mention [The "Three Things" Exercise for getting things out of talk](https://math.stanford.edu/~vakil/threethings.html) - @proffapt
- [ ] Read previous `docs` and `mistakes` about the event if happened before
- Talk with others to rectify previous mistakes
- [ ] Update `docs` and `mistakes` repo, if any
- [ ] Update `mailing-list` from form responses, if there was a form
Contributor guide
Research direction
Start with community/event-checklist.md at the referenced commit and compare its current sections with the requested additions. Update the checklist with the workshops repository guidance, feedback and publicity details, poster and room-booking timelines, the suggested exercise, and the remaining event follow-up items. Done means each requested point is represented clearly in the checklist.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100