This is the copy of the pad used to prepare the first karrot user call held on March 5 2018.
The original can be found here but will be automatically deleted after 30 days of inactivity.

Welcome dear users of Karrot!

Please answer the following questions, so that our call on Monday the 5th will go as smoothly as possible:


To answer, please copy&paste the paragraph containing the questions and fill in the answers directly underneath the respective question.
To give you an example, I answered them myself:


Please add your paragraph here!




Writeup of the main topics of the call on 2018-03-05

present:
teddy for östersund (just starting)
niki for maastricht (daily pickups, ~20 foodsavers, just introduced karrot)
fausto, chalo, xapeaz for quito (almost daily pickups, ~40 foodsavers, use karrot from the start)
nicco for gotenburg (daily pickups, ~60 foodsavers, use karrot since a year)
taras for stockholm (daily pickups, ~15 foodsavers, use olio)
tomasz for warsaw (almost daily pickups, ~40 foodsavers, want to use karrot)
isa for barcelona (just starting, encountered a lot of existing structures)
feature discussion:
notifications!!!
for what should be notified?
gotenburg: emergency pickups
quito: when a store is created, when someone cancels a pickup and needs someone else to do it
warsaw: when an empty pickup is approaching
maastricht: if a pickup is cancelled
how should be notified?
quito: emails are perfect for now
maastricht: push notifiations would be nice (yes there is an app! more info further down.)
gotenburg: sms would be great
when should be notified fpor empty pickups?
warsaw: pickups in the evening, notifications 24h before
who should be notified for empty pickups?
warsaw: people who subscribed to the store
quito: store subscriptions, yes!
hierarchies/permissions/admin roles
we are trying to go new ways in this regard and don't want to implement standard admin roles. we prefer progressive structures, which enable groups to act democratically and without the risk of an admin 'going mad' and all of a sudden acting against the interest of the group. that's why there's no admin roles yet. the password protection feature is only a temporary solution and we have many ideas for elaborate approval, voting and trust systems, which will also solve the problem which are normally solved by admin roles.
concrete ideas are:
- approval system for people who want to join a group
- voting system for the case of someone wanting to kick another member (my personal fave! ;))
- trust system to give out roles (which are socially viable but only badges in the software)
please refer to the linked issues on github for further reading:
- approval: https://github.com/yunity/karrot-frontend/issues/894
- voting: https://github.com/yunity/karrot-frontend/issues/853
- trust: https://github.com/yunity/karrot-frontend/issues/878
communication
we want to add walls to stores and pickups
there are also ideas to add threads to messages, which would already serve as a minimal version of a forum (https://github.com/yunity/karrot-frontend/issues/846)
1-on-1 conversations are also already worked on (https://github.com/yunity/karrot-frontend/issues/832)
mobile app
there is an app, but it's not in the play store because:
- it doesn't auto-update
- it's bleeding edge development
but is has push notifications for wall messages! ;)
if someone of you wants to test it I can send the apk file to you directly - but don't expect it to be perfectly usable, please!
networking talks:
after half an hour of technical problems the atmosphere was nice and collaborative!
it was definitely helpful talking to each other!
I really want to do this more often - also using a different service, I really don't mind.
you can set dates for calls as well, it doesn't have to depend on me! ;)
and I want to get your opinion on features more regularly, so I will probably ask more often in the future.