Weekly call about Karrot development 2024

Date: 2024-05-28 on Karrot
Facilitator: all
Minutes: all
Participants: Bruno, Nick

1. Opening

  • 10 min Check in
  • 5 min ADMIN
    • attendance (write down participants)
    • duration: (took us 1h to get to this point…) half an hour more, 11:10 or so
    • information: any (non-karrot) announcements? unavailabilities?
    • next meeting: weekly meeting and co-working
      • co-working: nick and bruno
      • meeting: nick…
    • pick facilitator for next week: Nick

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • continue work on navigating upcoming activities [Jay]
  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • notes and actions items from Siegen on the forum [Nathalie]
  • technical design of signup public activities on Codeberg [Nick]
  • discuss starting the meeting half an hour later next time, or on karrot [anyone]
    • discuss on karrot group

4. Discussion points

  • mini updates?

    • new look released
      • noticing mixed reaction in warsaw group 50/50 :slight_smile:
    • plugins nearly ready
      • doing frontend only is documented on docs
      • frontend env setup and plugin env setup
      • more docs to be written
      • plugin also in the backend, need to update recipe on coop-cloud
      • no docs for it yet
      • plan: instance configuration UI
      • examples of what a frontend plugin could do
        • adding new pages and menu entries
        • slots that put content in specific places (like a component on the wall, on top or below)
  • Polls design:

    • Penpot - Design Freedom for Teams
    • starting polls from group walls and place walls
      • but what about in the middle of a thread? probably not
    • added a “choose by role” option, of who can participate
    • no time limits
    • things left to work out
      • notifications
      • “poll has been created!”
        • bell notifications
        • push notifications
        • email notifications
        • notification configuration
      • list polls in their own section too?
      • who can start a poll?
        • whether it’s configurable?
        • anyone
        • can a newcomer create a poll only open for editors?
        • only editors should have the role selector
    • what does it look like in Loomio?
      • Top-level thing is Decisions
        • proposals, polls, meeting
        • a number of different things for how to do each of those, like templates

for when butze is back from hawaii:

  • membership for butze process

5. Actions and Outcomes

  • get feedback from others on the polls mockup [Bruno]
  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • notes and actions items from Siegen on the forum [Nathalie]
  • technical design of signup public activities on Codeberg [Nick]

6. Closing Ceremony

  • 10 min
  • checkout

Date: 2024-06-04 on Karrot
Facilitator: Bruno
Minutes: Nathalie
Participants: Butze (left early), Jay, Nathalie, Bruno, David (later)

1. Opening

  • 10 min Check in
  • 5 min ADMIN
    • attendance (write down participants)
    • duration: started later, to the hour 11 CEST
    • information: any (non-karrot) announcements? unavailabilities?
      • Jay on holidays, back in a month (8th July)
      • Butze on a train next week Tuesday, will check connection
    • next meeting: weekly meeting and co-working - yes
    • pick facilitator for next week: Nathalie

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • get feedback from others on the polls mockup [Bruno]
    • got feedback in karrot group
    • enable highlights in penpot, otherwise you might not find it
    • Jay will still give feedback
  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • notes and actions items from Siegen on the forum [Nathalie]
  • technical design of signup public activities on Codeberg [Nick]

4. Discussion points

  • membership for butze process [D]

    • checking our agreement again
    • Karrot
    • Membership policy
    • reviewed qualities for members
    • Propsal: Grant membership to Butze (Philip)
    • Reactions
      • Bruno
        • qualities checked for Butze
        • sees natural to have Butze part of the team
      • Nathalie
        • fun to review the qualities
        • good to take the time
        • still wondering what his Karrot contribution will be in the future, beyond Phd
        • had a nice contribution with the hackaton for example
        • wonders which other Karrot work interests Butze, like design, legal entity,…?
        • happy to formalize membership
      • Jay
        • agree with points mentioned
        • work as cohesive group, help out each other
        • good comprehensive list of qualities
      • Butze
        • very high values to live up to
        • aware of qualities
        • happy to become a member, process started last year in august when I met Nick in Luxembourg
        • contributions: not too many conrete tasks, needs to find my place still
        • achieve new vision and mission for myself
        • make connections between academia and karrot
        • connection and networking, working with foodsharing e.V.
    • Consent
      • Bruno and Nathalie consent!
    • Next Steps
      • add Butze to people page [Nathalie]
      • add Jay’s membership to agenda soon
        • intention to join the team
        • how to do onboarding, who is bringing this to the agenda?
        • when is the time to formalise?
        • don’t see a reason to not put this in the agenda, trust the process
        • ok that it’s not defined
        • maybe after Jay is back, but she is happy for us to discuss this beforehand
          [Butze left]
  • mini updates [R]

    • mockup for polls ongoing
    • Nick working on plugins
  • moving tuesday meeting 30min later, start on 10:00 CEST

    • decided in chat
    • changed on karrot already
    • affirmed in the meeting
  • financial host

    • Proposal - HedgeDoc
    • proposal to apply to allforclimate fiscal host
    • start a legal entity on our own or apply for fiscal host
    • issue: getting the payments from nlnet, not wanting to use private bank accounts
    • legal entity also includes questions of governance
    • went through options on last coworking with Bruno and Nick
    • All for Climate: EU-based, low fee, aligned values
    • Proposal
      • Choose Fiscal Hosting over founding our own legal entity
      • Choose Allforclimate as the fiscal host we want to apply to
    • Questions & Reactions
      • Jay
        • Q: How do legal entity and fiscal host go together? could still found legal entity later and stopü using fiscal host
        • Q: which countriy for legal entity? proposal is not to found entity now, but we considered UK but also other european countries
        • it’s economically easy to found something in France
      • David
        • good experience with them
        • everything is transparent
        • people can earn money, upload bills and money got transfered within a few days
        • income/ outcome visible on website
        • documentation available
        • create invoices, accept donations
        • a lot of work is done by the platform
        • keep getting active without worrying about bureaocratic stuff
        • we don’t have a legal entity
      • Bruno
        • Q: Use All for climate when signing a contract? [my connection broke down]
        • Q: Do we need to be Freelancers to access money? Yes! Everyone is responsible for their own taxes in their countries
      • Nathalie
        • clarification: All for Climate is a fiscal host using Open Collective which is the transparent platform
        • I do like it!
    • Consent Round
      • Choose Fiscal Hosting over founding our own legal entity
        • no objections - consent!
      • Choose Allforclimate as the fiscal host we want to apply to
        • no objections - consent!
    • Next Steps
      • Apply to Allforclimate :slight_smile: [let’s do it in coworking]
  • budget [R]

    • is there a report on the budget?
    • is it only visible for members ofthe team?
      • Bruno
        • no formal budget so far
        • 3 sources od income: nlnet, projet in gothenburg, donations
        • common pot of money
        • support contributors livelyhood
        • we had money circles, notes are public
        • we define who is getting what in these meetings
        • initally idea of providing (limited) basic income
        • shifting towards money for time/ contribution recently
        • thinking about our personal needs still
      • Jay
        • Q: do you ever pay external people (not karrot team)? we’ve done that once or twice, proposal for a person to work on a feature
      • Nathalie
        • interesting discussion about reporting
        • that will be a good thing with fiscal host
        • last meeting about money May 14th
        • currently spending EUR 1130/month
        • using Nick’s account, only 3k left
        • not really planned, but aware
        • still need to plan
        • not much security in terms of long-term savings
        • still figuring out how we relate to Karrot in terms of income
    • question answered :slight_smile:
    • no sense of urgency on this
    • although money agreement is probably due to review some time soon

when Jay is back

  • Jay’s membership

5. Actions and Outcomes

  • continue working on the mockup for polls [Bruno]
  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • technical design of signup public activities on Codeberg [Nick]
  • add Butze to people page [Nathalie]
  • Apply to Allforclimate :slight_smile: [let’s do it in coworking]

6. Closing Ceremony

  • 10 min
  • checkout

Date: 2024-06-11 on Karrot
Facilitator: Bruno
Minutes:
Participants: Nick, Bruno, Nathalie

1. Opening

  • 10 min Check in
  • 5 min ADMIN
    • attendance (write down participants)
    • duration: 1h
    • information: any (non-karrot) announcements? unavailabilities?
      • Bruno traveling for a week
    • next meeting: weekly meeting and co-working
      • co-working probably
      • next week yes!
    • pick facilitator for next week: Nick

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • continue working on the mockup for polls [Bruno]
  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • technical design of signup public activities on Codeberg [Nick]
  • add Butze to people page [Nathalie]
  • Apply to Allforclimate :slight_smile: [let’s do it in coworking]

4. Discussion points

when Jay is back

  • Jay’s membership

5. Actions and Outcomes

  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • technical design of signup public activities on Codeberg [Nick]

6. Closing Ceremony

  • 10 min
  • checkout

Date: 2024-06-18 on Karrot
Facilitator: Nick
Minutes:
Participants: Nick, Philip, Nathalie

1. Opening

  • 10 min Check in
  • 5 min ADMIN
    • attendance (write down participants)
    • duration: up to the hour 11:00 CEST
    • information: any (non-karrot) announcements? unavailabilities?
      • Nathalie: FOSC SOFA: restructuring of sofa, focusing on community of practise (meeting, talking about governance, open source, sociocracy, etc.)
        • next community of practise july 15th 17:00 CEST
        • could be a nice space for karrot people to join
    • next meeting: weekly meeting and co-working
      • co-working tomorrow: nick, … maybe butze, maybe not
      • meeting next week:
      • co-working next week: heads up → all for climate onboarding call
    • pick facilitator for next week: maybe Nathalie

2. Consent to agenda

  • 2 min

3. Review last week’s Actions/Outcomes

  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • membership payment coop-cloud [Nick]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • technical design of signup public activities on Codeberg [Nick]

4. Discussion points

  • mini updates?
  • start review of money agreement
    • Karrot
    • 5 min to read through
    • round to share reflections
      • Butze:

        • a good general text, easy to comprehend for people in Karrot project or used to alternative circles
        • for people not in alternative circles, maybe hard to comprehend what it actually means, e.g. “what is the money circle?”
        • says describe an agreement for each contributor, but what would it look like? amount of money, could make it more tangible
        • in second paragraph there is an explanation of how we see money, would move that into the beginning, “How do we perceive money”, so add some headings, preface, process, how we get to outcomes. with the goal to help outsiders to understand it better
      • Nathalie:

        • I like it a lot
        • saw we made a few amendments from initial draft
        • feel like it makes sense
        • like this second paragraph, feels quite honest, e.g. within our financial capacities
        • two minor points:
          • practicalities of money circle, usually takes place in the weekly meeting, not after it
          • a bit more tangible about how we do things, could mention opencollective, e.g. “all money is collected by our fiscal host and visible on our opencollective”
            • like the sense we have one collection of money, and we had some confusion before about whether to have extra agreements
            • nice sense to collect all the money from all the sources (not thinking about who brought it in), and then redistributing it
        • agree with butze, as the agreement could just be amount of money
      • Nick:

        • likes it
        • balance between dreamy vision (working from our hearts) and lived realities, we touch both parts of that
        • broadly made sense to me
        • guideline: what do we mean by this, e.g. the 3 categories for contribution, we’re open to have discussion about others
        • guideline could mean different things to different people
        • external work not reflected here, difference between core work and ‘external’ work, nothing to add here, but reflecting that not all situation are covered (where there is an overlap in projects)
        • ‘in the meeting’ could just edit that
        • tangible is good, but could be prescriptive instead of descripive
        • example section could be nice, based on previous examples
        • once we get fiscal host, we can include it in there and link it
        • not about who brings it in, support making that explicit
        • adding headings, would be happy about this: ideoligical background, what we’ll discuss, facts/ how it happens, examples - but not too motivted to work on headings myself, as it’s not a very long text
      • Butze:

        • also stumbled on the word “guideline”, not sure a good other word
        • it also says “people who use Karrot”, so users of karrot could come and ask for money?
        • also don’t see the need to structure to the text, but would be happy to
      • Nathalie:

        • also not so motivated to structure the text with headlines, as it seems not too long
        • am motivated to add a sentence here or there:
          • opencollective
          • one money pot
          • and in the weekly meeting, not after
        • openness of money circle? didn’t advocate for it to be so open, but happy with it, currently we only give money to karrot team, open to some flexibility, in reality mostly people in karrot team
      • Nick:

        • openness, just leave it, but how do people know? they would need to be aware of it and somehow active
        • we did pay travel costs to karrot users, could be worth having a section, making it clearer for other people
      • next steps

        • bring back a new version of text to a meeting (maybe after fiscal host?)
  • stirtoaction festival?
    • Festival Tickets 2024
      • we would all like to go, looks nice
      • maybe next year find a festival and go there together
      • happy for Nick to go and we could support financially
      • how would karrot representation look like? e.g. chatting to people, connecting projects
      • proposal: Nick can buy a ticket with Karrot money for £90 and represent Karrot as well as do his own things there
        • Butze: I consent
        • Nathalie: I consent
        • Nick: I consent

when Jay is back

  • Jay’s membership

5. Actions and Outcomes

  • write feedback and reflections on suggesting Karrot to parents coop [Bruno]
  • change getting started guide to give the right message for undergrad students [Vasilis]
    • summary is that we dont have capacity for dev contributions but HCIish things yes
  • technical design of signup public activities on Codeberg [Nick]
  • bring back a new version of text to a meeting (maybe after fiscal host?) [Nathalie, nick happy to co-work on it]