Weekly call about Karrot development 2026

Meetings
21

Date: 2026-06-23 on Karrot
Facilitator: Vasilis
Minutes: Bruno
Participants: Vasilis, Nathalie, Bruno

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11:15 CEST
    • information? any (non-karrot) announcements? unavailabilities?
      • Nathalie away mid- to end of July
    • next meetings:
      • co-working:
        • Wednesday: Vasilis, Nathalie (maybe)
        • Thursday:
      • NLnet welcome meetup: Vas (will try), Bruno (maybe)
      • weekly: Vas, Nathalie
    • pick facilitator for next weekly meeting: Nathalie

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] IX
  • start work on Stickers [Vas (lead), Jay (support)] V
  • Eszter will amend pad with time aspects [Eszter] II
  • contact Volontärbyrå (after release strategy) [Bruno] XXII
  • mark group as migrated - add as feature request to forum [Bruno] I
  • start Digital Justice Fund application draft [Nathalie, Vas] I
    • done, submitted
  • archive Luxembourg postal agreement [Nick]
  • inform A4C about Digital Justice Fund [Nathalie]

4. Discussion points

  • updates
  • A4C agreement doc?
  • nlnet next steps
    • meeting on Thursday?
      • We will organise two online welcome meetups. Participation is obviously entirely optional, but we hope at least some of you will enjoy such an opportunity to learn about the rest of your cohort and the amazing things they will be doing. The agenda of the welcome meetup is fairly straightforward: we’ll start with a bit of context about NLnet, NGI and NGI Zero. After that we’ll have a rapid fire round of introductions for those that feel like it (1-2 minutes per human) - giving you a quick overview of who is embarking alongside you and what they will do in parallel to your project. After that we’ll explain the Memorandum of Understanding mechanism, and walk you through the various support services we will be able to provide to you together with partner organisations. Once that is done, we’re remain available to answer any questions you or your team mates might have.

        • 16:30 :moneybag: Money Flow

          NLnet welcome meetup

        • Vas

          • put meeting in the agenda and if things don’t change rapidly he will be there
          • will share back notes with the team

        • Bruno

          • nice that Vas can join
          • we’re used to the process, need to be reminded
          • review old MoU we signed
          • go to meeting and draft MoU
          • dedicated meeting before appointment? see if anything has changed in application
          • part of work related to Eszters work

        • Nathalie

          • meeting on Thursday is a bit more general meeting
          • cannot access the links on the e-mail, asking for some kind of password
          • cannot do anything this week, next week yes
          • can help transfering from application to MoU
          • enough if only two people join the NlNet call
          • who will be the contact, who feels responsible?
      • https://community.karrot.world/t/application-to-nlnet-ngi0-commons-fund/2749
      • https://community.karrot.world/t/ngi0-commons-fund-december-2025/2801/2
      • Next step
        • Vas will join meeting and report back

Next:

5. Actions and Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] X
  • start work on Stickers [Vas (lead), Jay (support)] VI
  • Eszter will amend pad with time aspects [Eszter] III
  • contact Volontärbyrå (after release strategy) [Bruno] XXIII
  • mark group as migrated - add as feature request to forum [Bruno] II
  • archive Luxembourg postal agreement [Nick] I
  • inform A4C about Digital Justice Fund [Nathalie]
  • share WeavLib application on our forum [Vas]
  • Nathalie to contact A4C about doc we signed for our archive [Nathalie]
  • NlNet
    • define contact person (or admin team)
    • draft a plan (MoU) - check if Nick has access [Vas]
    • book an appointment
    • do the work
    • get paid
    • celebrate
22

