New Open Knowledge Network chapter in Nepal

Oscar Montiel - June 26, 2017 in community, OK Nepal

We are happy to announce that this month a new Chapter at the Open Knowledge Network is being launched officially: welcome Open Knowledge Nepal in this new stage! Since February 2013, Open Knowledge Nepal has been involved in research, advocacy, training, organizing meetups and hackathons, and developing tools related to Open Data, Open Government Data, Open Source, Open Education, Open Access, Open Development, Open Research and others. The organization also helps and supports Open Data entrepreneurs and startups to solve different kinds of data related problems they are facing through counseling, training and by developing tools for them. Nikesh Balami, CEO of Open Knowledge Nepal tells us: from random groups of people to build a core team of diverse backgrounds, starting from messy thoughts to realistic plans and long-term goals, we have become more organized and robust. [We] Identified ourselves as a positive influence towards the community and nation. After being incorporated as a Chapter, we now can reach out extensively among interested groups and also expect to create impact in a most structured way in national and international level. Our main goal is to establish ourselves as a well-known open data organization/network in Nepal. Pavel Richter, CEO of Open Knowledge International, underscored the importance of chapters: “Most of the work to improve people’s lives is and has to happen in local communities and on a national level. It is therefore hugely important to build a lasting structure for this work, and I am particularly happy to welcome Nepal as a Chapter of the growing Open Knowledge Family.” Chapters are the Open Knowledge Network’s most developed form, they have legal independence from the organization and are affiliated by a Memorandum of Understanding. For a full list of our current chapters, see here and to learn more about their structure visit the network guidelines. The Open Knowledge global network now includes groups in over 40 countries. Twelve of these groups have now affiliated as chapters. This network of dedicated civic activists, openness specialists, and data diggers are at the heart of the Open Knowledge International mission, and at the forefront of the movement for Open. Check out the work OK Nepal does at

Σειρά Επιπτώσεων: Βελτιώνοντας την Ικανότητα Συλλογής Δεδομένων σε Μη Τεχνικούς Οργανισμούς

Χριστίνα Καρυπίδου - June 26, 2017 in Featured, Featured @en, News, ανοικτά δεδομένα, κοινωνία πολιτών, Νέα

από τον  David Selassie Opoku Το Open Knowledge International είναι μέλος του Open Data for Development (OD4D), ενός παγκόσμιου δικτύου ηγετών στην κοινότητα ανοικτών δεδομένων, που συνεργάζονται για την ανάπτυξη λύσεων ανοικτών δεδομένων σε όλο τον κόσμο. Σε αυτό το blog, ο David Opoku του Open Knowledge International μιλά για το πώς το OD4D πρόγραμμα […]

Ποια δεδομένα χρειαζόμαστε; Η ιστορία της υποτροφίας του Cadasta GODI

Χριστίνα Καρυπίδου - June 26, 2017 in Featured, Featured @en, godi, News, ανοικτά δεδομένα, Νέα

Από τη Mor Rubinstein Αυτό το blogpost γράφτηκε από τις Lindsay Ferris και Mor Rubinstein Υπάρχουν πολλά δεδομένα εκεί έξω, αλλά ποιοι χρήστες δεδομένων χρειάζονται για να λύσουν τα προβλήματά τους; Πώς μπορούμε εμείς, ως εξωτερικό σώμα, να γνωρίζουμε ποια δεδομένα είναι ζωτικής σημασίας, ώστε να τα μετρήσουμε; Επιπλέον, τι πρέπει να κάνετε όταν δημοσιεύονται […]

Αξιολόγηση των ανοιχτών δεδομένων που παρέχονται από κυβερνήσεις για το 2017

Spyridoula Markou - June 25, 2017 in Featured, Featured @en, News, Uncategorized @en, Νέα

Δημοσιεύθηκε από το OK International η πρώτη έκθεση για την κατάσταση στα ανοικτά δεδομένα δημοσίων φορέων για το 2017. Η έκθεση συντάχθηκε από τους Danny Lämmerhirt, Mor Rubinstein και Oscar Montiel και στηρίχθηκε στα αποτελέσματα του Open Data Index (GODI) 2016/17. Στην έκθεση συμπυκνώνονται τα προβλήματα των ανοικτών δεδομένων που παρέχονται από τις κυβερνήσεις και […]

