The single source of truth for GDG on Campus JIS University events. Every event is an issue, its stage is a label, and an approved event publishes itself to this repository's listing. Nothing about an event lives in someone's head or a private chat.
-
Open an event — create a new issue using the Event template and fill in the schema.
-
Move it through the lifecycle — the event's label tracks its stage:
need-info→scheduled→approved→graphics-ready→mou-ready→listed→completedFrom any stage an event may be marked
cancelled(the issue is closed with a reason and dropped from the listing). -
Definition of done — before an event is set out and moved to
listed:- Approved through the on-campus flow
- MoU committed, and the hardcopy signed
- Graphics linked (banner 2560×650 + 1:1 thumbnail)
- Attendance form ready
- Dashboard link set
-
Each event also gets its own repository for its material — slides, code, resources, the MoU, the attendance CSV and graphics. When the event is done, that repo is archived and shared on socials.
A single fixed Google Form is circulated for every event, of any type, to take attendance.
Participation certificates are generated from the name and email recorded in the form. An event is
marked completed only when a valid attendance CSV — fixed columns Name, Email, College, Year — is
committed to the event's repository.
The full process is documented in the chapter's Guidelines & Playbook
(dscjisu/guidelines) — Managing Events on GitHub.
GDG on Campus JIS University · Department of Computer Science & Engineering