Date: 2026-06-30 on Karrot
Facilitator: Nathalie
Minutes: Bruno
Participants: Philip, Nick, Nathalie, Bruno

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11:30 CEST
    • information? any (non-karrot) announcements? unavailabilities?
      • Bruno will be travelling/away for most of July, beginning of August
    • next meetings:
      • co-working:
        • Wednesday: Nick (maybe)
        • Thursday:
      • weekly: Nick, Nathalie, Bruno (maybe), Philip (maybe)
  • pick facilitator for next weekly meeting: Vasilitator? Nathalie could do it

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] X
  • start work on Stickers [Vas (lead), Jay (support)] VI
  • Eszter will amend pad with time aspects [Eszter] III
  • contact Volontärbyrå (after release strategy) [Bruno] XXIII
  • mark group as migrated - add as feature request to forum [Bruno] II
  • archive Luxembourg postal agreement [Nick] I
    • nothing to do here
  • inform A4C about Digital Justice Fund [Nathalie]
  • share WeavLib application on our forum [Vas]
  • Nathalie to contact A4C about doc we signed for our archive [Nathalie]
  • NlNet → moved to agenda
    • define contact person (or admin team)
    • draft a plan (MoU) - check if Nick has access [Vas]
      • link from email working now!
    • book an appointment
    • do the work
    • get paid
    • celebrate

4. Discussion points

  • updates
  • nlnet MoU [D]
    • https://community.karrot.world/t/application-to-nlnet-ngi0-commons-fund/2749 our application
    • https://community.karrot.world/t/ngi0-commons-fund-december-2025/2801/2 email with next steps
    • review our milestones and move towards MoU
      • Reactions round
      • Philip
        • sounds legitimate to me, we talked about breaking the silo and self-hosting
        • all good to me
      • Nick
        • self-hosting: worth reviewing the custom pages now, since there’s the CMS thing
        • propose to do a little survey of people using plugins (Bruno, Daniel, other from FSLUX) and try to surface the needs of self-hosting
        • Will’s backend plugin on CoopCloud allows for writing on language of choice but downside of not having access to Karrot’s database. potentially having access to other Coopcloud services
        • breaking the silo: in addition to public signup to have the URL preview, an item to be added, could be included in the public signup
        • another idea for the public signup, a little form with options
        • on usability: how that aligns with what Eszter may or may not do, since there’s very specific things on the milestones
        • things that came up and did not make it into there at all. Any useful things?
      • Nathalie
        • question of how long
          • A: usually one year, worth asking, there may be some flexibility/extensions
        • no comments to self-hosting and breaking the silo
        • about usability: whether the two first milestones are distinct enough, also the question of how it fits with Eszter’s work
        • not attached to adding anything, not proposing any changes
      • Bruno
        • self-hosting: work done so far, does it change anything or build up on that?
        • ask around, survey self-hosted instances
        • breaking the silo, good to keep
        • same reaction on usability part, don’t know in which direction Eszter will work, nice to coordinate, milestones still feel relevant, get Eszters opinion, does is make sense to have those
      • Proposal
        • do not decide on the MoU today, do the survey of self-hosted instance (Nick), get Eszter’s feedback on usability (Nathalie) and have a time-frame for a decision on MoU (three weeks hard deadline - 21/7)
        • comment Nick: curiosity on breaking the silo, whether it could be a mini booking flow, which might have different steps. A question to the group whether that would be great or too much
          • added as a discussion point below
      • Next steps
        • Duration of MoU, Extensions
  • follow-up from resource mosaic [E]
    • what came up in the last 2 weeks?
    • Philip thinking about his involvement in Karrot, not deeply involved in some topics and feeling awkward to vote about it. Do I have the capacity? On foodsharing.de the focus will be on the resource mosaik. Does it resonate with Karrot? Also encouraging Anton to become more involved
    • thinking about whether to step back from his role, or finding his way to contribute
    • has been distracted on the meetings on the other topics
    • Reactions
      • Bruno
        • resource mosaic interesting idea to work on, could be part of karrot
        • see two barriers: capacity to design and build it, usability of it - make it work with all the different groups and needs
        • I like the vision of the resource mosaic, sees a long road
        • thinking about development capacity
        • appreciate bringing up question of involvment
        • how to we bring in people, how do we slowly grow, not everybody needs to sit with all the questions in the meetings
      • Nathalie
        • been thinking about the resource mosaik, a good sign, because it was inspiring and thought-provoking
        • can see how it’s useful for local community organizing and how people could contribute, sharing as community building
        • experience from neighbourhood community, offering a “budget”, and Nathalie avoiding the buy-thing approach
        • one thing that was off-putting: drawing big conclusions from it. Maybe too much to present as a justice, power-sharing or conflict resolution. Resistance towards framing it as the only justice tool
        • regarding Butze’s contribution: how do we align as a team and what is the right time for doing what?
        • a bit hesitant to shift the focus, difficult to bring it together at this very moment
      • Nick
        • noticing more how organic sharing happens, quite a lot of those with the boaties, happening all the time through chat-based tools
        • when there’s a good community and trust network, people do it
        • smaller context: project with particular needs
        • there are different spheres for sharing, and the question is how to define the intermediate circle for sharing and how a tool can be helpful
        • a tool is more interesting in the project-based sphere, like a booking system which is more agreement-based and not like the organic type of sharing which is more trust-based
        • a technical tools is more towards the booking type
        • maybe the commons-booking platform intersects with it
        • endless topics in Karrot, but never enough capacity. Question of whether we will have that
        • get away from me camera!
        • about Butze’s membership: maybe a connection role, not feeling like being part of the team deciding things. Maybe a role that could be created for others too
        • like and subscribe :+1:
      • Philip
        • maybe we could fund it, to get more capacity
        • have to think about the role, about what his contribution would be
  • public sign up idea feedback
    • recap, feedback if that is featuretis
      • from experience of organizing events and needing the sign-up form
      • a form-builder feature
      • we’ve got mockups from previous design processes, but maybe not a form
      • is it out of scope to extend the feature?
      • a form maybe is not necessarily totally tied to the public sign-up feature, but could end up on a signup
    • Nathalie
      • what are the use case: a pickup, or a coordination event, for people outside joining for specific tasks
      • imagine there is some pre-defined structure and you pick a slot
      • answer: yes, out of scope
      • hard to get there, not events or specific tasks one is signing up to
      • a bit opposed to merge it in there
      • remember we kicked it out intentionally in the past
      • generally resistant to change a lot things in the MoU
      • feeling a bit hard to hold something together and now pulling on different directions
    • Q: we kicked out something?
      • A: did not include that work in previous application
      • maybe could connect to make it useful for events
    • Bruno
      • could be part of the design of that task
      • event is type of activity, what information is needed from the participants e.g. contact information
      • see how it fits with participant types
      • it’s about designing it, see how it fits in milestone task, how far do we want to go with this
      • hear more about how you imagine this
      • noticing a pattern: there is an interesting idea, but we don’t build it fully, build seeds for the future
      • agnostic about it
    • Nick
      • makes sense when there is a use case to connect to, maybe existing use cases
      • example: a public sign-up could be just one question, a minimal version
      • could also be integrated into bigger workflows
      • a bolder version: create something for others to adopt
      • explanation: booking system is like signing up to an event. Commons booking system is more about sharing and other things
      • conscious about his featuritis brain, but also being creative with development, likes to open up and create a potential to make it easier to add other concepts on top of it
    • any actions on it?
      • not really, there’s room in the MoU to work with it

