manual checking

pycon-au-2016/videos/a-proof-of-concept-python-toolkit-for-effective-landscape-fuel-hazard-management.json

@@ -10,7 +10,10 @@
   "speakers": [
     "Henry Walshaw"
   ],
-  "tags": [],
+  "tags": [
+    "ArcGIS",
+    "Pandas"
+  ],
   "thumbnail_url": "https://i.ytimg.com/vi/3wLk9jHB7to/maxresdefault.jpg",
   "title": "A proof of concept Python toolkit for effective landscape fuel hazard management",
   "videos": [

pycon-au-2016/videos/automated-deployment-of-python-packages-for-development.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "Creative Commons Attribution license (reuse allowed)",
-  "description": "Andrew MacDonald\nhttps://2016.pycon-au.org/schedule/109/view_talk\nThe ability to automatically deploy development and test versions of software supports a rapid development/release cycle.\n\nWithin our section of the Bureau of Meteorology we have a number of internal Python packages, ranging from small simple packages to large applications that are dependent on the smaller packages. We manage the development cycle to ease deployment of these packages and applications into development, test, and production environments.\n\nElements of our process are:     * Source code management (git)     * Code review (Gerrit)     * Continuous integration (Jenkins)     * Internal PyPi servers (Apache)     * A development environment for automatic deployment of every Gerrit approved commit (Anaconda environment via Jenkins)     * Versioning (git tags + versioneer)     * Test environment for every tagged version (Anaconda environment via Jenkins)     * Production environment for specified releases (Anaconda environment via Ansible)\n\nA key benefit of this process is that we have a deployed Python environment for the latest development version of all packages, a pinned collection of packages for testing, and an approved stable collection for production. The development and test environments are rapidly updated when commits are approved in Gerrit or tagged. The production environment is then readily updated with specific versions after a period of testing in the test environment.\nThis presentation will discuss our development process, how it works for us and how we leverage Python packaging to do it.",
+  "description": "Andrew MacDonald\n\nhttps://2016.pycon-au.org/schedule/109/view_talk\n\nThe ability to automatically deploy development and test versions of software supports a rapid development/release cycle.\n\nWithin our section of the Bureau of Meteorology we have a number of internal Python packages, ranging from small simple packages to large applications that are dependent on the smaller packages. We manage the development cycle to ease deployment of these packages and applications into development, test, and production environments.\n\nElements of our process are: \n    \n* Source code management (git)     \n* Code review (Gerrit)     \n* Continuous integration (Jenkins)     \n* Internal PyPi servers (Apache)     \n* A development environment for automatic deployment of every Gerrit approved commit (Anaconda environment via Jenkins)     \n* Versioning (git tags + versioneer)     \n* Test environment for every tagged version (Anaconda environment via Jenkins)     \n* Production environment for specified releases (Anaconda environment via Ansible)\n\nA key benefit of this process is that we have a deployed Python environment for the latest development version of all packages, a pinned collection of packages for testing, and an approved stable collection for production. The development and test environments are rapidly updated when commits are approved in Gerrit or tagged. The production environment is then readily updated with specific versions after a period of testing in the test environment.\n\nThis presentation will discuss our development process, how it works for us and how we leverage Python packaging to do it.",
   "duration": 2220,
   "language": "eng",
   "recorded": "2016-08-15",

pycon-au-2016/videos/click-a-pleasure-to-write-a-pleasure-to-use.json

@@ -10,7 +10,9 @@
   "speakers": [
     "Sebastian Vetter"
   ],
-  "tags": [],
+  "tags": [
+    "click"
+  ],
   "thumbnail_url": "https://i.ytimg.com/vi/bsJFMtQ5MZU/maxresdefault.jpg",
   "title": "Click: A Pleasure To Write, A Pleasure To Use",
   "videos": [

pycon-au-2016/videos/comparing-wagtail-django-cms-and-mezzanine.json

@@ -11,7 +11,10 @@
     "Adam Brenecki"
   ],
   "tags": [
-    "django"
+    "django",
+    "django cms",
+    "mezzanine",
+    "wagtail"
   ],
   "thumbnail_url": "https://i.ytimg.com/vi/3UC1MNFOjEI/maxresdefault.jpg",
   "title": "Comparing Wagtail, Django CMS and Mezzanine",

pycon-au-2016/videos/designing-hardware-with-python-a-story-of-the-hdmi2usbtv-project.json

@@ -1,6 +1,6 @@
 {
   "copyright_text": "Creative Commons Attribution license (reuse allowed)",
-  "description": "Timothy Ansell\nhttps://2016.pycon-au.org/schedule/25/view_talk\nPython is generally considered a high level language a long way from hardware, this very fact actually makes it an awesome tool for helping out with the design and creation of hardware!\n\nThis talk will hopefully cover;\n* Python hardware description languages (HDLs) for creating \"gateware\" for FPGA chips or even real IC design.\n* Python scripting for hardware schematic layout and design rule checking.\n* Python tools for deploying, programming and debugging embedded systems.\n* Some cool projects like the HDMI2USB.tv (open source hardware for video capture) which use many of the above parts.\n\nThis talk will focus on open source tools.",
+  "description": "Timothy Ansell\n\nhttps://2016.pycon-au.org/schedule/25/view_talk\n\nPython is generally considered a high level language a long way from hardware, this very fact actually makes it an awesome tool for helping out with the design and creation of hardware!\n\nThis talk will hopefully cover;\n\n* Python hardware description languages (HDLs) for creating \"gateware\" for FPGA chips or even real IC design.\n* Python scripting for hardware schematic layout and design rule checking.\n* Python tools for deploying, programming and debugging embedded systems.\n* Some cool projects like the HDMI2USB.tv (open source hardware for video capture) which use many of the above parts.\n\nThis talk will focus on open source tools.",
   "duration": 1994,
   "language": "eng",
   "recorded": "2016-08-15",

pycon-au-2016/videos/django-drupal-a-tale-of-two-cities.json

@@ -11,7 +11,8 @@
     "Donna Benjamin"
   ],
   "tags": [
-    "django"
+    "django",
+    "drupal"
   ],
   "thumbnail_url": "https://i.ytimg.com/vi/dc7AvdDM5FA/maxresdefault.jpg",
   "title": "Django & Drupal: A tale of two cities.",

pycon-au-2016/videos/djangoconf-lightning-talks-and-closing.json

@@ -7,7 +7,8 @@
   "related_urls": [],
   "speakers": [],
   "tags": [
-    "django"
+    "django",
+    "Lightning Talks"
   ],
   "thumbnail_url": "https://i.ytimg.com/vi/ss1X-FqPEzU/maxresdefault.jpg",
   "title": "DjangoConf Lightning Talks and Closing",

pycon-au-2016/videos/pyrobuf-and-the-tyranny-of-speed.json

@@ -10,7 +10,9 @@
   "speakers": [
     "Gregory Saunders"
   ],
-  "tags": [],
+  "tags": [
+    "pyrobuf"
+  ],
   "thumbnail_url": "https://i.ytimg.com/vi/4Q7hDdCYppw/maxresdefault.jpg",
   "title": "Pyrobuf and the Tyranny of Speed",
   "videos": [

pycon-au-2016/videos/saturday-lightning-talks.json

@@ -7,7 +7,9 @@
   "related_urls": [],
   "slug": "pycon-au-2016-saturday-lightning-talks",
   "speakers": [],
-  "tags": [],
+  "tags": [
+    "Lightning Talks"
+  ],
   "thumbnail_url": "https://i.ytimg.com/vi/xJ1-QdatS9Q/maxresdefault.jpg",
   "title": "Saturday: Lightning Talks",
   "videos": [

pycon-au-2016/videos/sunday-lightning-talks-and-closing.json

@@ -6,7 +6,9 @@
   "recorded": "2016-08-15",
   "related_urls": [],
   "speakers": [],
-  "tags": [],
+  "tags": [
+    "Lightning Talks"
+  ],
   "thumbnail_url": "https://i.ytimg.com/vi/vgbZInw6rNM/maxresdefault.jpg",
   "title": "Sunday: Lightning Talks and Closing",
   "videos": [