Weekly call about Karrot development 2025

Date: 2025-11-04 on Karrot
Facilitator: we the people
Minutes:
Participants: Bruno, Nathalie

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: latest 11:00 CET
    • information? any (non-karrot) announcements? unavailabilities?
      • Nathalie in holiday mode next week (at least two Tuesday)
      • Bruno not doing co-working next week
    • next meetings:
      • co-working:
        • Wednesday: Nathalie, Bruno
        • Thursday: no
      • strategy session (Friday): yes
      • weekly: Bruno
    • pick facilitator for next weekly meeting: waiting for other people

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

4. Discussion points

  • updates
    • none
  • release
    • banner text, test on dev (Bruno has action item)
    • 2 or 1 banner texts?
      • pre- release
      • at the time
    • check with Nick about pre-release banner
    • use text from karrot group for a forum post! and link this post in banner
    • Nathalie could do more testing in co-working tomorrow (if she joins)
    • feedback issue? high demand bug fix
      • if not now def next
      • but maybe now
 :pray:
  • workshop Göteborg
    • Bruno has an idea! :bulb:
        1. karrot focused work, get together for the team, onboard new contributors like Wilhelm and others
        1. foodsharing Sweden project side; Nathalie & Butze lots of experience with foodsharing, foodsharing focused workshop, maybe started outreach already and there is interest from other cities in the region
      • Bruno can organise places to stay
      • connections hard to establish online, get more Swedish people on board!
      • Bruno & Butze talked about March, spring-time
      • finance with project money as part of the development money (~7000€)
    • reactions
      • checking the Bristol days pad (2300 EUR inc. Airbnb)
      • 2k-3k sounds feasible
      • thinking about how much for travel expenses and how much for development
      • more interested in number 1 (Karrot)
      • can imagine being a guest for a workshop on number 2
        • don’t know much about food safety. is it a big topic there? B: not really
      • Butze seems really interested, better candidate to lead this, maybe he could even bring Anton?
      • it would feel odd if introduced as a person from FS Germany
      • invite someone from Foodsharing is an idea
      • think we should start planning this now
      • the sooner we get to it the more likely
      • how long could it be? a week?
      • Bruno: could be as long as you wish! maybe span over 2 weekends, flexible from my side. have one whole weekend in this time frame
      • March/ April seem good
      • people are happy when spring starts, there is also a forest close by
      • Bruno to start with outreach campaign already
      • ‘How to organise your group’ workshop
      • could even do sociocracy input
      • get even more funding!
  • funding: https://www.thecatalyst.org.uk/current-projects/kindling/
    • Deadline to apply: Noon, 21 November 2025
    • continue conversation in thread
    • could do collaborative writing to apply, but seems very easy
    • needs at least one person committing to go in person
    • We won’t fund:
      • Activity that takes place outside the UK
      • Projects unrelated to tech justice
      • Large capital purchases (e.g. buying equipment)
      • Work that is already fully funded elsewhere. This does not include additions to previously funded activities.
    • funding for karrot? a bit more of a sub-project (one specific feature/ aspect)
    • could send them a question explaining karrot’s situation

Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] VIII
  • continue on finance app [Jay] VII
  • try a visualisation of our strategy on excalidraw [Nick] IV
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] III
  • contact VolontĂ€rbyrĂ„ [Bruno] II
  • write banner texts @Bruno
  • check eligibility for NLNet @Vasilis Vasilakis (Ntouros) II
  • check with Nick and open signal group for server discussion with Timber and Tilmann @Nathalie
  • point Daniel to the feedback discussion in karrot group @Nathalie
  • check with Nick around kindling funding @Bruno

Date: 2025-11-11 on Karrot
Facilitator: Vas
Minutes: Vas, Bruno
Participants: Vas, Bruno

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11 CET
    • information? any (non-karrot) announcements? unavailabilities?
      • Vas is back on the 24rd of Nov.
    • next meetings:
      • co-working:
        • Wednesday: -
        • Thursday: -
      • weekly: Bruno maybe
    • pick facilitator for next weekly meeting: Bruno (provisional)

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • write to bartosz about csv report [nick] VIII
  • continue on finance app [Jay] VII
  • try a visualisation of our strategy on excalidraw [Nick] IV
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] III
  • contact VolontĂ€rbyrĂ„ [Bruno] II
  • write banner texts @Bruno
  • check eligibility for NLNet @Vasilis Vasilakis (Ntouros) II
  • check with Nick and open signal group for server discussion with Timber and Tilmann @Nathalie
  • point Daniel to the feedback discussion in karrot group @Nathalie
    • done? Daniel found it!
  • check with Nick around kindling funding @Bruno