Next:

5. Actions and Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] XI
  • start work on Stickers [Vas (lead), Jay (support)] VII
  • Eszter will amend pad with time aspects [Eszter] IV
  • contact Volontärbyrå (after release strategy) [Bruno] XXIV
  • mark group as migrated - add as feature request to forum [Bruno] III
  • inform A4C about Digital Justice Fund [Nathalie] I
  • share WeavLib application on our forum [Vas] I
  • Nathalie to contact A4C about doc we signed for our archive [Nathalie] I
  • do survey on self-hosted instances [Nick]
  • ask Eszter’s feedback on MoU [Nathalie]
23

Date: 2026-07-07 on Karrot
Facilitator: Nathalie
Minutes: Vas
Participants: Nick, Vas, Nathalie, Eszter

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11:00 CEST
      • Nick only first 30min
    • information? any (non-karrot) announcements? unavailabilities?
      • end of July Nathalie is away
    • next meetings:
      • co-working:
        • Wednesday: Vas, Nathalie, Nick (maybe)
        • Thursday:
      • weekly: Nathalie, Vas (maybe), Nick
  • pick facilitator for next weekly meeting: Vas

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] XI
  • start work on Stickers [Vas (lead), Jay (support)] VII
  • Eszter will amend pad with time aspects [Eszter] IV
    • on agenda
  • contact Volontärbyrå (after release strategy) [Bruno] XXIV
    • done!
  • mark group as migrated - add as feature request to forum [Bruno] III
  • inform A4C about Digital Justice Fund [Nathalie] I
    • wrote email on July 1st
    • we got a reply
  • share WeavLib application on our forum [Vas] I
  • Nathalie to contact A4C about doc we signed, for our archive [Nathalie] I
    • wrote another email on July 1st
    • uploaded to Money flow place
  • do survey on self-hosted instances [Nick]
    • ongoing, wrote to Daniel and Wilhem, got some feedback/info
  • ask Eszter’s feedback on MoU [Nathalie]

