├── .gitattributes
├── static
    └── CC-by-NC-SA.png
├── humans.txt
├── .editorconfig
├── CHANGELOG.md
├── .github
    ├── ISSUE_TEMPLATE
    │   ├── config.yml
    │   └── talk-proposal.yaml
    └── workflows
    │   └── stale.yml
├── .gitignore
├── assets
    ├── js
    │   ├── youtube.js
    │   ├── main.js
    │   └── controller.js
    └── css
    │   └── main.css
├── README.md
├── old_videos.json
├── videos.json
├── index.html
└── guidelines.md


/.gitattributes:
--------------------------------------------------------------------------------
1 | * text=auto
2 | 


--------------------------------------------------------------------------------
/static/CC-by-NC-SA.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/pydelhi/talks/HEAD/static/CC-by-NC-SA.png


--------------------------------------------------------------------------------
/humans.txt:
--------------------------------------------------------------------------------
 1 | Code Contributors
 2 | =================
 3 | 
 4 | Saurabh Kumar (gh: theskumar / @_theskumar)*
 5 | 
 6 | * Possesses commit rights
 7 | 
 8 | Video Management
 9 | =================
10 | Vinay Dahiya (gh: vinaykrdahiya / @01_vkd)
11 | 
12 | Special Thanks
13 | ===============
14 | 
15 | The following haven't provided code directly, but have provided guidance and advice.
16 | 


--------------------------------------------------------------------------------
/.editorconfig:
--------------------------------------------------------------------------------
 1 | # http://editorconfig.org
 2 | 
 3 | root = true
 4 | 
 5 | [*]
 6 | charset = utf-8
 7 | end_of_line = lf
 8 | insert_final_newline = true
 9 | trim_trailing_whitespace = true
10 | 
11 | [*.{py,rst,ini}]
12 | indent_style = space
13 | indent_size = 4
14 | 
15 | [*.yml]
16 | indent_style = space
17 | indent_size = 2
18 | 
19 | [*.md]
20 | trim_trailing_whitespace = false
21 | 
22 | [Makefile]
23 | indent_style = tab
24 | 