Hackathon al Gran Sasso Science Institute! Iscrivetevi, avete tempo fino al 1 Luglio!

Francesca De Chiara - June 23, 2017 in civic tech, Events, Open Data

In occasione del Festival della Partecipazione, il Gran Sasso Science Institute (GSSI) organizza il 7 e 8 luglio prossimi a L’Aquila un Hackathon per sviluppare progetti di prodotti, di servizi o rappresentazioni visuali utili, sostenibili e replicabili, in grado di generare un impatto significativo nei modi di pensare, vivere e condividere la ricostruzione e le future […]

Hemos decidido disolver la asociación

maestro - June 22, 2017 in asamblea

En asamblea general extraordinaria celebrada el Jueves 22 de Junio de 2017 los socios presentes por unanimidad han decidido la disolución de la asociación. Queda una comisión liquidadora formada por Adolfo Antón, Alberto Abella, Diego Álvarez e Ignasi Alcaide para la liquidación de la misma. Agradeciendo a todos los socios la cooperación que se ha realizado durante estos años, y esperando que el conocimiento abierto siga adelante nos despedimos.

OKI Agile: Scrum and sprints in open data

Mor Rubinstein - June 22, 2017 in agile, Our Work, scrum

This is the third in a series of blogs on how we are using the Agile methodology at Open Knowledge International. Originating from software development, the Agile manifesto describes a set of principles that prioritise agility in work processes: for example through continuous development, self-organised teams with frequent interactions and quick responses to change ( In this blogging series we go into the different ways Agile can be used to work better in teams and to create more efficiency in how to deliver projects. The first posts dealt with user stories and methodologies: this time we go into using scrum and sprints to manage delivery of projects. Throughout my time as a project manager of open data projects in The Public Knowledge Workshop in Israel and in Open Knowledge International, I have used various tools and methods to manage delivery of software and content development. I have used Trello, Asana and even a Google spreadsheet, but at the end of the day I am always going back to Github to run all of the project tasks, assisted by Waffle. Many people that I spoke to are afraid of using GitHub for project management. To be fair, I am still afraid of Git, but GitHub is a different concept: It is not a code language, it is a repo site, and it has got really good functions and a very friendly user interface to use for it. So do not fear the Octocat!

Why Github?

  • As an open source community facing products, our code is always managed on Github. Adding another platform to deal with non-code tasks just adding more complications and syncing.
  • It is open to the community to contribute and see the progress and does not need permissions management (like Trello).
  • Unlike what people think – it is really easy to learn how to use Github web version, and it’s labels and milestones feature are helpful for delivery.

Why Waffle?

  • It syncs with Github and allows to show the tasks as Kanban.  
  • It allows to write estimates that hours of work for each task.
So far, working on Github for the project showed the following:
  1. Better cooperation between different streams of work
    Having one platform helps the team to understand what each function in the project is doing.  I believe that the coder should understand the content strategy and the community lead should understand the technical constraints while working on a project  It gives back better feedback and ideas for improving the product.
  2. Better documentation
    Having all in one place allows to create better documentation for the future.

So what did we do for GODI (the Global Open Data index) 2016?

  • Firstly, I have gathered all the tasks from the Trello and moved it to the Github.
  • I created tags that allow to differentiate between different types of tasks – content, design, code and community.
  • I added milestones and sorted out all tasks to fit their respective milestones of the project. I also created a “backlog” for all tasks that are not prioritise for the project but need to be done one day in the future. Each milestone got a deadline that responds to the project general deadlines.
  • I made sure that all the team members are part of the repository.
  • I organised Waffle to create columns – we use the default Waffle ones: Backlog, Ready, In Progress and Done.
Using one system and changing the work culture means that I needed to be strict on how the team communicates. It is sometimes unpleasant and needed me to be the “bad cop” but it is a crucial part of the process of enforcing a new way of working.  It means repetitive reminders to document issues on the issue tracker, ignoring issues that are not on GitHub and commenting on the Github when issues are not well documented. Now, after all is in one system, we can move to the daily management of tasks.


  • Before the sprint call
    • Make sure all issues are clear –  Before each sprint, the scrum master (in this case, also the project manager), make sure that all issues are clear and not vague. The SM will also add tasks that they think are needed to this sprint.
    • Organise issues – In this stage, prior to the sprint call, use the Waffle to move tasks to represent where you as a project manager think they are currently.
  • During the sprint call:
    • Explain to the team the main details about the sprint:  
      • Length of the milestone or how many weeks this milestone will take
      • Length of the sprint
      • Team members – who are they? Are they working part time or not?
      • Objectives for the sprint these derive from the milestone
      • Potential risks and mitigation
      • Go through the issues: yes, you did it before, but going through the issues with the team helps you as PM or SM to understand where the team is, what blocks them and creates a true representation of the tasks for the delivery team.
      • Give time estimates Waffle allows to give rough time estimates between 1-100 hours. Use it to forecast work for the project.
      • Create new tasksspeaking together gets the creative juices going. This will lead to creation of new issues. This is a good thing. Make sure they are labeled correctly.
      • Make sure that everyone understand their tasks: In the last 10 minutes of the sprint, repeat the division of work and who is doing what.
    • After the sprint call and during the sprint:
      • Make sure to have regular stand ups I have 30 minute stand ups, to allow the team to have more time to share issues. However, make sure not to have more than 30 minutes. If an issue demands more time to discuss, this means it needs its own dedicated call to untangle it, so set a call with the relevant team members for that issue.
      • Create issues as they arise – Don’t wait for the stand up or sprint kick-off call to create issues. Encourage the team and the community to create issues as well.
      • Always have a look at the issue trackerMaking sure all issues are there is a key action in agile work. I start everyday with checking the issues to make sure that I don’t miss critical work.
      • Hyper communicate – Since we are a remote team, it is best to repeat a message than not say it at all. I use Slack to make sure that the team knows that a new issue arise or if there is an outside blocker. I will repeat it on the team stand ups to make sure all team members are up-to-date.

    New open energy data portal set to spark innovation in energy efficiency solutions

    Open Knowledge International - June 22, 2017 in ckan, Viderum

    Viderum spun off as a company from Open Knowledge International in 2016 with the aim to provide services and products to further expand the reach of open data around the world. Last week they made a great step in this direction by powering the launch of the Energy Data Service portal, which will make Denmark’s energy data available to everyone. This press release has been reposted from Viderum‘s website at

    Image credit: Jürgen Sandesneben, Flickr CC BY

    A revolutionary new online portal, which gives open access to Denmark’s energy data, is set to spark innovation in smart, data-led solutions for energy efficiency. The Energy Data Service, launched on 17 June 2017 by the CEO of Denmark’s state-owned gas and electricity provider Energinet, and the Minister for Energy, Utilities and Climate, will share near real-time aggregated energy consumption data for all Danish municipalities, as well data on CO2emissions, energy production and the electricity market. Developers, entrepreneurs and companies will be able to access and use the data to create apps and other smart data services that empower consumers to use energy more efficiently and flexibly, saving them money and cutting their carbon footprint. Viderum is the technology partner behind the Energy Data Service. It developed the portal using CKAN, the leading data management platform for open data, originally developed by non-profit organisation Open Knowledge International. Sebastian Moleski, CEO of Viderum said: “Viderum is excited to be working with Energinet at the forefront of the open data revolution to make Denmark’s energy data available to everyone via the Energy Data Service portal. The portal makes a huge amount of complex data easily accessible, and we look forward to developing its capabilities further in the future, eventually providing real-time energy and CO2 emissions data.” Energinet hopes that the Energy Data Service will be a catalyst for the digitalisation of the energy sector and for green innovation and economic growth, both in Denmark and beyond. “As we transition to a low carbon future, we need to empower consumers to be smarter with how they use energy. The Energy Data Service will enable the development of innovative data based solutions to make this possible. For example, an electric car that knows when there is spare capacity on the electricity grid, making it a good time to charge itself.Or an app that helps local authorities understand energy consumption patterns in social housing, so they can make improvements that will save money and cut carbon”, said Peder Ø. Andreasen, CEO of Energinet. The current version of the Energy Data Service includes the following features:
    • API (Application Programme Interface) access to all raw data, which makes it easy to use in data applications and services
    • Downloadable data sets in regular formats (CSV and Excel)
    • Helpful user guides
    • Contextual information and descriptions of data sets
    • Online discussion forum for questions and knowledge sharing

    Ha Bun Shu: a Japanese Book of Wave and Ripple Designs (1919)

    Adam Green - June 22, 2017 in design, japan, japanese, ocean, ripples, sea, water, waves

    Wonderful selection of wave and ripple designs produced by the Japanese artist Mori Yuzan, which would have found their way onto swords and associated paraphernalia, as well as lacquerware, Netsuke, religious objects, and a host of other items.

    Digitale Agenda Stellungnahme & Fachgespräch: Moderner Staat – Chancen durch Digitalisierung

    walter palmetshofer - June 22, 2017 in Uncategorized

    Der Ausschuss für Digitale Agenda des Bundestags befasste sich letzte Woche, am 21.06.2017, in einem öffentlichen Fachgespräch mit dem Thema „Moderner Staat - Chancen durch Digitalisierung“ und wir waren auch dabei. Die völlständige Stellungsnahme ist hier. Die tl;dr-Zusammenfassung der Stellungsnahme: „Es geht um eine politische Frage, nicht um eine technische“, argumentierte Walter Palmetshofer von der Open Knowledge Foundation Deutschland e.V.. Der moderne Staat funktioniere als digitale Plattform und zeichne sich durch Transparenz, Anwenderfreundlichkeit sowie Datenschutz aus. Um öffentliche Daten nutzen zu können und eine offene Verwaltungskultur zu etablieren, solle der Gesetzgeber ein einheitliches Transparenzgesetz schaffen, forderte er. „Und wer „Moderner Staat – Chancen durch die Digitalisierung“ sagt, der muss auch offene Standards, offene Software, Interoperabilität, Netzneutralität und Infrastruktur - Breitbandausbau - sagen. Ohne diese Aspekte ist ein moderner Staat eben nicht möglich. Dies gilt auch aus Standortperspektive und industriepolitscher Unabhängigkeit von großen IT-Firmen (FAMGA, …). Weiters gilt es die Angst vor der Digitaliserung zu nehmen bzw. permament Stellung bei “Digitalisierungsbremsen” wie u.a. das NetzDG, Leistungsschutzrecht, Störerhaftung, … zu beziehen.“ Vielen, vielen Dank für den großartigen Input der Community für unsere Stellungnahme. (Vorallem TB, BK, GP, PP, JH, RB, AS & TT aus dem verwaltungsnahen Umfeld.) Aufzeichnung des Fachgesprächs und einige spannende Punkte:
    • 1:01:00 Government as Plattform vs. Goverment as a Service - Mergel
    • 1:09:30 Wieso E-Gov in Österreich eher umgesetzt wurde (Sitzung von 2003) - Ludewig
    • 1:11:00 Jarzombek zitierte Thorsten Dirks, CEO Bitkom: „Wenn sie einen Scheißprozess digitalisieren, dann haben sie einen scheiß digitalen Prozess,“ und nochmals den Koalitionsvertrag von NRW „Wir starten mit einem „Blockchain“-Pilotprojekt in der Verwaltung. Damit entwickeln wir die Sicherheit kritischer und sensibler IT-Prozesse weiter.“ Anmerkung: Kann man gerne die Blockchain drüberwerfen, wird aber das ursprüngliche Problem nicht lösen.
    • 1:13:39 „Juristisches Denken“ in der Verwaltung und die damit einhergehenden Parameter. Gut analyisiert und sorgte auch für Schmunzeln.
    Liste der weiteren Sachverständigen und die Stellungsnahmen:
    • Prof. Dr. Ines Mergel, Universität Konstanz, Fachbereich Politik- und Verwaltungswissenschaften
    • Dr. Johannes Ludewig, Vorsitzender des Nationalen Normenkontrollrates
    • Prof. Dr. Mario Martini, Leiter des Programmbereichs „Transformation des Staates in Zeiten der Digitalisierung“ am Deutschen Forschungsinstitut für öffentliche Verwaltung und Lehrstuhlinhaber für Verwaltungswissenschaft, Staatsrecht, Verwaltungsrecht und Europarecht an der Universität für Verwaltungswissenschaften Speyer
    • Matthias Kammer, Direktor des Deutschen Instituts für Vertrauen und Sicherheit im Internet