4. Discussion points

  • updates

  • design work with Eszter

    • https://karrot.world/#/group/191/pads/eszter-karrot
    • 5 working days on that
    • having a workshop together, have some building blocks, more hands-on workshop then, iterative design approach
    • check/review the agreement
    • Nick
      • seems good, outline is a workshop process, had one now another which will inform the design
      • NLnet is the most difficult for me now, we can feed it in the Mou but there is some time pressure with that, can schedule in some design interventions, 1-2 ppl a subteam, I would consent as it is now
      • find the 2 ppl of the subteam
    • Vas
      • quite clear,
      • 5 consecutive days? yes, need to be August, prep workshop separate day
      • iterative way, do another workshop?
        • if its 5 days,: workshop - design - a checkpoint/workshop with the 2 ppl of the subteam - work more - amendments
      • happy with what I read
    • Nathalie
      • its a good document, has the clarity and the work can start
      • how it binds together with NLNet, revised MoU by next week? Signing can happpen quite soon and first workshop can be part of NLnet
      • focus on navigation is aligned with what we ve put in our NLnet application,
      • change the wording of our milestones
    • Bruno
      • agree with Nathalie, fits well to the MoU, can start the work afterwards, its about the wording
      • Q: first workshop? Try to include ppl from outside the Karrot-team? If so…?
      • Est: We could, one person could be (Nat & Bruno have these 2 hats!)
    • Eszter
      • agreement sounds good, timings: August (quite free)
    • Proposal: Agree to ”Karrot working agreement with Eszter”, term: end October, small group: Eszter, Nick, Bruno
      • We got consent
    • Next steps
      • schedule design workshop [Bruno, Nick, Eszter]
        • will be preparing the playground for the workshop
        • find a date? Small group can take of it:
          • Bruno: 1 week of August could work, second half of August more available to join a workshop
          • Ezster: beginning of August, could probs work for Bruno as well
          • Nathalie: August 10th onwards will be available
          • Vas: generally available throughout august
      • review nlnet draft (see below)
      • decide when to sign MoU, maybe even include workshop

  • MoU check-in - working towards a “new” draft [E]

    • Increase usability and interface refinements 9000 EUR
    • We want to reduce the complexity in user experience and improve overall usability for all groups facing the complexity of self-governance. Also, Karrot still has some legacy interface and navigation design based on food saving type of groups. As new types of groups start using and experiment with Karrot, we started to identify different needs that do not necessarily require a new set of features, but that could be satisfied by making some tweaks and improvements to existing ones.
    • Milestones 9000 EUR
      • Improved message navigation (interface focus) 2500 EUR
      • Improved design of sidebar and menus (interface focus) 2500 EUR
      • Tweaks to make Activities-feature more useful for events (usability) 1500 EUR
      • Add calendar view to Activities (usability) 1500 EUR
      • Usability and interface refinements documentation 1000 EUR
    • Reactions: Change wording?
      • Eszter
        • Improved design of sidebar and menus (interface focus) 2500 EUR ← that is quite broad and would include things I wll be working on
        • Calendear view and Activities for events sounds more specific, not sure if that’s gonna be withing the main scope of what I ll be working on
        • first 2 points fit what we’d be doing
      • Bruno
        • good to see that there is some overlap
        • if there is sth else that might show up would be worth including/changing
        • is there sth to add? Do we miss sth Eszter?
      • Nathalie
        • Documentation could be done by one of us (Karrot-team), could be a video
        • Tweaks to make Activities-feature more useful for events (usability) ← woudnt see that in Eszters work
        • wording of Activities might need tweaks, maybe its not more about redesign the whole feature
        • Improved message navigation (interface focus) 2500 EUR
        • Improved design of sidebar and menus (interface focus) 2500 EUR
        • could we merge the above? or change the splitting in design and implementation
      • Vas
        • see the point of merging 1 or 2 or re-write slightly
      • Eszter
        • We dont need to decide on that now, make a plan regarding the timeline, when we d like to sign the MoU?

