You are browsing the archive for Roadmap.

Why you should take 10 minutes to look at the Open Data Roadmap this Open Data Day

- February 28, 2017 in community, IODC, Open Data Day, Roadmap

March 4th is Open Data Day! Open Data Day is an annual celebration of open data all over the world. For the seventh time in history, groups from around the world will create local events on the day where they will use open data in their communities.   For me, Open Data Day is a special day. This is not because I am busy organising it, but because I am always inspired by the different activities that we can all pull off as a community one weekend every year. Let’s be fair, while International Pancake day, which is celebrated today, is delicious, Open Data Day is important. It shows our strength as a community and brings new people to the discussions.

Open Data Day in Peru 2016

We all know, however, that open data is not only a one-day thing. It is a 365-day effort. Don’t get me wrong, even if you have done one event this year, and it is Open Data Day, you are fabulous! I do think, however, that this is a time to mention others in the community working all year round to try and make progress on different international topics. Whether that progress is being made through promoting the International Open Data Charter or working on standards for contracting or creating the world’s biggest open data portal for humanitarian crises. In the regional level, we see great examples of initiatives like AbreLatam/ConDatos or the African Open Data Conference.     Open Data Day, whether done locally or on a global-scale, is a good time to reflect on what happens in other places, or how you (yes, you!), can help and shape this open data ecosystem where we work. In my belief, if it’s open, everyone should have a right to express their opinions. Lucky for us, there is a tool that tries to look at the community’s burning topics and set the way forward. It is called the International Open Data Conference Roadmap, and it is waiting for you to interact with and shape further. Before you leave this post and read something else, I know what you might be thinking. It goes somewhere along the lines of “Mor, but who cares about my opinion when it comes to such high-level strategy?” Well, the whole community cares! I wrote this blog about the IODC just a year and a bit ago, and look, now I can actually help and shape this event. And who am I really? I am not a CEO of anything or a government official. I don’t think that only the noisy people (like me…) should be the individuals who are shaping the future. This is why your written opinion matters to us, the authors of the roadmap. Without it, this whole movement will stay in place, and without people understanding and working with the roadmap, we will not go anywhere.   I am aware that this post might come too late for some of you: your schedule for Open Data Day is full,  you need more time to get organised, etc. Got 30 minutes? Here is my suggested activity with the report and I would love to get comments on it on our forum! Got only 10 minutes? Pick a topic from the roadmap, the one that you feel most connected to, read about, a write a comment about it on our forum.

Activity suggestion: International Open Data Roadmap – what are we missing?

Time: 30 minutes Accessories: Laptops, post-its, pens, good mood.   Number of participants: 2-15 Activity: Step 1: Read the Roadmap main actions to the group :
Open Data principles– Broaden political commitment to open data principles Standards –  Identify and adopt user-centric open standards Capacity building – Build capacity to produce and effectively use open data Innovation – Strengthen networks to address common challenges Measurement – Make action on open data movement more evidence-based SDG– Use open data to support the sustainable development agenda   Step 2: Choose one action – If you have more than 4 people, divide the big groups into groups of up to 4 people.   Step 3: Read about the actions and what the mean in the report (pages 33-43). Discuss in the group about the meaning of the action. Do you understand it? If not what are you missing to understand it better? If yes, do you agree with it?   Step 4: On a post-it , write what do you think can help us to act and complete the actions or what are missing.   Step 5: Take a picture of your post it, upload it to the forum, with an explanation about it. You are also welcome to share it with on Twitter by using the hashtag: #IODCRoadmap.   I will run this session on the London Open Data Day Do-a-thon, if you are around, ping me at or my Twitter – @morchickit Have a great open data day event! Don’t forget to tweet about it #opendataday and send us your posts!

CKAN High-Level Roadmap Consultation – Autumn 2014

- October 1, 2014 in Association, Roadmap

We are working to create a Roadmap of key technical and community work for the next 6 months and we want to hear from as many as possible of you in the CKAN community to find out what you think is important. To aid this process we have created a long-list of Roadmap ideas in a Trello board which you can view, comment, vote on and add to – please take a look now and share your thoughts »

More Information

With the CKAN Association Steering Group and Technical Team in place, we can now think more about the CKAN “Roadmap”. The goal here is to agree a short-list of 4-6 high-level technical and community items that CKAN Association will focus on in the next 6-12m. The plan is as follows:
  • Build a “long-list” of potential roadmap item and review / prioritize with users and the community over the next few weeks
  • Create a final Roadmap selection (short-list) that will be the focus of our near-term work
Led by Ashley Casovan of the Steering Group, the Steering Group and the Technical Team have already prepped long-list of high-level roadmap items which can be found in trello here: Please jump in and vote and comment.


How does this relate to Github Ideas and Roadmap Tracker

The current ideas and roadmap tracker was used as input for this long-list. The purpose of the trello long-list was: To have a shorter high-level long-list that focused on key items (the issue tracker now has over 80 items of varying scope and detail) Provide a simple interface in which people (including non-developers) could vote and comment

How will the Roadmap be resourced