4. Discussion points

  • updates
    • prepared for release for all new features
    • banner is written, on dev
    • pop up icons explaining new features on dev
    • beta-testing done
    • meeting, everyone had an issue unf
    • we should replan the strategy call
  • NLnet upcoming funding call - https://nlnet.nl/commonsfund/
    • deadline of December 1st 2025 12:00 CET

    • looking to the previous calls, part of different calls

    • latest was NGI0Entrust, data sovereignty

    • having the same feeling as the previous time that we r not that technical for this

    • brainstorm some ideas

    • 24 - 27 could be some days to put things down if we decide to proceed

    • community management for commons in the physical world

      brainstorming on web4: bridge the physical with the digital

    • manage shared resources

Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] IV
  • continue on finance app [Jay] VIII
  • try a visualisation of our strategy on excalidraw [Nick] V
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] IV
  • contact VolontĂ€rbyrĂ„ [Bruno] III
  • check eligibility for NLNet @Vasilis Vasilakis (Ntouros) III
  • check with Nick and open signal group for server discussion with Timber and Tilmann @Nathalie
  • check with Nick around kindling funding @Bruno
  • Book the strategy call on the normal call the 25th @Vasilis Vasilakis (Ntouros)

Date: 2025-11-25 on Karrot
Facilitator: Vasilitator
Minutes: all
Participants: Bruno, Nathalie, Nick, Vas

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 1h, nick until 10:30 CET until 11 CET
    • information? any (non-karrot) announcements? unavailabilities?
      • vas away from 22nd december, then to oxford real farming conference
    • next meetings:
      • co-working:
        • Wednesday: Nathalie, Bruno
        • Thursday: Nathalie
      • weekly:
    • pick facilitator for next weekly meeting: Bruno

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • write to bartosz about csv report [nick] IV
  • continue on finance app [Jay] VIII
  • try a visualisation of our strategy on excalidraw [Nick] V
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] IV
  • contact VolontĂ€rbyrĂ„ [Bruno] III
  • check eligibility for NLNet @Vasilis Vasilakis (Ntouros) III
    • done
  • check with Nick and open signal group for server discussion with Timber and Tilmann @Nathalie
    • there is a group now about server things
  • check with Nick around kindling funding @Bruno
    • deadline passed
  • Book the strategy call on the normal call the 25th @Vasilis Vasilakis (Ntouros)
    • done

4. Discussion points

  • updates
    • paper rejected once again (Vasilis) :frowning: :frowning:
    • bath community :seedling:
    • tech collective in Sweden/ Gothenburg, could host karrot @Bruno
  • nlnet/ strategy
    • deadline 1st of Dec
      • Nathalie:
        • excited to use excalidraw, summary of topics
          • use our strategy notes to draw out some software ideas for NLnet
          • do have time to come up with a collection of ideas
        • How much text it needs??? Bit less motivated to write these things
      • Vas:
        • would be great if we make it! but quite tight deadline, would feel a bit sad if we didn’t try

        • tomorrow traveling, maybe can join co-working
? need to check

        • was involved in the two previous proposals
        • text should be quite to the point, title and small paragraph
        • 1st is next monday, at noon CET
      • Bruno:
        • positive, we should try
        • not aim for a lot of features
        • strategy work that we didnt finish
        • make strategy before the application ? not possible as of now
        • but we can think in parallel
      • Nick:
        • I feel that its worth having a go
        • very clear, clearly understood things already, avoid vague,
        • making a smaller application
        • less items/money
        • Monday 12 is the deadline, sunday is busy
        • further enabling self-hosting might be quite appealing
        • very much in line with our visions as well
    • Suggestion: Attempt to converge some ideas for NLNet
      • thread list of ideas, engage there
        • the more recent one
      • suite of public pages on self-hosted instance
      • public sign up for activities
.
      • organising pads in “docs”
      • progressive UI
        • introducing wide level of complexity to the user
        • requires design process
      • Karrot for small groups?
      • support organizing common resources
        • requires design process
        • could be related to IoT, connecting a physical object to Karrot
      • different activities/ event types
      • become more general purpose (not ready for other communities)
        • pair up with a community, e.g. Makerspace
    • another round
      • a couple of more defined ideas and one that requires design process
      • is a design-only task acceptable by Nlnet?
        • we can always submit and adjust after their feedback
      • progressive UI seems interesting
    • public sign-up
    • public pages
    • design process: progressive interface (with implementation?)
    • improve broader use of activities (beyond pick-ups): make it more concrete

Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] V
  • continue on finance app [Jay] IX
  • try a visualisation of our strategy on excalidraw [Nick] VI
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] V
  • contact VolontĂ€rbyrĂ„ [Bruno] IV
  • continue nlnet proposal [all]