Next:

5. Actions and Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] XII
  • start work on Stickers [Vas (lead), Jay (support)] VIII
  • do survey on self-hosted instances [Nick] I
  • ask Eszter’s feedback on MoU [Nathalie] II
  • schedule design workshop in August [Bruno, Nick, Eszter]
  • upload the agreemet on our Karrot-team and Feedback group [Vas]
  • check minutes on the MoU [Vas]
  • draft 1 and 2 milestones merger [Nathalie]
24

Date: 2026-07-14 on Karrot
Facilitator: Vas
Minutes: Nick
Participants: Vas, Nick, Nathalie, Bruno

1. Opening

  • 10 min Check in
    • attendance (fill in above)
    • duration: 11:00 CEST
    • information? any (non-karrot) announcements? unavailabilities?
      • end of July Nathalie is away also Nick
      • Bruno travelling next week
    • next meetings:
      • co-working:
        • Wednesday: Vasilis, Nathalie
        • Thursday: Willhelm could do a show and tell about the CMS (thursday or monday) (postpone…)
      • weekly:
  • pick facilitator for next weekly meeting:

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] XII
  • start work on Stickers [Vas (lead), Jay (support)] VIII
  • do survey on self-hosted instances [Nick] I
    • got quite a lot of feedback (done)
  • ask Eszter’s feedback on MoU [Nathalie] II
    • happened in last meeting (done)
  • schedule design workshop in August [Bruno, Nick, Eszter]
    • 2nd half of august for bruno
  • upload the agreement on our Karrot-team and Feedback group [Vas]
    • done, agreement between karrot and eszter
  • check minutes on the MoU [Vas]
    • done
  • draft 1 and 2 milestones merger [Nathalie]
    • done

4. Discussion points

  • updates
  • MoU decision
    • https://karrot.world/#/group/191/pads/nlnet
    • Reactions
    • Nick
      • 1. would like to show 1) milestones to tech people for feedback
      • 2. add to breaking the silo: link preview for 1500 EUR e.g. for posting karrot links in messenger groups
      • 3. for task 3: use UX, delete bracket text
    • Round
      • Bruno
        • 1st point sounds good, see what’s needed for change, if any change, just do it and submit it, so we don’t stall
          • good possibility wilhelm can continue contributing to karrot in the future, nice to keep him in the loop and keep engaged, has capacity, skills, and can work independently
        • 2nd one, good to remember that, would be happy to have that included
        • 3rd makes sense, totally
      • Vas
        • agree with all the points
        • do we need to update our internal deadline for MoU agreement?
      • Nathalie
        • all sounds good
        • had been thinking to write UI/UX, happy to use UX working + without text in brackets
        • link preview thing makes sense
        • have a concern with adding more money
        • patience with this is going down a bit, not sure how it works with nlnet
        • if it needs more process, then could take out a milestone to make the money less again
        • if we take too long, the timing might not work well with Eszters work
        • wondering about our balance and money
        • happy to make a decision now, and wait for feedback, if it doesn’t bring up issues then we can go forward
      • nlnet: “Note that the final amount of the grant will be determined in dialogue with you, also taking into account any new insights during the negotiations.”
      • Nick
        • got a way forward, need to make tweaks
        • likely to get consent

Next:

5. Actions and Outcomes

  • play with some designs/mockups/ideas on supporting users self-identification [Jay] XII
  • start work on Stickers [Vas (lead), Jay (support)] VIII
  • schedule design workshop in August [Bruno, Nick, Eszter]
  • share the plugin nlnet proposal with concerned people to solicit feedback [Nick]
  • update nlnet editor with new changes [Nathalie]
  • book nlnet appointment [Nick]