New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help to orient future development #100

Open
loleg opened this Issue Jul 6, 2017 · 3 comments

Comments

2 participants
@loleg
Copy link
Member

loleg commented Jul 6, 2017

Two years and 99 issues since this project started, I would like to get some feedback on how to orient, organize and optimise future development. Some background on the project status and mission is in ABOUT.md. Additional discussion is on a related forum thread. Or you can jump straight into the project board to help sort through top issues.


At time of writing there are 217 hackathon projects in the make.opendata.ch wiki, 90 projects published on hack.opendata.ch, 21 at now.makezurich.ch and dozens more on archived sites like IoT 2015 and 1001001. Many, many more are published by the open data community on other platforms (GitHub, OGD portals, university websites, etc.)

On their own, each of these is an interesting and inventive contribution to the community, the beginnings of a grassroots collaboration, a research direction, a startup... As a whole, the projects can be a rich source of information both on the history/evolution of the open data movement, as well as a references to the experience of participants with various data sources and platforms. Our old wiki platform has many downsides - first and foremost the difficulty to aggregate data about projects (status, team members, etc.) - which was one of the motivators for Dribdat, something that has been worked on with contributions and support from several core members the Opendata.ch community.

We have been discussing the idea of running more development sprints on Dribdat: updating it's backend, giving the frontend a refresh, further work on the chatbot interface and adding a better mobile frontend, moving it within the main infrastructure at Opendata.ch (it is currently hosted on the server of Datalets.ch), migrating data from past events on Make.Opendata.ch, integrating it with our community platforms (sites, blogs, forums, social media), and scaling it out to many more events and users using a SaaS model (click a button to start your own hackathon..)

Critically, this all should be done with a view to the wider usefulness of the tool, so it would be great to solicit feedback and collaboration from Open Knowledge and other closely aligned communities.

The sprint goal could sound something like this: develop our framework for bootstrapping and supporting projects from hackathon to startup, with a focus on community building, event support, use of data sources, and documenting progress, with plug-in support for on-prem and on-cloud collaboration. A longer term organisational goal could be: create the go-to platform for discovering, certifying and funding development of open data sources. As a stretch goal, we could: promote the cause of open development and open data, hackathons and civic activism, invite contribution and use by the international community.

The project has so far progressed mostly on contributions of free time, about 2 K CHF allocated towards short sprints out of the budget of events over the past two years. Even a small amount of motivation or support from the user community would help to motivate progress.

Here are some ways I can think of that people could contribute:

With moderate support, we could move to better infrastructure and support a self-service model, and carefully migrate project data to showcase a variety of community initiated open data projects. With good funding, all of the above plus integration with data portals and community tools could be imagined. With significant resources, and greater purpose, we could potentially rewrite the whole project using modern technologies like streaming data, reactive programming, blockchains, etc. But we need to start somewhere: spend at least a little time this summer dusting off the code base and closing some of the issues, and all kinds of contributions and support are welcome.

If you are interested in helping us to move forward with these plans, or think we should stop right here and do something more productive: please leave a note or just click the voting button as a sign of support. Thanks! -- @loleg

@loleg loleg added the help wanted label Jul 6, 2017

@loleg loleg changed the title Organise a development sprint Need help organising future development Jul 6, 2017

@loleg loleg changed the title Need help organising future development Get help organising future development Jul 6, 2017

@loleg loleg changed the title Get help organising future development Get help organizing future development Jul 6, 2017

@tamberg

This comment has been minimized.

Copy link

tamberg commented Jul 7, 2017

Thanks for the great work! Happy to recommend Dribdat anytime. How about focusing on sustaining the current feature set and ensuring that past results remain accessible (as you already do)? Maybe that sounds a bit unambitious but sometimes simple and reliable tools are quite useful, e.g. cURL.

@loleg

This comment has been minimized.

Copy link
Member

loleg commented Aug 7, 2017

Thank you @tamberg for that really excellent point. I would also quite like to go the way of Frictionless Data, focusing on collecting data and making tools around it. I'll take your suggestion as a vote in favor of focusing on the data model, aggregation and API, allowing for development of various apps / frontends in a later sprint.

@loleg loleg changed the title Get help organizing future development Help orient future development Aug 7, 2017

@loleg loleg changed the title Help orient future development Help to orient future development Aug 7, 2017

@loleg loleg removed this from Architecture in Dribdat 2.0 Aug 7, 2017

@loleg

This comment has been minimized.

Copy link
Member

loleg commented Aug 7, 2017

I've set up a project board where we can sort through the top improvement requests and bugs, as well as consider more fundamental concerns. It's not perfect but it's a start!

@loleg loleg added this to Data model in Dribdat 2.0 Dec 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment