Open source inspired workflows  for open (and closed) geospatial data

Slide 1

Slide 1 text

! Open source inspired workflows   for open (and closed) geospatial data @benbalter [email protected] government.github.com

Slide 2

Slide 2 text

! 1. How open source got here 2. Where geodata is today 3. What data publishers can learn

Slide 3

Slide 3 text

! Open source ≠ published code

Slide 4

Slide 4 text

! Open source as a philosophy

Slide 5

Slide 5 text

! Open Source (software)  software that can be freely used, modified, and shared   (in both modified and unmodified form) by anyone

Slide 6

Slide 6 text

! Open Source  a philosophy of collaboration in which working materials are made available online for anyone to fork, modify, discuss, and contribute to.

Slide 7

Slide 7 text

! Open source as a workﬂow

Slide 8

Slide 8 text

! Open source workﬂows must be location- and time-agnostic

Slide 9

Slide 9 text

! Wikipedia v. Encyclopedia Britannica

Slide 10

Slide 10 text

! A brief history of   open source tooling

Slide 11

Slide 11 text

! In the beginning, we had drawers

Slide 12

Slide 12 text

PDP-1 (or so I’m told)

Slide 13

Slide 13 text

Open source at the Tech Model Railroad Club

Slide 14

Slide 14 text

! We eventually upgraded to email

Slide 15

Slide 15 text

! ...and FTP

Slide 16

Slide 16 text

! ...and the read-only web

Slide 17

Slide 17 text

! 1. Had to be there 2. Had to know them 3. Had to be perfect

Slide 18

Slide 18 text

! This is where (geo)data is today

Slide 19

Slide 19 text

! Computering is hard

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

! You are constantly one character away from crashing the entire site

Slide 22

Slide 22 text

Version Control * 2d96cfe - (HEAD, tag: v3.1.1, origin/master, origin/HEAD, master) :gem: bump (43 minutes ago) * f4b446b - remove stray backtick (44 minutes ago) * 83599e3 - Merge branch 'master' of https://github.com/benbalter/g-man (46 minutes ago) |\ | * 42514ea - Merge pull request #61 from devscott/laxco (50 minutes ago) | |\ | | * 072d9b5 - Adding in additional entry for La Crosse County, WI (54 minutes ago) | |/ * | 1e95d95 - remove unresolvable domains (46 minutes ago) * | 1a8645a - remove uwyo.edu/CES (86 minutes ago) |/ * 70410ba - Merge pull request #60 from jpmckinney/canada (2 hours ago) |\ | * a77ad43 - Use consistent comments for Canada hosts (2 hours ago) | * 1776e45 - Add more Canadian hosts (2 hours ago) * | 05211a0 - Merge pull request #58 from mitio/bulgarian-government-domains (3 hours ago) |\ \ | * | fe8f862 - Add Bulgaria's government main domain (3 hours ago) | |/ * | 85d0c7b - Merge pull request #59 from mitio/fix-readme-typos (3 hours ago) |\ \ | |/ |/| | * f558a90 - Add missing word in the readme (3 hours ago)

Slide 23

Slide 23 text

! Version control tracks who made what change when

Slide 24

Slide 24 text

! Author publishes User downloads User ﬁnds a bug User submits   a patch

Slide 25

Slide 25 text

! Is this a bug? Has anyone else experienced this? Is this the best solution?  Can someone help test this? Can you release a new version with the ﬁx? Email all the things!

Slide 26

Slide 26 text

! The instructions to contribute to the linux kernel is 50,000 words

Slide 27

Slide 27 text

! Collaborative version control Decentralized & social

Slide 28

Slide 28 text

! Decentralized Everyone has the opportunity to contribute

Slide 29

Slide 29 text

! Social Everything happens in the open and by people

Slide 30

Slide 30 text

! Standardized Don't need to RTFM

Slide 31

Slide 31 text

! Captures and exposes process Proposed alternatives, what decision was made, why

Slide 32

Slide 32 text

! Is this a bug? Has anyone else experienced this? Is this the best solution?  Can someone help test this? Can you release a new version with the ﬁx? (Google and then) post all the things!

Slide 33

Slide 33 text

! "Anyone is encouraged to contribute to the project by forking and submitting a pull request. (If you are new to GitHub, you might start with a basic tutorial.)" Contributing to whitehouse/petitions

Slide 34

Slide 34 text

! Open source ≠ published code

Slide 35

Slide 35 text

! Open source ≠ published code

Slide 36

Slide 36 text

! Open source ≠ published code

Slide 37

Slide 37 text

! Three lessons geodata can   learn from open source

Slide 38

Slide 38 text

! 1. Prefer open formats to increase potential for data consumers

Slide 39

Slide 39 text

! Purpose-built, proprietary tools

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

Shapeﬁle GeoJSON

Slide 42

Slide 42 text

! 2. Adopt shared standards

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

! Foster Open standards

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

! 3. Free tightly held data

Slide 47

Slide 47 text

! Published data

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

! Open data

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

! Collaborative data

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

! Bonus: collaborative tools

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

! Your ﬁrst (or second) step

Slide 56

Slide 56 text

! Don't make multi-year, multi-million dollar investments on a hunch for what developers might ﬁnd useful

Slide 57

Slide 57 text

! 1. Establish a "data" repository

Slide 58

Slide 58 text

! 2. Publish all the data you can

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

! Open source inspired workflows   for open (and closed) geospatial data @benbalter [email protected] government.github.com

Slide 64

Slide 64 text

‣ PDP-1 — flickr.com/photos/hiddenloop/307119987/ ‣ Punch Card Decks — mehul panchal, via Wikimedia Commons Photo credits