Date: 2025-12-02 on Karrot
Facilitator: Bruno
Minutes:
Participants: Nathalie, Bruno, Nick, Jay

1. Opening

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • write to bartosz about csv report [nick] V
  • continue on finance app [Jay] IX
    • why is this coworking subject on the weekly meeting every week? can it be removed?
      • take it off :slight_smile:
  • try a visualisation of our strategy on excalidraw [Nick] VI
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] V
  • contact VolontĂ€rbyrĂ„ [Bruno] IV
  • continue nlnet proposal [all]
    • :partying_face: :partying_face: :partying_face:

4. Discussion points

  • updates
    • nlnet application
      • submitted on Monday in time!
      • see pad for details https://karrot.world/#/group/191/pads/nlnet
        • public pages for self-hosting instances
        • public sign-up for activities
        • interface and navigation improvements
      • added up to 20 000 EUR
    • feedback issue + ci issue
      • keeps loading feedback, reported by many people
      • fixed it! 3 fixes actually
        • sent to place after giving feedback, scrolls to your feedback just given
        • select field is empty —> that can’t happen any longer
        • deletes notification that becomes irrelevant (after giving feedback)
      • videos were helpful (in karrot group)
      • working with codeberg to fix ci issue too
    • yuca signal group
      • discussion about yuca server
      • access to the server/ how do we manage the server, not solely for karrot
      • there is a group now! Tilmann, timber, Nathalie and Nick
      • no active plan (yet)
  • release the beast! :lion:
    • push the button
    • ready for some time
    • one of the bigger ones, bunch of new features (roles, sanctions)
    • might introduce bugs
    • let’s do it!
    • merge in new translations too
    • comments
      • everything set and done, right?
        • info buttons
        • tutorials are up
        • activate banner (draft on dev already)
      • when?!
        • try this week
      • feature flag?
        • no! you’ll have to have them
        • not maintaining two pathways e.g. for sanctions
        • roles can at least surface existing karrot ones if not used for custom ones
      • would it be interesting to do it together?
        • resealing can be done any time
        • deployment better be done on special time (late)
        • keep it as an idea for the future
  • solikyl situation
    • nick’s message to karrot team explaining the situation: https://community.karrot.world/t/situation-in-solikyl-goteborg/2474
    • nick’s message to the person: https://community.karrot.world/t/account-restriction/2473
    • formal request: https://community.karrot.world/t/request-to-exclude-group-member/2475
    • don’t use the membership review feature, partly from when it used to notify the whole group each time
    • people spread out around the town, don’t always want to take positions about issues coming up
    • many people don’t really understand the voting membership review feature
    • plan to write to karrot team in advance got a bit rushed, and they heard before, and it got chaotic
    • round:
      • nathalie:
        • Q: do you think the sanctions feature could have helped?
        • process seems well documented and fine
        • not so interested in all the details of exactly what happened within the group
        • reflected on our agreement, have all the pieces in place
        • need to follow up with the person
        • excluding from the group yes, but the what about from the whole instance? is that a question, would think “probably not” (exclude them from the whole instance)
        • would we act the same way for any karrot group? responsiveness, etc
 probably not?
      • jay:
        • so many questions and so many things to say! have been thinking about it a lot
        • had a gut feeling, don’t like it when we override some rules, put in place some rules, then block them kick them out, censor their messages
        • seems a lot of effort to make things fair, then override it, means structure is probably not good enough and need to adapt it
        • thinking of cases where it could be abused, e.g. where somehow has some power in an organisation and asks karrot to kick them out
        • surprised about decision to censor message, there was a previous case of somebody writing a lot of incoherent aggressive messages, but in this case message was just pointing out faults of the organisation
        • maybe could have been handled using accountability features within karrot (e.g. showing dates, etc.)
        • censoring a message gives a sense of something to hide, what if something is going on, do they have another way of reporting it
      • butze:
        • don’t want to add much
        • excluding people from a group is harshest thing I know about from community
        • every case is crazy, experienced it a couple of times, and currently going through it in siegen, it causes ending of initiatives
        • have been a big hippy before saying noone gets excluded, but really changed my mind
      • nick:
        • https://community.karrot.world/t/situation-in-foodsharing-warsaw/1782
        • temporary restriction is not part of our agreement, would be in favour of updating it
        • a lot of harm can be done in a short time, processes can often take weeks
        • have it done before made a a precedent
        • can put everything (account, message) back, if we decide on it here
        • less interested in the details of the group, don’t have the connection to make sense of it, feels inappropriate
        • improving our database agreement
        • don’t want to receive personal messages or be in that position to act
        • karrot team signal chat for emergencies?
        • see feedback log on forum: external authorities, reflect them on karrot group
      • Bruno:
        • would like to say ‘yes’ that sanctions would have helped
 but a bit hesitant. Situation developed over years, complex. In this case rather ‘no’
        • tricky position to be in, board of a group and part of karrot team
        • don’t think we’ve overridden any processes
        • sense of trust is also part of our agreement, want to lift this up
        • trying to not talk about details, keeping a healthy distance for karrot team
        • team decision is still necessary
      • Proposal
        • rework our agreement
          • to include temporary restrictions pending further decision
          • to consider communication ways
          • to improve accountability by having an internal write-up of what happened
        • this.situation
          • uphold request to restrict member from the groups
          • remove temporary restriction from karrot.world
      • consent? yes!
  • strategy session next week?
    • Bruno, and Nathalie can be there, maybe Butze? vas we don’t know yet. Jay too
    • follow up in activity chat?
    • if not next week probably next year
  • christmas bonus feature?
    • https://karrot.world/#/group/191/pads/christmas-bonus
    • video call and pads in the past
    • criteria: genuinely useful, well contained (no big design process),
    • invitation to join, playful and fun, do designs etc
    • other ideas for some other fun gadgets
      • meditation timer?
      • other things for video calls, hand up thing (with numbers!)
      • don’t want to lose karrot personality from carrots and hearts emojis in calls!

Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] VI
  • try a visualisation of our strategy on excalidraw [Nick] VII
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] VI
  • contact VolontĂ€rbyrĂ„ [Bruno] V

