Open Data is only the Beginning - Open Belgium 2017

The rise of Open Data is only the beginning in becoming a thoroughly Open City. This session will highlight 10 hands-on principles of being an Open City through the use of modern and open technologies.

Based on the concepts of Open Development, Open Data & Open Source and illustrated using existing efforts from various governments.If you need inspiration to introduce open efforts in your city or want to improve your city's efforts then this is the session you need to attend.

Transcript

1. Open Data is only the Beginning
   An Open City Government talk beyond Open Data on
   Open Development & Open Source.
   Open Belgium
   6 March 2017, Brussels
   

   View Slide

2. Johan Janssens
   Make.Good.Code
   www.timble.net - @johanjanssens
   I'm a Belgian web developer,
   free software advocate,
   chief breaker of things @Timble.
   

   View Slide

3. 3% of sites on internet
   build solely by volunteers
   

   View Slide

4. An open source web publishing platform used by 65 local police forces & federal police.
   Open Police
   

   View Slide

5. Making a city open beyond data ...
   https://flic.kr/p/nDzaE3
   

   View Slide

6. http://opendefinition.org/
   The Open Definition initially derived from
   the Open Source Definition.
   “Open data and content can be freely
   used, modified, and shared by
   anyone for any purpose”
   

   View Slide

7. Open City Government
   https://flic.kr/p/9KR59t
   

   View Slide

8. [City] is committed to:
   ● Transparency
   ● Meaningful public participation
   ● Collaborating with public and across government
   ● Sharing best practices, software and resources
   http://opengovernmentinitiative.org/declaration-of-local-open-government-principles/
   

   View Slide

9. An open city must create a legal
   framework that will institutionalize the
   principles of transparency,
   participation, and collaboration into
   its culture and work.
   http://opengovernmentinitiative.org/declaration-of-local-open-government-principles/
   Open City Directive
   

   View Slide

10. Why?
    https://flic.kr/p/eQtasQ
    

    View Slide

11. Builds trust
    Being open about code, and the processes which lead
    to coding decisions, are vital parts of building trust in
    government.
    

    View Slide

12. Increases transparency
    Coding in the open allows the public to see how public
    money is being spent.
    

    View Slide

13. Potential for reuse
    Work together and reuse solutions from other government
    services rather than re-writing the wheel.
    

    View Slide

14. Makes it better
    The more eyes there are on a service the better it gets.
    Howlers are spotted, better alternatives are pointed out,
    the bar is raised.
    

    View Slide

15. Helps to find great people
    Developers can see the quality and style of code
    produced, the types of technologies, and the kinds of
    services delivered.
    

    View Slide

16. How?
    https://flic.kr/p/qhd2dh
    

    View Slide

17. www.gov.uk/service-manual/service-standard & www.dta.gov.au/standard/
    Create a 'Digital Service Standard'
    Set of criteria to create and run digital services.
    

    View Slide

18. Digital Service Standard of GOV.UK:
    1. Understand user needs
    4. Use agile methods
    5. Iterate and improve frequently
    8. Make all new source code open
    9. Use open standards and common platforms
    www.gov.uk/service-manual/service-standard
    

    View Slide

19. www.cgi-group.co.uk/cgi-successfully-awarded-a-place-on-the-governments-digital-services-framework
    Outsourcing suppliers must comply
    with the Digital Service Standard
    It took us 6 months to negotiate a contract to deliver
    open source software to the Belgian Police.
    

    View Slide

20. https://github.com
    Use GitHub
    The largest open source community in the world.
    

    View Slide

21. government.github.com/community/
    Who’s using GitHub?
    Add your organisation ...
    

    View Slide

22. https://pages.18f.gov/open-source-guide/making-readmes-readable/
    Start with a README
    The first thing a user will see when encountering your code.
    

    View Slide

23. https://github.com/tinkkit/tink-core/blob/master/README.md
    

    View Slide

24. https://pages.18f.gov/open-source-guide/writing-clear-and-concise-issues/
    Create issues
    Tasks that need to be completed or discussed are
    added to repositories as issues.
    

    View Slide

25. https://github.com/Fedict/eid-viewer/issues
    

    View Slide

26. https://en.wikipedia.org/wiki/Coding_conventions
    Use coding standards
    Reduce the cost of maintenance and
    improve code readability.
    

    View Slide

27. https://github.com/timble/openpolice-platform/blob/master/application/site/component/districts/view/relations/html.php
    

    View Slide

28. The Gitflow workflow defines a strict branching model
    designed around the project release.
    Use a branching model
    nvie.com/posts/a-successful-git-branching-model/
    

    View Slide

29. https://github.com/timble/openpolice-platform
    

    View Slide

30. https://www.vagrantup.com/ & https://www.docker.com/
    Have a virtual development
    environment
    Lower development environment setup time, increase
    development/production parity, and make the "works on my
    machine" excuse a relic of the past.
    

    View Slide

31. https://github.com/timble/openpolice-platform/blob/master/README.md
    

    View Slide

32. Examples
    https://flic.kr/p/bwHCXU
    

    View Slide

33. https://www.boston.gov
    

    View Slide

34. https://github.com/CityOfBoston/boston.gov
    

    View Slide

35. https://github.com/CityOfBoston/boston.gov/issues
    

    View Slide

36. https://analytics.usa.gov/
    

    View Slide

37. https://github.com/18F/analytics.usa.gov
    

    View Slide

38. https://www.govcms.gov.au
    

    View Slide

39. https://github.com/govCMS/govCMS
    

    View Slide

40. https://www.kanooh.be/nl/raamcontract/abonnementen-websites
    

    View Slide

41. https://tweakers.net/nieuws/85895/vlaamse-overheid-kiest-voor-drupal-as-a-service-aanbieder-kanooh.html
    Built with Drupal
    but source code is not open
    Funded by us, the taxpayer, for 9 million
    

    View Slide

42. We’re lagging behind
    https://flic.kr/p/o3ZQHn
    

    View Slide

43. http://www.feweb.be/sites/default/files/FEDERAALREGEERAKKOORD_09102014.PDF
    No mention of open source in the
    federal coalition agreement
    

    View Slide

44. 75 countries endorsed the Open Government Declaration since 2011. Belgium hasn’t.
    

    View Slide

45. https://governmenttechnology.blog.gov.uk/2016/12/14/our-commitment-to-better-open-source-practices/
    Others already have a commitment to
    make source code open by default.
    

    View Slide

46. View Slide

47. I have a “simple” dream ...
    

    View Slide

48. I dream of living in a truly open city
    where I can access, use, modify the
    code of my city’s website.
    You?
    

    View Slide

49. We build things for the web
    www.timble.net
    Thank you
    tom.janssens.me - @JanssensTom
    

    View Slide