The aim of the Roadmap is to produce a list of things that the CKAN Association and general community can specifically focus and execute on. We aim to produce a list that is commensurate with current (and anticipated) resources available to the CKAN Association based on Member commitments.

Where can I find out more about CKAN Roadmaps

See the Roadmap page.

Improvements to the CKAN Roadmap Process

- March 13, 2014 in community, News, Roadmap

We have switched to a Github issue tracker for tracking and managing the ideas in the CKAN Roadmap (see also this pretty version). As detailed previously we have a public process for managing the roadmap for CKAN. This was being managed in Trello but is moving to a Github issue tracker. We have also updated the Roadmap page to give more information about the Roadmap and how it works:
The Roadmap provides stakeholders in CKAN, including users, developers and vendors, with the ability to shape and understand the future technical path for CKAN. Specifically, the Roadmap provides for:
  • Suggesting new ideas and features for CKAN
  • Prioritizing these into a schedule for future work especially on “core” CKAN
We emphasize that ideas don’t just have to be about improvements to the core CKAN software – for example, the idea of creating a new phone app client for CKAN would be perfect thing to submit. Lastly, we should emphasize that, of course, just because an item is in the ideas tracker does not mean it will get worked on. If you want a certain feature implemented then the best way to ensure that happens is to sponsor its development – get in touch for more information

Check out the Roadmap

New ideas and current roadmap itself are managed via an issue tracker on github. Idea issue tracker along with instructions on now to make new suggestions » Prettier column-based view of the ideas and roadmap »

Project CKAN

- October 18, 2013 in ckan, development, getting involved, membership, News, Roadmap

Over the last few years CKAN has seen impressive growth in technology, uptake, number of deployments and in the vendor and developer communities. It is now the basis of dozens of major sites around the world, including national data portals in the UK, US, Canada, Brazil, Australia, Germany, Austria and Norway. Once, almost all core CKAN development was done by the Open Knowledge Foundation; now, there are an increasing number of developers and providers, deploying, customising and working with CKAN. We believe that, as with many open-source projects when they achieve a certain size, the time has come to bring some more structure to the community of CKAN developers and users. By doing so we aim to provide a solid foundation for the future growth of the project, and to more explicitly empower its growing array of stakeholders. We are therefore proposing to create an independent, self-governed CKAN project at the Open Knowledge Foundation, separate from our own CKAN developments and offerings, to guide the future development and direction of the software. The main proposed actions are:
  • To establish a steering group and advisory board to oversee the project and represent the growing number of stakeholders.
  • To establish specific groups or teams to look after specific areas; in particular, a “technical group” to oversee technical development and a “content and outreach group” to oversee materials (including project website) and to drive community and user engagement.
  • To establish a membership model for stakeholders to support the long-term sustainability of the project.
The project will still have its formal institutional home at the Open Knowledge Foundation, and enjoy support and participation from our CKAN team. But it will be autonomous and will have its own independent governance, from a board drawn from major CKAN stakeholders. The Open Knowledge Foundation will continue to contribute at all levels, but this approach will allow others – from government users to suppliers of CKAN services – to have a formal role in the future development and direction of CKAN. Over the next couple of weeks we will be introducing a new structure for development (how to become a core contributor etc) and governance (steering committee and supporting as a member) and we would love to hear your ideas and feedback. Please either get in touch or place ideas in this open project ckan document and watch this space for more posts soon!

CKAN Roadmap goes public

- June 24, 2013 in ckan, contributing, News, Roadmap

Now that CKAN 2.0 is out, what should the next direction be for CKAN? New features, easier customisation, more data previews, UI tweaks… we’ve had plenty of ideas and suggestions, and we’d like you, the CKAN community, to help shape the direction and future of CKAN.

So, we’ve created a public CKAN Roadmap using Trello! CKAN is open source and there are lots of ways to get involved:

  • Prioritise features: see something you want? Vote it up (by clicking on the card and pressing the ‘vote’ button)!
  • Specify implementation: comment on a feature card with requirements, edge cases to consider or related work that exists.
  • Contribute code: Are you a coder working on something like one of these features? Let us know! Add a comment to the card, and e-mail the dev list.
  • Sponsor: See a feature listed you’d really like in CKAN, but don’t have the skills to implement yourself? You can sponsor the feature by paying for the developer time needed to create it. Just, write to info[at] or using our contact form.
  • Suggest: Is there some great feature that you can’t see on the roadmap? Add it to our github wiki page and kickstart a discussion on the discussion list.

Roadmap screenshot

About the roadmap

On the roadmap, you’ll find four columns of cards:

  • Ideas / requests: there are lots of ideas that have been put forward. Which of them would you find most valuable?
  • Backlog: These are things we plan to work on, but haven’t started yet.
  • In progress: Stuff our developers are working on at the moment.
  • Done: These are features that have recently been developed and will appear in a release of CKAN soon. Click on a card to see more details.

For actual bugs and issues, it is still best to report them on our github issue tracker. For general Q&A please use stackoverflow or drop a note to our open community dev list.