Date: 2025-12-09 on Karrot
Facilitator: all
Minutes: all
Participants: Bruno, Nathalie

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11 CET
    • information? any (non-karrot) announcements? unavailabilities?
      • Nathalie & John chatting about advent of code
    • next meetings:
    • pick facilitator for next weekly meeting: open

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • write to bartosz about csv report [nick] VI
  • try a visualisation of our strategy on excalidraw [Nick] VII
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] VI
  • contact VolontĂ€rbyrĂ„ [Bruno] V

4. Discussion points

  • updates
  • next strategy session
    • next week? Vas might be working?
    • tomorrow? too short-term?
    • what do we want to do
      • focus on actionable items
      • create roadmap or summary
      • guiding document/ text
      • matrix Nathalie worked on and Bruno’s summary draft
      • 2 levels: broader summary/ vision text and actionable items
      • how to make something that is useful and relevant for the upcoming efforts
      • would be sad if we have a strategy and continue without integrating it
      • keep it alive? paste it in pad
  • funding opportunities
    • nlnet proposal pending
    • some karrot money from foodsharing Sweden project
    • another funding opportunity: https://www.fritz-thyssen-stiftung.de/foerderung/foerderbereiche/staat-wirtschaft-gesellschaft/ @Sofi J
      • research-oriented
      • requires project proposal
      • “AntrĂ€ge können grundsĂ€tzlich nur aus einer Hochschule bzw. gemeinnĂŒtzigen Forschungseinrichtung heraus gestellt werden.”
      • is Siegen interested/ doing this anyway?
    • oc newsletter had a bunch of ideas, see Money Flow place
      • Lush Charity Pot: Nathalie did apply once for foodsharing Festival, smaller projects, don’t like funding travelling costs they write (but could try?), “small & easy”, question of entity
      • didn’t look at others
      • Eramus+: cooperation with groups, we are well positioned for that. foodsharing academy did it (Nathalie might get access to application form), how much coding? maybe design?
    • not very focused on that now

  • Karrot does Göteborg
    • what needs to be done to make it happen?
      • create a place?
      • confirm definit interest from karrot team
      • find a time period
      • combine with foodsharing Sweden workshops and karrot workshops → needs planning
      • how does it fit in the foodsharing Sweden timeline?
        • instance up and running
        • started outreach campaign
        • more realistic: maybe we won’t have that
 depends on when
        • time to work on this together
        • thinking of March
 and set-up instance together
        • or April/ May we’d have the instance already and some groups from Sweden to come as well (more optimistic), could work on other karrot things
        • leaning towards earlier in the year


Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] VII
  • try a visualisation of our strategy on excalidraw [Nick] VIII
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] VII
  • contact VolontĂ€rbyrĂ„ [Bruno] VI
  • fill out OC questionnaire [Nathalie]
  • submit expense for Oct/Nov [Nathalie]
  • check with people about strategy call next week [Bruno]
  • ask butze about https://www.fritz-thyssen-stiftung.de/foerderung/foerderbereiche/staat-wirtschaft-gesellschaft/ [Nathalie]
  • put up a message or poll to find a time period for Göteborg reunion [Bruno]