--------------------------------------------------------------------------------
/CHANGELOG.md:
--------------------------------------------------------------------------------
 1 | # Change Log
 2 | All notable changes to this project will be documented in this file.
 3 | This project adheres to [Semantic Versioning](http://semver.org/).
 4 | 
 5 | ## [Unreleased][unreleased]
 6 | ### Added 
 7 | - Add license to README.
 8 | - `humans.txt` to recognize the human efforts behind this project.
 9 | - Open issues count badge
10 | - This CHANGELOG file, based on the guidelines from http://keepachangelog.com/.
11 | - Th `.editorconfig` file to fix editor differences.
12 | - README with list of talks
13 | 
14 | [unreleased]: https://github.com/pydelhi/talks/compare/v0.0.0...HEAD
15 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/config.yml:
--------------------------------------------------------------------------------
 1 | blank_issues_enabled: true
 2 | contact_links:
 3 |   - name: 💬 PyDelhi WhatsApp
 4 |     url: https://chat.whatsapp.com/IUA2o1Xu8w8LmaZ8bw0nbb
 5 |     about: Please use the WhatsApp community to connect with fellow Pythonistas in and around Delhi/NCR.
 6 |   - name: 💬 PyDelhi Telegram
 7 |     url: https://t.me/PyDelhi_official
 8 |     about: Please use the Telegram group to connect with fellow Pythonistas in and around Delhi/NCR.
 9 |   - name: Q/A Forum
10 |     url: https://github.com/orgs/pydelhi/discussions
11 |     about: Use the forum to ask questions about the meetup, help us with Sponsorship, or anything else.
12 | 


--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
 1 | # Created by https://www.gitignore.io
 2 | 
 3 | ### OSX ###
 4 | .DS_Store
 5 | .AppleDouble
 6 | .LSOverride
 7 | 
 8 | # Icon must end with two \r
 9 | Icon

10 | 
11 | # Thumbnails
12 | ._*
13 | 
14 | # Files that might appear in the root of a volume
15 | .DocumentRevisions-V100
16 | .fseventsd
17 | .Spotlight-V100
18 | .TemporaryItems
19 | .Trashes
20 | .VolumeIcon.icns
21 | 
22 | # Directories potentially created on remote AFP share
23 | .AppleDB
24 | .AppleDesktop
25 | Network Trash Folder
26 | Temporary Items
27 | .apdisk
28 | 
29 | 
30 | ### Linux ###
31 | *~
32 | 
33 | # KDE directory preferences
34 | .directory
35 | 
36 | # Linux trash folder which might appear on any partition or disk
37 | .Trash-*
38 | 
39 | 


--------------------------------------------------------------------------------
/assets/js/youtube.js:
--------------------------------------------------------------------------------
 1 | // Asynchronously load the YouTube API
 2 | var tag = document.createElement('script');
 3 | tag.src = 'https://www.youtube.com/iframe_api';
 4 | var firstScriptTag = document.getElementsByTagName('script')[0];
 5 | firstScriptTag.parentNode.insertBefore(tag, firstScriptTag);
 6 | 
 7 | // Creates an <iframe> (and YouTube player) after the YouTube API is loaded
 8 | var player;
 9 | function onYouTubeIframeAPIReady() {
10 |     player = new YT.Player('player', {
11 |         height: calculatePlayerHeight().toString(),
12 |         width: '100%',
13 |         videoId: null
14 |     });
15 | 
16 |     $(window).resize(function() {
17 |         var newPlayerHeight = calculatePlayerHeight();
18 |         player.setSize('100%', newPlayerHeight);
19 |     });
20 | }
21 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # PyDelhi Talks
2 | 
3 | Thank you for your interest in speaking at PyDelhi meetups! We are excited to hear your ideas and learn from your experiences. To propose a talk, please [create a new issue and fill out the questionnaire](https://github.com/pydelhi/talks/issues/new?template=talk-proposal.yaml).
4 | 
5 | 
6 | ## Licensing information
7 | 
8 | <img align="left" src="static/CC-by-NC-SA.png" width="300" style="padding-right:1em"/> Talks delivered at PyDelhi events under the [Creative Commons Attribution-Non Commercial-ShareAlike (CC BY-NC-SA) 4.0 International](https://creativecommons.org/licenses/by-nc-sa/4.0/) license, unless specified otherwise in the speaking material or in the description. This means you can share and adapt the content for non-commercial purposes, as long as you give appropriate credit to the presenter, provide a link to the license, and indicate if changes were made. You must also distribute your contributions under the same license as the speaker, or adapt to a compatible license based on the rights granted by the speaker and the regulations that apply to the content you create.


--------------------------------------------------------------------------------
/assets/js/main.js:
--------------------------------------------------------------------------------
 1 | $(document).ready(function() {
 2 |     initEventHandlers();
 3 | });
 4 | 
 5 | /**
 6 |  * Setup all the custom event handling of buttons etc. required.
 7 |  */
 8 | function initEventHandlers() {
 9 |     // The close button of the video player container
10 |     $('#video-player-container-dismiss').click(function() {
11 |         $('#video-player-container').addClass('hide');
12 |         if (player) {
13 |             player.stopVideo();
14 |         }
15 |     });
16 | }
17 | 
18 | /**
19 |  * Returns what the height of the YouTube player container should be,
20 |  * given its current width.
21 |  *
22 |  * By default, a 16:9 aspect ratio is used.
23 |  */
24 | function calculatePlayerHeight(aspectRatio) {
25 |     if (!aspectRatio) {
26 |         aspectRatio = 9.0 / 16.0;
27 |     }
28 |     var playerWidth = $('.container.video-player-container').width();
29 |     var playerHeight = playerWidth * aspectRatio;
30 |     return playerHeight;
31 | }
32 | 
33 | $(window).resize(function() {
34 |     var newPlayerHeight = calculatePlayerHeight();
35 |     if (player) {
36 |         player.setSize('100%', newPlayerHeight);
37 |     }
38 | });
39 | 


--------------------------------------------------------------------------------
/old_videos.json:
--------------------------------------------------------------------------------
 1 | [
 2 |     {
 3 |       "title": "Contributing to Mozilla Marionette & Firefox UI Tests",
 4 |       "presenter": "Sanyam Khurana",
 5 |       "year": 2016,
 6 |       "venue": "PyDelhi",
 7 |       "slides": "http://www.sanyamkhurana.com/marionette-intro/#/",
 8 |       "videos": {
 9 |         "youtube": "https://www.youtube.com/watch?v=l1tZaud0GO4"
10 |       },
11 |       "tags": ["web", "python", "testing", "mozilla"]
12 |     },
13 |     {
14 |       "title": "Testing 101",
15 |       "presenter": "Saurabh Kumar",
16 |       "year": 2015,
17 |       "venue": "PyDelhi",
18 |       "slides": "http://bit.ly/testing-101",
19 |       "videos": {
20 |         "youtube": "https://www.youtube.com/watch?v=_pX8LaMKNBk"
21 |       },
22 |       "tags": ["testing", "pytest"]
23 |     },
24 |     {
25 |       "title": "Prospector",
26 |       "presenter": "Anurag Sharma",
27 |       "year": 2015,
28 |       "venue": "PyDelhi",
29 |       "slides": "http://bit.ly/prospector-talk",
30 |       "videos": {
31 |         "youtube": "https://www.youtube.com/watch?v=CnUvdSusebE"
32 |       },
33 |       "tags": ["prospector", "static", "analysis"]
34 |     },
35 |     {
36 |       "title": "Moving from Django to Pyramid",
37 |       "presenter": "Pankaj Singh",
38 |       "year": 2015,
39 |       "venue": "PyDelhi",
40 |       "slides": "http://bit.ly/django2pyramid",
41 |       "videos": {
42 |         "youtube": "https://www.youtube.com/watch?v=a2Llc1EGGA4"
43 |       },
44 |       "tags": ["web", "pyramid", "django"]
45 |     }
46 |   ]
47 |   


--------------------------------------------------------------------------------
/assets/js/controller.js:
--------------------------------------------------------------------------------
 1 | var pyDelhiTalksApp = angular.module('pyDelhiTalksApp', []);
 2 | 
 3 | pyDelhiTalksApp.controller('VideoListCtrl', function($scope, $http, $sce) {
 4 |     $scope.currentVideo = null;
 5 | 
 6 |     $http.get('./videos.json').success(function (data) {
 7 |         $scope.videos = data;
 8 |         if ($scope.videos.length > 0) {
 9 |             $scope.currentVideo = $scope.videos[0];
10 |         }
11 |     });
12 | 
13 |     $scope.youtubeIdFromUri = function(uri) {
14 |         var re = /v=([a-z0-9_\-]+)/i;
15 |         var match = uri.match(re);
16 |         var id = match[1];
17 |         return id;
18 |     }
19 | 
20 |     $scope.youtubeThumbnail = function(uri) {
21 |         var id = $scope.youtubeIdFromUri(uri);
22 |         return 'http://i.ytimg.com/vi/' + id + '/mqdefault.jpg';
23 |     }
24 | 
25 |     $scope.youtubeEmbed = function(uri) {
26 |         var id = $scope.youtubeIdFromUri(uri);
27 |         console.log(id);
28 |         return 'http://www.youtube.com/embed/' + id;
29 |     }
30 | 
31 |     $scope.currentVideoUri = function() {
32 |         if ($scope.currentVideo !== null) {
33 |             var uri = $scope.currentVideo.videos.youtube;
34 |             return $sce.trustAsResourceUrl(uri);
35 |         }
36 |     }
37 | 
38 |     $scope.setCurrentVideo = function(videoObject) {
39 |         $scope.currentVideo = videoObject;
40 |     }
41 | 
42 |     $scope.selectVideo = function(videoObject) {
43 |         $scope.setCurrentVideo(videoObject);
44 |         if (player) {
45 |             var currentVideoId = $scope.youtubeIdFromUri($scope.currentVideo.videos.youtube);
46 |             player.loadVideoById(currentVideoId);
47 |         }
48 |         $('#video-player-container').removeClass('hide');
49 |         $('html, body').animate({ scrollTop: 0 }, 150);
50 |     }
51 | });
52 | 


--------------------------------------------------------------------------------
/assets/css/main.css:
--------------------------------------------------------------------------------
 1 | body {
 2 |   background-color: #f1f1f1;
 3 | }
 4 | 
 5 | [ng\:cloak],
 6 | [ng-cloak],
 7 | [data-ng-cloak],
 8 | [x-ng-cloak],
 9 | .ng-cloak,
10 | .x-ng-cloak {
11 |   display: none !important;
12 | }
13 | 
14 | .well-xxsm {
15 |   padding: 0;
16 | }
17 | 
18 | .well-video-container {
19 |   background-color: #fefefe;
20 |   border: 0;
21 |   height: 400px;
22 |   -webkit-box-shadow: 1px 1px 5px 1px rgba(0, 0, 0, 0.1);
23 |   box-shadow: 1px 1px 5px 1px rgba(0, 0, 0, 0.1);
24 | }
25 | 
26 | .video-container-title {
27 |   padding: 15px;
28 |   text-align: center;
29 |   font-weight: bold;
30 |   font-size: 1.4em;
31 | }
32 | 
33 | .video-container-thumbnail {
34 |   filter: alpha(opacity=50);
35 |   opacity: 0.5;
36 |   -webkit-transition: opacity 0.2s ease-in-out;
37 |   -moz-transition: opacity 0.2s ease-in-out;
38 |   transition: opacity 0.2s ease-in-out;
39 | }
40 | 
41 | .video-container-thumbnail:hover {
42 |   filter: alpha(opacity=100);
43 |   opacity: 1;
44 |   cursor: pointer;
45 | }
46 | 
47 | .video-container-info {
48 |   padding: 15px;
49 |   text-align: center;
50 |   font-size: 1em;
51 | }
52 | 
53 | .video-container-presenter {
54 |   font-size: 0.8em;
55 | }
56 | 
57 | .video-player-container {
58 |   background-color: #424242;
59 |   padding: 20px 10px;
60 |   top: 0;
61 |   bottom: 0;
62 |   left: 0;
63 |   right: 0;
64 |   position: absolute;
65 |   z-index: 10;
66 | }
67 | .jumbotron {
68 |   margin-bottom: 0;
69 | }
70 | 
71 | .jumbotron-close {
72 |   float: right;
73 |   font-size: 40px;
74 |   line-height: 1;
75 |   color: #fefefe;
76 |   filter: alpha(opacity=20);
77 |   opacity: 0.2;
78 | }
79 | 
80 | .jumbotron-close:hover,
81 | .jumbotron-close:focus {
82 |   color: #fefefe;
83 |   text-decoration: none;
84 |   cursor: pointer;
85 |   filter: alpha(opacity=100);
86 |   opacity: 1;
87 | }
88 | 
89 | button.jumbotron-close {
90 |   -webkit-appearance: none;
91 |   margin: -10px 15px 0 0;
92 |   padding: 0;
93 |   cursor: pointer;
94 |   background: transparent;
95 |   border: 0;
96 | }
97 | 


--------------------------------------------------------------------------------
/.github/workflows/stale.yml:
--------------------------------------------------------------------------------
 1 | # Mark proposals as inactive after 60 days of inactivity;
 2 | # See https://github.com/actions/stale for more on configuration
 3 | 
 4 | name: Mark open talk proposals as inactive
 5 | on:
 6 |   schedule:
 7 |     #        ┌───────────── minute (0 - 59)
 8 |     #        │  ┌───────────── hour (0 - 23)
 9 |     #        │  │  ┌───────────── day of the month (1 - 31)
10 |     #        │  │  │  ┌───────────── month (1 - 12 or JAN-DEC)
11 |     #        │  │  │  │ ┌───────────── day of the week (0 - 6 or SUN-SAT)
12 |     #        │  │  │  │ │
13 |     - cron: "0 3 15,* * 6" # 0300 UTC on day 15 of the month and every Saturday
14 |   workflow_dispatch:
15 | 
16 | permissions: {}
17 | 
18 | jobs:
19 |   stale:
20 |     permissions:
21 |       issues: write
22 |     runs-on: ubuntu-latest
23 |     steps:
24 |       - uses: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639 # v9.1.0
25 |         with:
26 |           days-before-stale: 60 # corresponds to two months/meetups
27 |           days-before-close: -1 # never close any issues; we'll do this manually.
28 |           stale-issue-label: "inactive"
29 |           remove-stale-when-updated: true
30 |           stale-issue-message: |
31 |             Hi there! This proposal has been automatically marked as "inactive" due to it
32 |             not receiving any activity for the last sixty days.
33 | 
34 |             To you as a contributor to the PyDelhi community, thank you for your proposal
35 |             and apologies if this issue fell through the cracks! This ping was created to
36 |             help bring this proposal a fresh pair of eyes. If you need any help, you can
37 |             always reach out here on this issue, or email us at
38 |             [pydelhi.org@gmail.com](mailto:pydelhi.org@gmail.com).
39 | 
40 |             If you think that this talk is no longer relevant, or that you are no longer
41 |             available to deliver this talk at one of our meetups in the coming time, you
42 |             may either close this issue, or the currently active volunteers shall do it
43 |             at some point in the future. If you are still interested in delivering this
44 |             talk, please comment on this issue to indicate your interest, and the
45 |             "inactive" label will be dropped automatically.
46 | 
47 |             If you are a volunteer for the PyDelhi community, and if you no longer have
48 |             the bandwidth to dedicate to reviewing this proposal, please consider
49 |             reaching out to your fellow volunteers to help you with this proposal on the
50 |             appropriate communication channels.
51 | 
52 |             If this issue is not a talk proposal, please ignore this message, remove the
53 |             "inactive" label, and either continue with your work here as planned or
54 |             close this issue if it is no longer relevant.
55 | 


--------------------------------------------------------------------------------
/videos.json:
--------------------------------------------------------------------------------
  1 | [
  2 |   {
  3 |     "title": "Unleash the Power of Python: Automated Testing for Units, Functions, and APIs",
  4 |     "presenter": "Dr. Shailendra Pratap Singh",
  5 |     "year": 2023,
  6 |     "venue": "PyDelhiConf",
  7 |     "slides": "",
  8 |     "videos": {
  9 |       "youtube": "https://www.youtube.com/watch?v=XtZZhq2rg10&t=336s"
 10 |     },
 11 |     "tags": [
 12 |       "python",
 13 |       "pytest",
 14 |       "testing",
 15 |       "quality-assurance",
 16 |       "automation"
 17 |     ]
 18 |   },
 19 |   {
 20 |     "title": "Data Visualisation in Python",
 21 |     "presenter": "Jaidev Deshpande",
 22 |     "year": 2023,
 23 |     "venue": "PyDelhiConf",
 24 |     "slides": "",
 25 |     "videos": {
 26 |       "youtube": "https://www.youtube.com/watch?v=f0XcIYHTm2A"
 27 |     },
 28 |     "tags": [
 29 |       "python",
 30 |       "data-visualisation",
 31 |       "matplotlib",
 32 |       "pandas",
 33 |       "numpy",
 34 |       "data-analysis"
 35 |     ]
 36 |   },
 37 |   {
 38 |     "title": "Sanic Unleashed: Mastering Asynchronous Unit Testing in Python",
 39 |     "presenter": "Akshita Dixit",
 40 |     "year": 2023,
 41 |     "venue": "PyDelhiConf",
 42 |     "slides": "",
 43 |     "videos": {
 44 |       "youtube": "https://www.youtube.com/watch?v=WZait-ZMki0"
 45 |     },
 46 |     "tags": [
 47 |       "python",
 48 |       "unit-testing",
 49 |       "asynchronous-testing",
 50 |       "sanic-framework"
 51 |     ]
 52 |   },
 53 |   {
 54 |     "title": "Making apps with Kivy",
 55 |     "presenter": "Akshay Aurora",
 56 |     "year": 2023,
 57 |     "venue": "PyDelhiConf",
 58 |     "slides": "",
 59 |     "videos": {
 60 |       "youtube": "https://www.youtube.com/watch?v=dirM8vMb8XY"
 61 |     },
 62 |     "tags": [
 63 |       "python",
 64 |       "kivy",
 65 |       "app-development"
 66 |     ]
 67 |   },
 68 |   {
 69 |     "title": "Scaling ML Models on SageMaker",
 70 |     "presenter": "Sanjay Kumar Tiwary",
 71 |     "year": 2023,
 72 |     "venue": "PyDelhiConf",
 73 |     "slides": "",
 74 |     "videos": {
 75 |       "youtube": "https://www.youtube.com/watch?v=igUYTKmT1vg"
 76 |     },
 77 |     "tags": [
 78 |       "scaling",
 79 |       "amazon-sagemaker",
 80 |       "ml-models",
 81 |       "mlops"
 82 |     ]
 83 |   },
 84 |   {
 85 |     "title": "Creating a distributed Key Value store",
 86 |     "presenter": "Shubham Upreti",
 87 |     "year": 2022,
 88 |     "venue": "PyDelhi Meetup",
 89 |     "slides": "https://github.com/pydelhi/talks/issues/196",
 90 |     "videos": {
 91 |       "youtube": "https://www.youtube.com/watch?v=s8mXsJPi5y4"
 92 |     },
 93 |     "tags": [
 94 |       "web",
 95 |       "python",
 96 |       "distributed",
 97 |       "key-value-store"
 98 |     ]
 99 |   },
100 |   {
101 |     "title": "GRPC in Python",
102 |     "presenter": "Dishant Sethi",
103 |     "year": 2022,
104 |     "venue": "PyDelhi Meetup",
105 |     "slides": "https://github.com/pydelhi/talks/issues/198",
106 |     "videos": {
107 |       "youtube": "https://www.youtube.com/watch?v=6h9I3iyqyu4"
108 |     },
109 |     "tags": [
110 |       "web",
111 |       "python",
112 |       "grpc",
113 |       "google"
114 |     ]
115 |   },
116 |   {
117 |     "title": "Finding high-impact performance bottlenecks in a Django app",
118 |     "presenter": "Puneet Gupta",
119 |     "year": 2022,
120 |     "venue": "PyDelhi Meetup",
121 |     "slides": "https://docs.google.com/presentation/d/1Elhcf6SbrsF_3ZoIHr66RoFvCsOt-5t8oXYO6Bpb084/edit#slide=id.p",
122 |     "videos": {
123 |       "youtube": "https://www.youtube.com/watch?v=hY8DA0klUHM"
124 |     },
125 |     "tags": [
126 |       "django",
127 |       "python",
128 |       "web",
129 |       "performance"
130 |     ]
131 |   },
132 |   {
133 |     "title": "Why Open Source?",
134 |     "presenter": "Daksh P Jain",
135 |     "year": 2022,
136 |     "venue": "PyDelhi Meetup",
137 |     "slides": "https://github.com/pydelhi/talks/issues/199",
138 |     "videos": {
139 |       "youtube": "https://www.youtube.com/watch?v=yumTOUH4sBI"
140 |     },
141 |     "tags": [
142 |       "open-source"
143 |     ]
144 |   }
145 | ]


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
  1 | <html lang="en" ng-app="pyDelhiTalksApp">
  2 |   <head>
  3 |     <meta charset="UTF-8" />
  4 |     <meta http-equiv="x-ua-compatible" content="ie=edge" />
  5 | 
  6 |     <title>Talks &#8226; PyDelhi</title>
  7 |     <meta name="description" content="Talks at Python Delhi User Group" />
  8 |     <meta name="viewport" content="width=device-width, initial-scale=1" />
  9 | 
 10 |     <link
 11 |       rel="stylesheet"
 12 |       href="https://cdnjs.cloudflare.com/ajax/libs/normalize/3.0.3/normalize.min.css"
 13 |     />
 14 |     <link
 15 |       href="https://fonts.googleapis.com/css?family=Roboto"
 16 |       rel="stylesheet"
 17 |     />
 18 |     <link
 19 |       href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css"
 20 |       rel="stylesheet"
 21 |     />
 22 |     <link href="https://pydelhi.org/assets/css/main.css" rel="stylesheet" />
 23 |     <link href="./assets/css/main.css" rel="stylesheet" />
 24 | 
 25 |     <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
 26 |     <!--[if lt IE 9]>
 27 |       <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
 28 |       <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
 29 |     <![endif]-->
 30 | 
 31 |     <script src="https://cdnjs.cloudflare.com/ajax/libs/angular.js/1.3.8/angular.min.js"></script>
 32 |     <script src="./assets/js/controller.js"></script>
 33 |   </head>
 34 | 
 35 |   <body class="page page-talks" ng-controller="VideoListCtrl">
 36 |     <div
 37 |       id="video-player-container"
 38 |       class="jumbotron video-player-container hide"
 39 |     >
 40 |       <button
 41 |         id="video-player-container-dismiss"
 42 |         type="button"
 43 |         class="jumbotron-close"
 44 |         data-dismiss="jumbotron"
 45 |         aria-label="Close"
 46 |       >
 47 |         <span aria-hidden="true">&#215;</span>
 48 |       </button>
 49 | 
 50 |       <div class="container video-player-container">
 51 |         <div id="player"></div>
 52 |       </div>
 53 |     </div>
 54 | 
 55 |     <div class="container">
 56 |       <!-- GitHub Fork Ribbon -->
 57 |       <a class="link--fork-on-github" href="https://github.com/pydelhi/talks">
 58 |         <img
 59 |           style="position: absolute; top: 0; right: 0; border: 0"
 60 |           src="https://pydelhi.org/assets/images/btn--fork-on-github.png"
 61 |           alt="Fork me on GitHub"
 62 |         />
 63 |       </a>
 64 | 
 65 |       <br />
 66 | 
 67 |       <div class="row">
 68 |         <div class="col-md-12">
 69 |           <div class="input-group input-group-lg">
 70 |             <span class="input-group-addon">
 71 |               <span
 72 |                 class="glyphicon glyphicon-search"
 73 |                 aria-hidden="true"
 74 |               ></span>
 75 |             </span>
 76 |             <input
 77 |               class="form-control"
 78 |               placeholder="Search"
 79 |               type="text"
 80 |               ng-model="query"
 81 |             />
 82 |           </div>
 83 |         </div>
 84 |       </div>
 85 | 
 86 |       <br />
 87 | 
 88 |       <div class="row" ng-cloak>
 89 |         <div
 90 |           class="col-md-3 col-sm-6"
 91 |           ng-repeat="video in videos | filter:query"
 92 |         >
 93 |           <div class="well well-xxsm well-video-container">
 94 |             <div class="video-container-title">{{video.title}}</div>
 95 | 
 96 |             <div class="video-container-thumbnail">
 97 |               <img
 98 |                 ng-src="{{youtubeThumbnail(video.videos.youtube)}}"
 99 |                 width="100%"
100 |                 ng-click="selectVideo(video)"
101 |               />
102 |             </div>
103 | 
104 |             <div class="video-container-info">
105 |               <p class="video-container-presenter">
106 |                 by {{video.presenter}} ({{video.venue}} {{video.year}})
107 |               </p>
108 |               <span
109 |                 class="label label-default"
110 |                 ng-repeat-start="tag in video.tags"
111 |                 >{{tag}}</span
112 |               >
113 |               <span ng-repeat-end></span>
114 |             </div>
115 |           </div>
116 |         </div>
117 |       </div>
118 |     </div>
119 |     <!-- /container -->
120 | 
121 |     <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
122 |     <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/js/bootstrap.min.js"></script>
123 |     <script src="./assets/js/main.js"></script>
124 |     <script src="./assets/js/youtube.js"></script>
125 |   </body>
126 | </html>
127 | 


--------------------------------------------------------------------------------
/guidelines.md:
--------------------------------------------------------------------------------
 1 | # Guidelines for Submitting a Proposal and Delivering an Impactful Talk
 2 | 
 3 | We're excited to welcome proposals for talks and presentations! Whether you're an experienced speaker or new to public speaking, these guidelines will help you submit a strong proposal and deliver an engaging and effective talk. Keep in mind that these are high-level guidelines, not hard and fast rules. The most important thing is to learn and have fun! And we are always here to support you through every step of the process! 
 4 | 
 5 | Please note that all talks are licensed under a [Creative Commons Attribution-Non Commercial-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-nc-sa/4.0/).
 6 | 
 7 | ---
 8 | 
 9 | ## Guidelines for Proposal Submission
10 | 
11 | ### 1. How We Select Proposals
12 | We have both 25-minutes (20 minutes for the talk, followed by a 5-minute Q&A) and 5-minutes (lightning) talks in our monthly meetups. Your talk proposal should be **Python-related**. Our audience consists largely of Python beginners, but advanced topics are also welcome if you explain them in a way that's accessible. If your topic requires specific knowledge, **clearly mention any prerequisites** in your proposal.
13 | 
14 | Even if your idea is still in development, submit a proposal! We're available to provide feedback and suggestions. Don't worry about communication skills or English fluency—our focus is on the content, and we're happy to help you refine your talk.
15 | 
16 | ### 2. Be Detailed
17 | Provide as much detail as possible in your proposal. If you already have slides or a brief video summarizing your talk, include them. More detail helps us better understand your talk and give it a fair evaluation. This also helps the audience understand what to expect.
18 | 
19 | ### 3. Submit Early
20 | We start reviewing proposals as soon as they come in, so the earlier you submit, the more time you'll have to receive feedback and refine your talk. Proposals submitted early tend to get more attention. Keep in mind that our **meetups are held on the third Saturday of each month**, so factor that into your availability.
21 | 
22 | ### 4. Clearly State Prerequisites
23 | If your talk requires prior knowledge or preparation, make sure to **state this clearly** in your proposal. Providing links to additional resources or reading material can also help the audience better prepare for your talk.
24 | 
25 | ### 5. Follow the Code of Conduct
26 | We have a strict [**Code of Conduct**](https://pydelhi.org/coc.html) that all speakers and participants must follow. Please take a moment to review it before submitting your proposal. Our community is committed to being welcoming, inclusive, and respectful, and we expect the same from all participants. Any form of derogatory or exclusionary language is not tolerated.
27 | 
28 | ---
29 | 
30 | ## Guidelines for Delivering an Engaging Talk
31 | 
32 | Here are some tips to help you effectively communicate your message and keep your audience engaged:
33 | 
34 | ### 1. Get to the Core Message Early
35 | Begin your talk by getting to the main point within the first 3-5 minutes. Avoid long introductions, as they tend to lose the audience's attention. Try to get the attention of the audience with an interesting title. 
36 | 
37 | For lightning talks (5 minutes), focus on sparking curiosity rather than covering every detail. If your talk has prerequisites, make sure the audience is aware upfront.
38 | 
39 | ### 2. Keep the Session Interactive
40 | Engagement is key. Make your presentation interactive by asking questions, encouraging participation, or conducting small activities throughout the talk. You can use tools for audience interaction to gather real-time feedback or conduct polls.
41 | 
42 | #### A. Use Real-Life Examples
43 | Simplify complex ideas by using real-life examples or analogies. This makes technical concepts easier to understand and more relatable to the audience. You can also stick to one motivating example that you can refer to throughout your talk. This helps maintain audience engagement and creates a clear narrative that ties all your points together.
44 | 
45 | #### B. Make the Presentation Visually Engaging
46 | Avoid text-heavy slides. Use visuals, diagrams, or videos to illustrate your points. Keep slide text to a minimum (4-5 lines max) and use images to support your message. Visual content helps convey information more effectively than blocks of text.
47 | 
48 | #### C. Add Humour Thoughtfully
49 | A well-timed joke or light comment can lighten the mood and help you connect with the audience really fast. However, make sure that your humour is appropriate and relevant to the context.
50 | 
51 | #### D. Having Code in Your Talk/Slides
52 | If done well, please include it. Otherwise, it could overwhelm the audience, as real-time tutorials during talks are usually not recommended by many. However, meetups are a safe space where you can try new things without judgment. We are very open to people experimenting with different formats and styles at our meetups.
53 | 
54 | #### E. Include Hooks to Encourage Conversation
55 | Add points/hooks in your talk that will encourage the audience to approach you after the talk for further discussion. This not only adds value to your talk but also creates opportunities for networking and deeper engagement with attendees.
56 | 
57 | ### 3. Use the Stage to Your Advantage
58 | Engage with the audience by moving around the stage and making eye contact. Moving with purpose helps keep the energy high and reduces the risk of losing your audience’s attention.
59 | 
60 | ### 4. Vary Your Tone and Pitch
61 | Keep your delivery lively by varying your tone and pitch. A monotone voice can easily lose the audience’s attention, while vocal variation can highlight key points and keep the audience engaged.
62 | 
63 | ### 5. Highlight The Best Practices
64 | When discussing code or technical processes, especially when demonstrating live coding, emphasize best practices such as **security** and **ethical coding**. For instance, never display sensitive data, like API keys, during your presentation.
65 | 
66 | ---
67 | 
68 | 
69 | **Courtesy**: Anand B. Pillai, Aditi Juneja
70 | 
71 | 
72 | Happy contributing!
73 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/talk-proposal.yaml:
--------------------------------------------------------------------------------
  1 | name: 🎙️ Talk proposal
  2 | description: Create a proposal for your talk at the PyDelhi monthly meetups here.
  3 | labels: ["proposal"]
  4 | body:
  5 |   - type: markdown
  6 |     attributes:
  7 |       value: |
  8 |         👋 Thanks for taking the time to share your learnings with the PyDelhi community!
  9 | 
 10 |         We would highly recommend you go through our [guidelines on submitting a proposal and presenting](../guidelines.md), **especially if it is your first time**.
 11 | 
 12 |         Please note that all talks are licensed under a [Creative Commons Attribution-Non Commercial-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-nc-sa/4.0/), unless you state otherwise and request the use of a different license of your choosing, either in your proposal below or in the materials you intend to share.
 13 | 
 14 |   - type: input
 15 |     id: title
 16 |     attributes:
 17 |       label: Talk title
 18 |       description: Please share a clear, engaging title for your talk
 19 |       placeholder: "e.g.; an introduction to machine learning with Python"
 20 |     validations:
 21 |       required: true
 22 | 
 23 |   - type: textarea
 24 |     id: description
 25 |     attributes:
 26 |       label: Short talk description
 27 |       description: Brief abstract about your talk (50-150 words). This will be used for our social media.
 28 |       placeholder: |
 29 |         Describe what your talk covers, who would benefit from it, and what key takeaways
 30 |         attendees can expect. This description will be used for promoting your event on social media.
 31 |     validations:
 32 |       required: true
 33 | 
 34 |   - type: textarea
 35 |     id: long-description
 36 |     attributes:
 37 |       label: Long talk description
 38 |       description: A longer version of a description about your talk (150-500 words).
 39 |       placeholder: |
 40 |         Add a longer description of your talk: similar to the previous one, but with more details.
 41 |     validations:
 42 |       required: true
 43 | 
 44 |   - type: dropdown
 45 |     id: format
 46 |     attributes:
 47 |       label: What format do you have in mind?
 48 |       description: Choose the format that best fits your content
 49 |       options:
 50 |         - Talk (20-25 minutes + Q&A)
 51 |         - Workshop (45-60 minutes, hands-on)
 52 |         - Lightning talk (5 minutes)
 53 |         - Sponsored talk (20-25 minutes, sponsored by a company or organization as part of a potential partnership or sponsorship arrangement via venue sharing, food and beverages, or other amenities for the event)
 54 |         - BoF (Birds of a Feather) session (30-45 minutes, open discussion or topic exploration with the audience)
 55 |         - Panel discussion (45-60 minutes with multiple speakers discussing a specific topic, followed by audience Q&A – please specify the panelists as well)
 56 |         - Other (please share more details in your proposal)
 57 |     validations:
 58 |       required: true
 59 | 
 60 |   - type: textarea
 61 |     id: outline
 62 |     attributes:
 63 |       label: Talk outline / Agenda
 64 |       description: "Please provide a brief outline of your talk's structure"
 65 |       placeholder: |
 66 |         Example:
 67 |         • Introduction to the problem (5 mins)
 68 |         • Core concepts and theory (10 mins)
 69 |         • Live demo/code walkthrough (15 mins)
 70 |         • Best practices and pitfalls (10 mins)
 71 |         • Q&A (10 mins)
 72 | 
 73 |         You may update this outline later as you prepare your talk.
 74 |     validations:
 75 |       required: true
 76 | 
 77 |   - type: textarea
 78 |     id: takeaways
 79 |     attributes:
 80 |       label: Key takeaways
 81 |       description: What will attendees learn or gain from your talk?
 82 |       placeholder: |
 83 |         Please 3-5 key takeaways that attendees can expect from your talk. Here are some rubrics:
 84 |         • Understanding of [concept/technology/approach]
 85 |         • Practical knowledge of [specific skill/technique]
 86 |         • Best practices for [relevant area]
 87 |         • Common pitfalls to avoid when [doing something]
 88 |         • Resources and next steps for further learning
 89 |     validations:
 90 |       required: true
 91 | 
 92 |   - type: dropdown
 93 |     id: domain
 94 |     attributes:
 95 |       label: What domain would you say your talk falls under?
 96 |       description: This helps us categorise and promote your talk to the right audience.
 97 |       options:
 98 |         - Core Python
 99 |         - Data Science and Machine Learning
100 |         - Web Development
101 |         - DevOps & Infrastructure
102 |         - CLI & Developer Tooling
103 |         - Testing & Quality Assurance
104 |         - Mobile Development
105 |         - Research & Academia
106 |         - Artificial Intelligence & Deep Learning
107 |         - Careers and Community
108 |         - Security
109 |         - Game Development
110 |         - Other/Miscellaneous
111 |     validations:
112 |       required: true
113 | 
114 |   - type: input
115 |     id: duration
116 |     attributes:
117 |       label: "Duration (including Q&A)"
118 |       description: "Please specify the total time needed for your talk, including a Q&A session"
119 |       placeholder: "For example: 30 minutes (20 minutes for the talk + 10 minutes for a Q&A session)"
120 |     validations:
121 |       required: true
122 | 
123 |   - type: textarea
124 |     id: prerequisites
125 |     attributes:
126 |       label: Prerequisites and preparation
127 |       description: What should attendees know or prepare beforehand?
128 |       placeholder: |
129 |         For example:
130 |         • Basic Python knowledge (functions, classes)
131 |         • Laptop with Python 3.8+ installed
132 |         • Familiarity with command line basics
133 |         • No prior experience with [specific technology] needed
134 | 
135 |         We usually have a diverse audience, so please keep in mind that not everyone may be familiar with advanced topics.
136 |         If your talk requires specific tools or libraries, please mention them here.
137 |         If you plan to do a live demo, please ensure you have tested it on the event setup beforehand.
138 |         If you feel you will need help with this, please let us know.
139 |     validations:
140 |       required: false
141 | 
142 |   - type: textarea
143 |     id: resources
144 |     attributes:
145 |       label: Resources and references
146 |       description: Any helpful resources for reviewers and attendees
147 |       placeholder: |
148 |         • Links to relevant documentation
149 |         • GitHub repositories
150 |         • Articles or papers
151 |         • Tools or libraries used
152 |     validations:
153 |       required: false
154 | 
155 |   - type: input
156 |     id: slides
157 |     attributes:
158 |       label: Link to slides/demos (if available)
159 |       description: Share any existing materials or work-in-progress
160 |       placeholder: "https://slides.com/... or https://github.com/..."
161 |     validations:
162 |       required: false
163 | 
164 |   - type: input
165 |     id: speaker-social-twitter
166 |     attributes:
167 |       label: "Twitter/X handle (optional)"
168 |       description: "Your Twitter/X handle for social media promotion and networking"
169 |       placeholder: "@yourusername"
170 |     validations:
171 |       required: false
172 | 
173 |   - type: input
174 |     id: speaker-social-linkedin
175 |     attributes:
176 |       label: "LinkedIn profile (optional)"
177 |       description: "Your LinkedIn profile for professional networking"
178 |       placeholder: "https://linkedin.com/in/yourusername"
179 |     validations:
180 |       required: false
181 | 
182 |   - type: input
183 |     id: speaker-pic
184 |     attributes:
185 |       label: "Profile picture URL (optional)"
186 |       description: "We'll use this for event posters and social media. You can use a professional photo, avatar, or any image you're comfortable with being public."
187 |       placeholder: "https://example.com/your-photo.jpg, GitHub profile picture, Gravatar, and so on"
188 |     validations:
189 |       required: false
190 | 
191 |   - type: textarea
192 |     id: about-author
193 |     attributes:
194 |       label: Speaker bio
195 |       description: Tell us about yourself! This will be used for speaker introductions and promotional materials.
196 |       placeholder: |
197 |         Include:
198 |         • Your background and current role
199 |         • Relevant experience with the talk topic
200 |         • Previous speaking experience (if any)
201 |         • Fun fact or personal interest
202 |         • How to reach you (email, social media)
203 | 
204 |         Don't worry if you're a first-time speaker – we welcome everyone!
205 |     validations:
206 |       required: true
207 | 
208 |   - type: input
209 |     id: availability
210 |     attributes:
211 |       label: Availability
212 |       description: When would you be available to give this talk? (PyDelhi meetups are typically organised on the third Saturday of each month)
213 |       placeholder: "Month/Year or specific dates (DD/MM/YYYY)"
214 |     validations:
215 |       required: true
216 | 
217 |   - type: textarea
218 |     id: accessibility
219 |     attributes:
220 |       label: Accessibility & special requirements
221 |       description: Are there any accessibility needs or special technical requirements for your talk?
222 |       placeholder: |
223 |         For example:
224 |         • Screen reader compatibility is needed
225 |         • Large font requirements
226 |         • Special AV equipment
227 |         • Dietary restrictions for the event day
228 |         • Any other accommodations
229 |     validations:
230 |       required: false
231 | 
232 |   - type: checkboxes
233 |     id: speaker-agreements
234 |     attributes:
235 |       label: Speaker checklist
236 |       description: "Please confirm the following agreements before submitting your proposal:"
237 |       options:
238 |         - label: "I have read and understood the [PyDelhi guidelines](https://github.com/pydelhi/talks/blob/main/guidelines.md) for submitting proposals and giving talks"
239 |           required: true
240 |         - label: "I will make my talk accessible to all attendees and will proactively ask for any accommodations or special requirements I might need"
241 |           required: true
242 |         - label: "I agree to share slides, code snippets, and other materials used during the talk with the community"
243 |           required: true
244 |         - label: "I will follow PyDelhi's Code of Conduct and maintain a welcoming, inclusive environment throughout my participation"
245 |           required: true
246 |         - label: "I understand that PyDelhi meetups are community-centric events focused on learning, knowledge sharing, and networking, and I will respect this ethos by not using this platform for self-promotion or hiring pitches during my presentation, unless explicitly invited to do so by means of a sponsorship or similar arrangement"
247 |           required: true
248 |         - label: "If the talk is recorded by the PyDelhi team, I grant permission to release the video on PyDelhi's YouTube channel under the CC-BY-4.0 license, or a different license of my choosing if I am specifying it in my proposal or with the materials I share"
249 |           required: false
250 | 
251 |   - type: textarea
252 |     id: comments
253 |     attributes:
254 |       label: Additional comments
255 |       description: Anything else you'd like us to know?
256 |       placeholder: |
257 |         • Are you a first-time speaker? We're here to help!
258 |         • Do you need mentorship or feedback on your talk?
259 |         • Special circumstances or considerations besides the ones stated above?
260 |         • Do you have any other questions about the process that do not fit the requests stated above?
261 |         • Did you find an issue with this questionnaire or have suggestions to improve it? Please let us know here or [open a separate issue](https://github.com/pydelhi/talks/issues/new?template=BLANK_ISSUE), and we will be happy to hear from you!
262 |     validations:
263 |       required: false
264 | 
265 |   - type: markdown
266 |     attributes:
267 |       value: |
268 |         ## What happens next?
269 | 
270 |         1. **Review process**: Our team will review your proposal as soon as possible.
271 |         2. **Feedback**: We may reach out for clarifications or suggestions
272 |         3. **Confirmation**: Once accepted, we'll coordinate the event logistics with you
273 |         4. **Support**: First-time speakers can seek mentorship and practice sessions, if needed. Just let us know!
274 | 
275 |         **Questions?** Reach out to us:
276 |         - 💬 [WhatsApp community](https://chat.whatsapp.com/IUA2o1Xu8w8LmaZ8bw0nbb)
277 |         - 📧 Email: pydelhi.org@gmail.com
278 |         - 💬 [Telegram](https://t.me/PyDelhi_official)
279 |         - or write to us below! :)
280 | 
281 |         ---
282 | 
283 |         **Improve this questionnaire:** Did you find a bug, or do you have suggestions? Please feel free to add them to the comments above or [open a separate issue](https://github.com/pydelhi/talks/issues/new?template=BLANK_ISSUE) as you prefer. We welcome contributions to improve this proposal form and the overall process!
284 | 
285 |         Thank you for contributing to the Python community in Delhi! 🐍❤️
286 | 
287 |         *This proposal form was inspired by and enhanced with ideas from [BangPypers](https://github.com/bangpypers). Thank you to the BangPypers community for sharing best practices!*
288 | 


--------------------------------------------------------------------------------