Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
100 lines (77 sloc) 8.29 KB

Karrot Roadmap

General Direction

First of all, we want to support the existing users on, which are mostly foodsaving groups. For this, we want to improve governance and statistics.

To use Karrot for other purposes than saving food, we want to consolidate a user base that is part of two or more groups. Development should focus on a useful platform for them to coordinate with their groups/teams and to create synergies of cooperation between groups and people in those groups. An example of that, which is already happening in Gothenburg, is the foodsaving group (Solikyl) and the Bike Kitchen group. There is potential for much more in this city, which could prototype this kind of use case.

To make Karrot useful to a wider public, we want to add sharing features and allow users to communicate directly with established groups, which would become hubs for saving and sharing. The possibility to create new groups for sharing stuff or coordinating activities would also be a much more straightforward feature.

Karrot is a free and open-source software and its vision should inspire more people to contribute and co-create it. Therefore we need to work also on the following:

  • On governance and organisation: finish writing the constitution and defining what kind of association should be created. This would give clear guidelines for the role of contributors and ensures a more transparent and democratic development process.
  • Discuss and define the need and role of funding. Apply for grants when time is right and there is an opportunity.
  • Start doing some PR and recruiting: by improving the website with a clearer description of what Karrot does and its vision, reach out in our networks to show it off and recruit new contributors.

Current Development (higher priority)

We are working on this either right now or pretty soon in the future. Should be implemented in the next few months.

View issues

Ready for development (lower priority)

Issue is understood well enough for development to start, but not currently assigned to a developer.

View issues

Current discussion (higher priority)

We want to work on this in mid-term future. We need to think about it more before we can implement it, so active discussion is highly welcome. Feel free to join in!

View issues

Discussion (lower priority)

Quite a bit in the future (~1 year), haven't been discussed very much. If one of those is more important to you than those in "Current discussion", please contact us!

View issues

You can’t perform that action at this time.