Date: 2025-12-16 on Karrot
Facilitator: Vas
Minutes: all
Participants: Vas, Bruno, Jay, Nathalie

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11 CET
    • information? any (non-karrot) announcements? unavailabilities?
      • Jay Xmas week?
      • Vas needs to check his rota
    • next meetings:
      • co-working:
        • Wednesday: Nathalie, Vas (maybe), Jay (maybe, depends on workload), Bruno (maybe)
        • Thursday:
      • weekly:
    • pick facilitator for next weekly meeting: let’ see if the meeting is happening

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

4. Discussion points

  • updates
    • no updates
  • strategy call?
  • money circle
    • https://community.karrot.world/t/weekly-call-about-karrot-development-2025/2089/37
    • https://karrot.world/#/group/191/pads/money
    • how much money is left?
      • some confusion about money left on people’s account. Is the 6000 EUR on Nick’s account correct? Did he transfer part of it?
      • for now we trust what’s on the pad, gotta check again with Nick
    • -880,00€/ month team members for October/ November/ December
      • Nick: 400€
      • Nathalie: 250€
        • still outstanding for Dec, 250 till the end of the year, ideally continue with this number, do not need an answer now. let’s see in Jan
      • Bruno: 0€
        • keep at the same 0 rate, if we keep the same will last for 4-5 months, not counting the fsharing sweden money though
      • Vas: 230€
        • need to give back 40
        • Vas needs to transfer the money to the OC then or keep them for Jan
      • Jay: 0€
        • no updates, speaking about the money flow, bit stalled on the app for financial planning, thinking of how transfers could be recorded, plan to come up with a solution for the financial planning
      • Butze: 0€
    • next steps
      • check with Nick on overall balance
      • Nathalie & Nick do outstanding payments
      • bring back to meeting in Jan for ongoing payments
  • work on Foodsharing Sweden [bruno]
    • update and share some questions and thoughts, no need to decide now
    • admin and money related, how to deal with the money
    • checked with Wilhelm, if would be interested in working in this project
    • how we deal with the money flow?
    • we have a budget 73.000 SEK which is 6-7k in euros and need to deliver
      • instance for sweden, with some custom standing pages, menu, landing page etc
      • check with nick and the plugin system
      • could cover things such as travelling to gotenburg
    • Jay:
      • interested on the trip
    • Nat:
      • understood that instance is not on Karrot, but support and development can be
      • would like to define responsibilities (deliverables), which is on Karrot level and which on FSS?
      • balance internal needs and paying non karrot team members, different payrates possible tension
    • Vas:
      • also same questions above
    • Bruno:
      • idea to organise a meetup in gotenburg, for team-reunions but also organise a workshop
      • the instance is not for the karrot-team to deliver
      • aiming to take care of it locally
      • there might be also some cost there
      • distribution of money is a bit tricky, do a partnership with karrot, be delivering this for this amount of money
    • Jay
      • could try to help, but also has a full-time job
    • Nathalie
      • likes Bruno’s project manager alter ego
      • what needs to be delivered?
      • karrot’s part could also be “training and support”
    • Bruno
      • Ć”hat needs to be done from fs sweden side:
        • deployment of own instance
        • customisation of landing page
        • add other static pages to karrot instance
        • also looking for someone to do design
      • karrot could also turn this to a bigger project
    • Vas
      • part of fs sweden budget is allocated to karrot? outsourcing to another community?
        • Bruno: yes
    • next steps
      • further clarify tasks and do ‘milestones’ (money and who is doing what) nlnet-style, could include Wilhelm in that

Next:

5. Actions and Outcomes

  • write to bartosz about csv report [nick] VIII
  • try a visualisation of our strategy on excalidraw [Nick] IX
  • put the redis systemd preserve runtime directory into yuca ansible [Nick] VIII
  • contact VolontĂ€rbyrĂ„ (after release) [Bruno] VI
  • ask butze about https://www.fritz-thyssen-stiftung.de/foerderung/foerderbereiche/staat-wirtschaft-gesellschaft/(waiting for reply) [Nathalie] I
  • Check with Nick for the 6th of Jan to run our Strategy call [Vas]
    • done on activity chat
  • Check with Nick about Karrot money on his account [Vas]
  • check if we could do an invoice to FSS through Open Collective [Bruno]
  • prepare a proposal with milestones on the FSS project [Bruno]

6 posts were merged into an existing topic: Weekly call about Karrot development 2026