Date: 2023-02-17 19:30 CET
Where: Jitsi Meet
Facilitator: -
Minutes: All
Participants: Nick, Nathalie
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration:
information: any (non-karrot) announcements? unavailabilities?
Nick has finished work project! (almost)
next meeting:
next Wednesday co-working: Nathalie will be there
next Friday general:
Nathalie won’t be present
Nick might be cycling, but maybe can join
pick facilitator for next week: you? your karrot needs you!: see who’s there
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
5 min
engage with feedback workflow on forum [Bruno et al]
4. Discussion points
Update from Daniel about meeting [R]
they decided the funding won’t cover a dedicated meeting
we can do something independent
Nathalie would be up for thinking about doing something
also previous idea we had about going to Gothenburg
unclear what the festival will consist of and what we would prepare for it, Nathalie quite clear to go to it, unless really small
not officially announced yet
proposal for mariha’s email
Next week:
continue conversation about how to join the Karrot Team in general [all]
check how groups are doing with new features [E] (next time)
new meeting time idea? [E]
5. Actions/Outcomes
Nick reply to Daniel about idea to organise independently for meeting, and also mention we’ll think about a workshop
wait for more reactions until next co-working time and reply to mariha [Nathalie]
6. Closing Ceremony
10 min
checkout
Appendix
What the letters mean
[R] Report (clarifying the information) - one person telling something to everyone, so everyone gets clarity on the subject, can ask questions, but not really discussion, etc…
[E] Exploration (hearing reactions & ideas) - share our opinions, reactions, hear what everyone things, what’s on our mind
[D] Decision (making a decision) - final step to bring it together to a decision
List of ideas
making a tutorial(s), writing a manual/ handbook
future roadmap, plan
general direction for Karrot in the future? the conceptual part? more solid conceptual framework
in-person meeting \o/
‘Legalizing’ Karrot? Building a legal structure we can use?
bank account/ legal structure, open collective
governance structure of Karrot/ Karrot ‘team’
Server structure, connection with foodsharing.de and Kanthaus
sociocracy and Karrot
how sociocracy could support groups
idea of commons
if there are shared resources in a group = commons (e.g. a cargo bike) can this be supported by karrot. e.g. a feature for shared items? \
finding partnerships to do some on the ground testing. related to a funding or part maybe. (the idea that Nick explained recently), a network, a movement, outreach a more specific one
outreach: establish network and partnerships, maybe connecting with local movements
re-contextualise Karrot towards a more-generalised tool
a mind map of these ideas, to visualize and revisit them → have a focused session on this
Date: 2023-02-24 19:30 CET
Where: Jitsi Meet
Facilitator: Vas
Minutes: Vas and all
Participants: Vas, Nathalie, Nick, Bruno
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 9 CET, Nathalie leaves at 8:30 CET
information: any (non-karrot) announcements? unavailabilities?
next meeting:
next Wednesday co-working: Nathalie will be there, Vas as well
next Friday general:
pick facilitator for next week: you? your karrot needs you!: open to everyone/ Vas
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
5 min
engage with feedback workflow on forum [Bruno et al]
ongoing
Nick reply to Daniel about idea to organise independently for meeting, and also mention we’ll think about a workshop [Nick]
moved to discussion
wait for more reactions until next co-working time and reply to mariha [Nathalie]
done
4. Discussion points
new meeting time idea? [D]
we don’t like the fridays that much, was a compromise
Bruno: could do meetings during the day, almost everyweekday beteween 9-15.00 but not fridays or tuesdays. Evenings mondays and tuesdays
Nathalie: happy to move from friday. afternoons have calls. mostly mornings would work before 13.00-14.00. Could do mondays or tuesdays and tuesday evening.But wd prefer morning slots.
Nick: prefer mornings. Quite flexible. Not thursday morning. Early in the week slightly better, not wkends
Vasilis: avoid weekends, regular meeting monday morning, monday later, other mornings are ok, early on during the day
Proposal: Tuesday 10 CET? 9 UK time
yeah!
Q: Starting next week? yes!
Nick reply to Daniel about idea to organise independently for meeting, and also mention we’ll think about a workshop [E,R,D]
no funding for the meeting, but festival will happen, around mid august?
had the idea to do it anyway. use karrot money or no money
Nathalie: super nice t meet in person. doing it not in lux but in gotenburg.
team focus or engaging with groups?
organisational bit can be a burden maybe. depending on how much energy we put…
bruno: come to gotemburg! but open for other places as well. Maybe define a deadline?
vasilis: would be fun to meet up, team focus/ group engaging?, likes the idea of göteborg, how open we want it to be? invite others? what could Bruno organise, maybe a community center to sleep in.
bruno could help with logistics for sleeping more people.
it would be nice to stay in the same place, share, cook etc if that is possible
festival/workshop [E]
Bruno: would be fun and fine! if its mid aug its maybe gonna be easier for me. sounds duable
Nick: Yes on my radar. hazy about what a workshop is.
Vasilis: Yes on my radar. hazy about what a workshop is.
Nathalie: Yes on my radar, i think in Luxmeburg, up for a wkshop but also up to hear from daniel more. i do think they also provide cost for workshops.
new rhythms? [E]
how to fit karrot in work life, provide financial situation
how do people feel about rythm of Karrot in their lives
work out what we need to do
time fo evolution? Karrot team definition, crowd funding
do other/ external work e.g. for tech coop or other orgs
Nathalie: forgot to take notes here…not sure how i feel about karrot sometimes, the priority it takes in my life… CSX idea
Bruno: another wave of acitivity, planning and doing stuff, more time to plan and do things now, need for life designing
Vasilis: very interesting topic, how can Karrot become more of a daily part in our lives, when we got funding there was more energy there last year, we also had more pressure, that was bad, like to think about a more hybrid way, Karrot has potential for funding, other projects have more money than we do, can not write code, limited in participation to Karrot, transition would also require legal status esp. for
good project, worthy a push!
non-coding input is super valued
a lot of reflective space in Karrot, moving slowly
resilient way of doing things vs rocket ship to the moon
continue conversation about how to join the Karrot Team in general [E] [all]
check how groups are doing with new features [E] (next time)
find a time for design session/ retrospection session on roles feature [D]
[R] Report (clarifying the information) - one person telling something to everyone, so everyone gets clarity on the subject, can ask questions, but not really discussion, etc…
[E] Exploration (hearing reactions & ideas) - share our opinions, reactions, hear what everyone things, what’s on our mind
[D] Decision (making a decision) - final step to bring it together to a decision
List of ideas
making a tutorial(s), writing a manual/ handbook
future roadmap, plan
general direction for Karrot in the future? the conceptual part? more solid conceptual framework
in-person meeting \o/
‘Legalizing’ Karrot? Building a legal structure we can use?
bank account/ legal structure, open collective
governance structure of Karrot/ Karrot ‘team’
Server structure, connection with foodsharing.de and Kanthaus
sociocracy and Karrot
how sociocracy could support groups
idea of commons
if there are shared resources in a group = commons (e.g. a cargo bike) can this be supported by karrot. e.g. a feature for shared items? \
finding partnerships to do some on the ground testing. related to a funding or part maybe. (the idea that Nick explained recently), a network, a movement, outreach a more specific one
outreach: establish network and partnerships, maybe connecting with local movements
re-contextualise Karrot towards a more-generalised tool
a mind map of these ideas, to visualize and revisit them → have a focused session on this
Date: 2023-03-07 19:30 CET
Where: Jitsi Meet
Facilitator: Vas
Minutes: Vas and all
Participants: Vas, Nathalie, Nick, Bruno
reth
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 1:30h, Bruno leaves 1h in
information: any (non-karrot) announcements? unavailabilities?
next meeting:
next Wednesday co-working: Nathalie will be there, Vas as well
next Tuesday general:
pick facilitator for next week: you? your karrot needs you!: Bruno
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
4. Discussion points
time for the meeting [E,D]
Bruno: maybe we start 30mins earlier or check if can change the next thing
Nick: is up for trying 30 mins earlier but how about another day as well?
Nathalie: 30mins would work for me
Vasilis: 30mins earlier the same day
continue conversation about how to join the Karrot Team in general [E] [all]
What this topic is?
Nathalie: sometimes I do wish for places where the structures are clear, there is a lot of fluidity in Karrot, wonder if that is too much for me sometimes? How responsible I feel, effort I put? Is it just an open call? Do have a lot of sympathy for structure. Defining membership. Defined doesnt mean closed. Potential to the design feature of roles. Was wondering if we want to use this feature more e,g, approved can be karrot-team ppl, karrot friends etc. Governing members and asosciated members, my hope is to have more ppl engaged in the governance. The idea of growing the team but being open as well. a. Community org, b. software work?. More ppl coming into the technical. How a new developer get invlolves for example. Could it be a seperate circle?
I like the ideda of connecting with fosc.
Summary: will be happy having a better team definition.
Nick: reaction to above is excitment! Design our organisatinal structure. On the basis of sosiocracy. Use a sort of consent process to make a constitution of Karrot. The need of the contributors. The need of the users, the needs of software itself to be a viable entity. Transition point/inflection point to inform a structure that can better serve those needs. Personal situation: want to flow in money doing software that feels good to me. Some with Karrot, some working with tech coops.
Bruno: thinking along…I agree with the most, we need to start defining things, maybe a governing structure. ‘Who is part of the Karrot-team?’ Defining a membership team and consent. Finding other spaces for ppl to contribute. Democratising and participatory, general assembly? what are the fora the ppl can join to. How we incorporate the feedback? Its a process, we wont have answers now. We can start finding what the Karrot team is, what the scope is, what are the decisions.
write down some proposals/ideas. some concrete proposals.
Vas: lot of interesting comments, likes the momentum, move into a bit more structure, very amazed by fluid organising in the beginning, now becoming something more ‘concrete’, thinking about the idea of sociocracy, inital mapping, possible circles that could operate, how do you open up the process to groups? e.g. foodsaving Leuven - how could they participate?, rethink Design Session and prioritise this topic to design our organisation,
Nick: would like to spend time on that. Organisational transformation in a concent way. Dont want that be rushed despite my personal scale. Can screw up the dynamics so I m consious of that. Article: women in os tech.
Def positive in finding more sources of funding.
-Next steps ideas:
collect together organisational structure models (e.g. article from John)
maybe open a forum thread?
Design Process on our governance
-Nathalie: have a draft of csx to further discover. I m on this topic. Happy to thik of this, for us is fun to do the mapping things. Excited to get togethere with fosc and see what their prompts, questions. Idea of going through this together is beneficial for fosc as well.
-Bruno: maybe we can aim to dedicate 30mins of each meeting where we continue on this. To keep it steady.
-Vasilis: likes idea of getting connected with FOSC, external collaboration could give us a boost, interesting what they would say, different angle on Karrot, before reaching out to them: draft of what we are working on, make an extra document/ map of our topics and ideas, proposal: 30min in the next meetings, make something we can shar with external people and share it with FOSC later on. Writing down open questions and needs
Nick: do we plant sth first and get an external need? Needs first or a model that can hold our needs? Chicken or egg problem? Inherit messiness in this process. Little steps in different directions. Different diverse inputs. I feel limited whilst on the trip. I can imagine writing up some thoughts to go on the forum post. 30min standing agenda item. Check in ‘how is our csx learning exploraiton going?’.
Standing agenda point?
conctacting fosc people? try and get call after the 18th of March [Nathalie introduces each other]
jot down some thoughts [Nick to initiate that?]
check how groups are doing with new features [E] (next time)
can be a feedback session.
data: have groups using those new features? can we see that through grafana?
data is a bit to feed in more human processes. data can give a good initial sense.
unling the feedback session to design sessions. make a community cafe style feedback session?
community cafe? a meeting with groups?
a community cafe is beyond karrot? can be sharing experiences about foodsaving/sharing.
starting point with the ppl that we already engaged. Dave daniel or more ppl? see if they want to participate. General feedback with a special curiosity on new features. Improvements ideas. Could fit in the process of collecting feedback.
could be called a feedback session
make a time poll for a feedback session
find a time for design session/ retrospection session on roles feature [D]
would like to discuss roles vs membership
5. Actions/Outcomes
change the forum post accordingly [Vas]
chnage the activity series [bruno]
write to Daniel [Nathalie]
engage with the thread about festival and workshop [all]
engage again with the thread on new features ane suggest a time to meet and discuss and find a day for a co-working/design session [vas]
conctacting fosc people? try and get call after the 18th of March [Nathalie introduces each other]
jot down some thoughts [Nick to initiate that?]
make a time poll for a feedback session [vas]
6. Closing Ceremony
10 min
checkout
Appendix
What the letters mean
[R] Report (clarifying the information) - one person telling something to everyone, so everyone gets clarity on the subject, can ask questions, but not really discussion, etc…
[E] Exploration (hearing reactions & ideas) - share our opinions, reactions, hear what everyone things, what’s on our mind
[D] Decision (making a decision) - final step to bring it together to a decision
List of ideas
making a tutorial(s), writing a manual/ handbook
future roadmap, plan
general direction for Karrot in the future? the conceptual part? more solid conceptual framework
in-person meeting \o/
‘Legalizing’ Karrot? Building a legal structure we can use?
bank account/ legal structure, open collective
governance structure of Karrot/ Karrot ‘team’
Server structure, connection with foodsharing.de and Kanthaus
sociocracy and Karrot
how sociocracy could support groups
idea of commons
if there are shared resources in a group = commons (e.g. a cargo bike) can this be supported by karrot. e.g. a feature for shared items?
finding partnerships to do some on the ground testing. related to a funding or part maybe. (the idea that Nick explained recently), a network, a movement, outreach a more specific one
outreach: establish network and partnerships, maybe connecting with local movements
re-contextualise Karrot towards a more-generalised tool
a mind map of these ideas, to visualize and revisit them → have a focused session on this
find a time for design session/ retrospection session on roles feature [D]
would like to discuss roles vs membership, getting the concept clear
do a design process
would be nice to see how groups are using it, do it after/during the feedback session maybe
Nathalie has some ideas, but when/where should it be shared?
a quick one now then get the feedback
been thinking about the definition of roles, now it’s more connected to membership
role allows you to do something
assigning some specific tasks is what a role is (relating to sociocracy)
approved role and trust giving is more like a membership type
operative roles, like participant types: how can they be displayed?
volunteer, grassroots organisation might have a bigger need to define different types of membership
Reactions
questions: what should be coded and what’s open for the group to decide? editor a special role, leave it like that, approved role linked to participate in acticities, unsure what else should be in the software
roles related to participant types, comes and goes
new onboarding process involced new type of membership
idea of badges (board member etc)
would like clear concept of this besides the technical implementation
useful to think about what groups are like, make patterns visible, user and group needs
what do we want to support with Karrot?
exisiting groups and existing features, how to fuse the concepts
nothing in the software which is causing harm
love to enage with this kind of abstract thinking
editor role came out of a need for an admin function, more like a reaction
be more intentional about design in the future
draft making could happen already
create a thread on the forum is one idea
Nathalie could take responsibility - think about it
Date: 2023-03-21 meet.jit.si/karrot
Facilitator: Vasilis
Minutes: Vas
Participants: Bruno (kind of), Nathalie, Nick, Vasilis
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 1:30h
information: any (non-karrot) announcements? unavailabilities?
Nathalie offline thursday-sunday
next meeting:
next Wednesday co-working: its happening
Nick,Vas,nathalie
next Tuesday general:happening
pick facilitator for next week: you? your karrot needs you!: mNick
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
make a time poll for a feedback session [vas]
engage again with the thread on new features and do a time poll to meet and discuss and find a day for a co-working/design session [anyone co-working]
reply fosc e-mail [someone co-working]
rewrite thoughts and questions about EU funding to put it back into the matrix channel [Nick]
look into and prod about nlnet funding, and/or explore in co-working tomorrow [Nick]
4. Discussion points
standing point: organizational structure [E]
general check in or pick a specific aspect and share some thoughts?
Nick: I think we have a need, and there are some nice ideas, practical bit of claryfing how things work, form an interesting organisation. The time is now. I d love to explore, discuss needs and see how they alight, reading ‘who decides book’ from Sofa,
Nathalie: dont have so much, not much surplus energy atm to go through organisational change, recently thinking about growth, more ppl? what would be a good size? where do you want to go?
Vasilis: interesting to think about growth topic, start doing a map at some point, keep an archve on what we’ve chatted about, could also be table of needs/ people, resource that we gradually enrich and edit
Bruno: a map would be nice, the ecosystem we have, the resources, how do we see it for the future, if things start get bigger and more complicated, not worth getting into detail if we dont have things in place, basic ideas: general circle, general assembly, then we have the karrot team, development circle…
Nick: feel the risk of it becoming an abstract topic that is draining withough any outcome coming out of it, got a sense that sometimes we need more navigation, why do we come in the project in the first place? what drives us as individuals? other stuff might come from that? rather than starting from a map lets see inwards first? A weekly chat is a good idea. keep it as a standing point.
Nathalie: map/resource of topics, help me have a view on different topics, this map thing can go to a co-working as well, getting clarity: state the vision and aims, mission, unclarity for myself,
Vasilis: concern that needs from the current team have a narrow focus, combine it with map to have a bigger picture
Bruno: start drafting sth more concrete, motivations and also vision, can be more inspiring that is also related to motivation, obviously the needs and how that relates to the project and start connecting the bits of the project. I sense that we can get more concrete
Proposal:
use 20min of next meeting to start drafting
clearer take on our needs: why is everybody here?
ok!
commons consortium [R]
not go ahead with the proposal, requires an organisation that has managed millions of pounds/money, Ivan also motivated to connect regardless of the funding, there might be an ongoing conversation
I d expect sth more clear: hey everybody we are not doing it
nlnet funding [ED]
didnt do so much what they are asking, partly touches on the other topic, thiking about money and time: my new money focus life, starting from that 5-50 thousands of euro, last time was a bit stressful to meet the milestones, dif working pattern, idea i have now is approximately hourly rate, agree on doing some stuff, gives us double the time, also touches the money model. At least its sth to think about. Did calculations, say if ppl were working…38.000 for 3days a week for 3 months. 1,5 as a multiplier. wanted to play with the numbers. how is that thinking relates to you.
Bruno: how do we fit Karrot, its quite broad when u look at the list that can be quite broad speaking, data sovereigity…there are stuff to explore that can fit Karrot, we should sort of try and see what are priorities with funding are, and see if they can fit in the funding. should have the time to improve some basic things, usability in general, more friendly, more sleak experience. If the feeling is kind of shared with the rest of you but I m flexible and positive to try this out. Add the comment on the money/payment 1/week. Not get stuck in counting the exact hours. More doing an estimation of hours we contribute
Nathalie: positive about NLnet, could to apply in general, also think to make things more easier at the beginning about time comittment, better organise the pace, slow…to are we doing it? Also noticed my persnal time comittment is not that high, 3 days per week is a lot, last time doing the meeting, co-working 2+ max. Do know what is the capacity, focus on usability, idea to have a manual, do like videos, could imaninge having a spec project doing this manual, and focus on that
Vasilis: positive
Nick: coordinate the application process, noticed I have the most time and energy for doing that. What I heard from ppl: bruno 1 day a week, usability stuff is motivating, Nathalie: half a day
request from Daniel/ Luxembourg [ED]
- reach consent ? proposal from Nick: remove the user, record that decision as an agreement on Karrot group, do the process of jouining FSLux and share what we did with them, agreement to record a decision atm, change the period of time to 3 months instead of a year. It is a one time removal.
- Nathalie:happy to make this decsion, shall i ask if the followed their own process or its none of my business. Unsure of how happy I am for keepping the proopsal/agreement up for a year. Do this and see what happens.
- Bruno: in favor of the proposal, work on general proposal on how we deal with some cases, what happens if the person gets accepted again? another request comes? Discuss the general proposal…make it clearer.
- Vasilis: consent but be aware of not becoming judjes, deleting accounts
- Consent on above amended proposal!
- Next steps in coworking/ near future
who is in there? numbers? process? (e.g. who is listed on it)
adding tasks as attachment sounds good idea
some clarity of which tasks won’t fit that can be worked on now, so not too dependent on this to start working
maybe can copy/paste some parts from previous application, e.g. previous projects/organisations section
part to write a description of ourselves, wondering how to make sure we get the parts
important to fit in things we’d like to work on, not just a list of things we can work on, so look at personal motivation
last time on NLnet put all the milestones, really vague on money related to tasks, how you gonna use money incluiding rates, a bit tighter, i want that myself (Nick), that is sth I am consious, to work on get consent and explore
my sense to have it that ppl put tasks willing to be responsible for, there might be delays…put things ppl are wiling to work on and formulate themselves, was pushing tilman on that as well.
came up with the idea of handling the rate:
a rate we will be willing to work on that 15/20/25?
chargable rate x2, x1,5
decide how much allocate to the stuff
estimate tasks
we neeed to make a number
add ppl on the application
bump Nick over tax (nick) given we dont have a karrot bank. accoount
internal would what u get, other part is the karrot fund
round Q & R
Nathalie: a good starting point, about the rates, I m putting my internal rate >15euros, 20 - 25. Adress the bank account thing. Karrot bank account? → Legalizing topic.
Bruno: like the proposal of the two rates, also started thinking about needs about formalizing things a little more, self-employed or karrot-as-employer, exploring that a bit now, goes into organisational structure stuff, have to interact with bureaucracy, connected with bank/money stuff, etc. legal entities, … first reaction to tasks: “don’t think I can do much here”, seems more code related… but did see more design/community engagement stuff, hard to estimate things, will try to estimate average weekly contribution time, and sense of tasks, fine with rate idea, wish to end up receiving more than current amount, seems that this plan will go there
Vasilis: ok with the rates we suggested, don’t know about market rate, regarding bank accounts, if we do need it then need legal status, opens up new discussion, uk, elsewhere?, could also open up opportunities for other funding that needs legal status, so would like to work towards that direction, need to submit rate, do we need to budgeting? personal reaction: depends when/if we start, could spend sometimes like 2 days/week, depends on others capacity/motivations too, quite a few tasks to do, esp. research and engagement with communities, and can foresee collaboration with Nathalie/Bruno there, like to work with other people
Nick: relieved that ppl are ok ish with the money idea on rates, to have more foormalisedd structure there. we can get more real on what we need in our life. bring some of the needs up.
rate quite like to decided it today. it is asked for. make it concrete. Would propose 20 as internal rate.
3 rates: low rate 15,mid 20-25, high 30-40. Nathalie had similar thooughts, 21.50€ was the magic number,20 is quite a good number, make a proposal 20, 1.5x20 =30 for the application, 2/3 going to the person, 1/3 distributed Karrot fund
one thing that could be set up is an open collective account, maybe we could set up, there are some fees, maybe its worth it
we need to do budgeting, how to estimate hours on a task its hard, we just have to do the best on that
consent round?
rate of 20, 1.5x20 =30 for the application, 2/3 going to the person, 1/3 distributed Karrot fund
Nat: wonder if its in my tolerance rate? why not 22?
Bruno: consent, we could raise it a little bit, 21,5/22 or we just leave it as it is, at the end, you count with ur own rate, internal rating? calculate the total
Vas: +1 Bruno
Nick: would like the same for eveybody, maybe we havent got time to work the system, flat rate is a starting point of equality, start with the same rate this time. Re-make proposal 22,33 rate. Uncertainty on NLnet on market rates.
rate of 22€, 1.5x22 =33€ for the application, 2/3 going to the person, 1/3 distributed Karrot fund
Nat: Consent
Bruno: Consent
Vasilis: Consent
Nick: Consent
comment: stress that this is a self-employment rate
how to get the task list in shape, so people have things they feel comfortable with
Nathalie: looking at tasks and availability, won’t take on many, maybe one, happy for others to take on more, esp. coding ones, fine for imbalance of numbers within the team, if someone has motivation, great! coherent documentation one, could be nice, if it fits… could bring to co-working and get help to frame it, topics/pages/link to forums/videos, info about how the features work in details, have been thinking on this for a while, might be only thing to work on. also general feedback: really impressed by whole process, read through the tasks, sitting and nodding surprised by ActivityPub focus, didn’t see karrot in federated space before… not so into design things right now, e.g. the roles stuff. something to constantly work on would feel nice.
Bruno: leaves in anger
Vasilis: we mentioned the manual thing before, but didn’t include it, … fits with general themes
Nick: surfacing motivations and mush things in the framing, not bad if a milestne doesnt 100% fit in. On the documentation, I would support that, one thing i conceived of that. Coding and not coding way.
roles stuff?
Nathalie: feeling space for new things smaller, feels it takes energy, could be fine anyway, feels like a pre-existing idea, not sure how much we’ll shake this anyway, if others work on it, and there’s moments for feedback
Vas: roles very important, can see collaborating with bruno and nathalie
Nathalie: willingness to really listen to groups too small for this feature, have ideas but feels a stretch to work them in, can see listening to group needs would work, and maybe merge in
feels more able to be self-directed to do the documentation part
might re-think participation in roles stuff
what now, until submission?
Nathalie:
work on task list, assign people, time/money correlation, double check the names where people feel responsible and we need from those people
then writing the other parts of the application that Nick/Vas took on
CSX part, might talk more in co-working, less clear, bigger topics would be good to have more focus and time, but personally have less time and not wanting to expand it, will think more about it
Vasilis:
looking at application itself, abstract needs a couple of edits, but mostly OK
past engagements with similar projects, to support why we’re capable, needs the involvement of all of us, 2 lines per person (short tailor made CV)
explain what the budget would be for, would like support of someone else on that
significant technical challenges, also need support on
can take the lead on historic efforts, and engagement ecosystem
can engage on the 4 sections, and have good draft by end of co-working tomorrow
bigger question we didn’t discuss, how much money we ask for, needs some monetizing of the tasks, or the reverse way
have first good version by tomorrow? then maybe another co-working on Friday, or maybe even Thursday and Friday, can fix schedule to focus on that
Nick:
responsible for explaining budget
task/budget allocation in a spreadsheet
get a total amount
5 people to put on /
availabilities:
Tilman is in! → 10h/ week
Vas: 10-16h/week
Nick: 2-3 days/week
Nathalie 5h/week
another coworking end of this week, finish by fridy 7pm
Ashley, and I’m currently a college student looking to get more experience in web development
5/6/7 pm UTC would work
student from USA, maybe 2
could have an evening call
would like feedback on how we move on, as they are looking to hear back from us
reactions
Nathalie: wasn’t thinking so much initially as “college student” thing, but more in new contributor, onboarding frame of mind, like as we do with groups that want to use karrot, could see how connection goes, feel a bit obliged to reply and make call happen, could enjoy the call, framing is unclear now
Vasilis: wondering where they came across Karrot? remember it was in a list of projects somewhere, maybe there, definately don’t have energy for a call with student at the minute, great if you can take it on, maybe it’s for their dissertation or thing for uni, maybe have something quite specific so they can choose
Nick: unmotivated to put a lot of energy in, in the past: full of enthusiams at the beginning, a lot of help needed, becoming an (unpaid) coding tutor, when close to deadline: rush something that satisfies uni, not very useful to Karrot or the groups in the end, just trying to be clear about situation, maybe a better project that has more funding and that is part of their job to do funding, not a lot of time either, not very clear what they want. Find something they can work on themseves. Can’t think of any tasks at the moment. Probably the only person that could support them (technically)
want to support students
unclear exactly how to proceed
could bring to co-working
Nick offers to write definitive no
Next time:
money review: Review the amounts of how much money we receive [E]
Date: 2023-04-04 meet.jit.si/karrot
Facilitator: Bruno
Minutes:
Participants: Bruno, Nathalie, Nick
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 45 min
information: any (non-karrot) announcements? unavailabilities?
Nathalie will do less Karrot things for the coming 2 weeks, so not joining weekly meeting
next meeting:
next Wednesday co-working: Yes!
next Tuesday general: yes
pick facilitator for next week: you? your karrot needs you!: Nick
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
make a time poll for a feedback session [vas]
reply fosc e-mail [someone co-working]
continue to work on nlnet application [all]
4. Discussion points
new group in Bath [R]
transition bath group facilitated ‘eco’ meeting last year
one outcome was a whatsapp group → reached limitation
someone proposed Karrot
recommended from bioregion members
set up now!
like a ‘group of groups’
setting up another instance? bath.community maaaybee
comment: another group in Göteborg also lookig into Karrot
report nlnet funding [R]
it was fun!
Vas very committed
Vas and Nick went throught the final bits on saturday, send it away and celebrate
feeling optimistic
having a little break now after the sprint
thank you!
applied for 42.000€
money review: Review the amounts of how much money we receive [E]
Nathalie’s been receiving 400E/months and feel like committed contributor. But now feeling more like occasional since won’t have much time and will go down a bit: 150-200
Nick wants to crank it up! We’re in a state of transition between different models, waiting for funding, different personal needs, etc. There’s also the upcoming review of our whole money agreement. Without calculations feels like 400-500
Bruno, fine at this level, not had much time to reflect on how much time, past and future. trying to keep it at average level, not done so much in last couple of weeks, ups and downs. fine with current amount if others are fine too. 200. need for formalize evidence of income for state in the future, and would be useful to receive a higher amount, even if a 3/6 month period to receive a much higher amount.
also check-in with Vas next time and give chance to review
current balance: 16.154,98 EUR
standing point: organizational structure [E]
quick round no discussion
Nick: topic contained a lot in the funding. If we don’t get funding we can do a scaled down version.
Nathalie: CSX thing is quite big, but we could focus still on the question of what we do with the smaller group here, not necessarily connected to funding. What to do in relation to FOSC/SOFA (organisational learners?).
Bruno: agrees that things are related to funding, still nice to do something regardless, identifying needs, personal and project related, where do we need more clarity? where could we benefit from organisational clarity? e.g. what is the Karrot team, levels of contribution, relationship to establish with contributors, what are terms and condistions to contribute, not only money-wise, how do we decide on what to work on (features, bugs), involvement and engagement of Karrot users
not very clear about the governance structure of the group, nathalies proposal is clearer here, we want to know how they make decision, could refine wording about the position to make clearer how the group came to the decision and how they’re in a position to bring that to use
like the thing that they tried the feature at least once, although not completely sure, as maybe there could be a situation that it wouldn’t work for?
not very clear on the “database admins will act based on this agreement”, based on the karrot team agreement I guess…
typo on “the the Karrot” (the Karrot God?), I guess the Karrot Team
ask for clarification on what those two lines meant
on removed things, maybe these things were too detailed, and more of an internal thing, so good
Vas:
makes sense to not include the 3-or-more people, 3 is random number, if we did add a number a percentage might make more sense
added point about their governance agreement makes sense, prevent hijacking a group by new members contacting us
some groups don’t have a governance document though, so might need a bit of back and forth, and some small groups are flat informal organisations
judging vs trusting, on evidence… “ideally” is quite open, so allows for the scenario… for a group that doesn’t have clear governance, we would start having to judge the value of the word of an older member vs newer member, karrot team ends up the judge in these scenarios. maybe an extreme case.
makes sense to have tried the membership review once
database admins can seek advice or escalate… guess the idea someone can just do it if it’s super clear already, otherwise can go into a discussion with the karrot team
quite happy to proceed, makes sense
however, if we delete the 3-or-more people, one person could come up and make a request, would make sense more to be a percentage, e.g. 20% of members should agree, or provide list of their emails, or something… 20% is random number, but would make sense
Nick:
also like the show your gov agreement
happy with modification
tried the membership (I approve that)
get rid of the 3 ppl
get rid of the time period bit
one-time removal +1 keeps it simple
didnt fully comprehent the database admin
given the actual ppl who are database admin is ok but still it is ok to bring it up to the meeting with the Karrot team to understand what is the case with the membership review features
can we delete the whole last section?
i think shorter agreements are better
principles
what u do (requesting)
what we do
-would be ok to have a good enough for now agreement
-rework the words tomorrow in the meeting?
-put it for 1year
Bruno:
start thinking of scenarios, and in-practise cases…
and pondering wider thoughts for bigger platforms (BigTech platforms have shit moderation… comply with law, minimise cost, so AI and poorly paid people)
how much can we refain from judging role? always cases where the group can’t contain a situation, could escalate to board, or police, or other wider structures. not easy. and we cannot guarantee we cannot make judgements. even if judgement about the processes of the community.
just reflections, hopefully don’t have to deal with the extreme cases
up for a “safe enough for now…” and work as we progress
capacity and complexity at scale… how much can be assigned to the group themselves, 100s of 1000s of active groups? how does it look like in the context of community supported software compared to capitalist organisations, would be really innovative… nothing like that right now, moderating on that scale for non-capitalist orgs
Vas:
good comments from Bruno
any way to refain from having a judging role?
makes sense to do things at a human level, not having AI deciding anything
for 100s/1000s groups cannot do that model, … but maybe Karrot Team would be bigger
if we implemented roles feature and trust for role, maybe we have more “admin” roles that allow people to remove people directly, so they don’t need to ask us to mediate
e.g. current case was not asking us for advice, but asking us to do something they have already agreed without their group, more a technical request
leads us to discussion as we explore the CSX model
in luxembourg they have a conflict team and a wellbeing manager, but could not resolve situation, karrot membership review process doesn’t meet their needs so well, but neither did their community processes
Nick:
dreaming hat back on. wider society and technology? big tech exploited workers doing modertation from a ‘poor’ country for a rich country.
instance administrator in Mastodon, fediverse is currently undergoing a lot of growth and so active topic there…
making visible the invisble power of database admins esp for more informal projects
its not a desire to be judging, we could rework the revelant sentence though on the text
its hard to know what judgement is
standing topic: organizational structure [E]
quick round, no discussion
we’re all blank on this right now
from cybernetics, how much an org can cope with “variety” coming in
idea to have it as a standing topic to look at the board
how it relates to wider community and needs
sense to bring things forward when there is space available for development, rather than piling up everything
lots of things come up that are not in github issues or on the board
should we maybe not use Github issues at all? Bugs for example are not always clearly a bug, but maybe requires discussion, a new feature
working towards outcome/decision about how the flow can work at the moment, proposal for use of GitHub
ongoing planning for Göteborg trip [V]
Vas applied for 2 month studentship to Switzerland in June/July, visit some CSAs, then bring this knowledge/discussion into Karrot, and physical project, for ongoing exploration
in the meantime… plan to visit Göteborg and Luxembourg…
maybe potential to visit Bruno all together
open proposal for May, maybe a bit last minute
Vas could go to Göteberg anyway in May, and maybe another later trip
… waiting to hear about going to Switzerland or not
a round!
Nathalie: excited about this, could make something happen, would be nice to see each other, don’t have clear framing, could be more visiting Bruno, or super intense Karrot weekend, or in the middle? May is quite soon… but still waiting for Vas’s reply… [Vas: reply is due this week], not a massive trip, wondering about prices and travel, have some weekends in May… end of May but then middle of June, maybe July… fuzzy…
Bruno: happy to welcome everyone to Göteborg, getting to dates… would be good to plan it well, in May there are some days to align with that might be better, would be nice to have some Karrot time together, family visits… some visits to not align with… end of May, beginning of June… co-ordinate with summers/vacations… have to work out a place to stay, can check with friends, etc. potential for a nice little cottage house on an island (Orust) that a friend has…
Q: may? beginning/end? [Vas: avoiding end of May, lots of travel, greece, etc. may 10th-20th makes sense, could work well?]
Vas: may works regardless of switzerland plans
Nick: was going to say all of May is out, but a well planned trip could work mid-may centred around weekend of 20th (weekend before/after are busy)
another quick round of what next?
Bruno: not much to decide now, go through a bunch of filters to see if it’s happening in may:
a) switzerland trip for vas or not [LIES!!! he is up for mid-may regardless]
b) nicks availability
c) to see availabilities here
d) nathalies availabiltiies
open, but can’t decide anything right now
if not may, then later during summer? could open up other possible locations
Nick: my availbility is quite possible mid-may, if we decide very soon, and plan travel and money well, not sure if our momentum will get there, but if things are aligning, can organise solidly and quickly… will not fly
Vas: prioritise asking Bruno to see about asking mums and timeframes, e.g. 15-20 may, we don’t need to force Bruno to be with us all day, can then start checking how to get there, can do it regardless of Switzerland, checking newcastle to Göteborg, train/boat/etc, takes ages and expensive… go to dublin, then göteborg cheaper and faster… we can work out where to stay, so don’t burden Bruno with logistics
Nathalie: not available 13th/14th may, but would be after, thinking more about weekends, can think within week, need to think about how to work within that time, current plan is to have free days here and there rather than a bunch of it, reality coming back… travelling until 13th may, also beginning of June doing something… need a bit of time to let it sink in, and research, getting more realistic about distance and time, can see how it can happen, maybe stay alone in Sweden a bit, glimmer of an idea! would like to travel, not completely convinced
standing topic: organizational structure [E]
5. Actions/Outcomes
make/check a time poll for a feedback session [vas]
discuss reply to Darren during co-working [Nick/Vas]
progress hacktionlab CSX proposal during co-working [Nick/Vas]
minor: “Do that with the help of a board” clarify what the “board” is
clarify “standing point” each meeting, maybe too much to go through every week, maybe we don’t need a decision each time, maybe takes too much space in weekly meetings, as they are operational parts, so weekly meeting can be more focused on decisions, although if we’re in a routine it could be short, could try it… don’t have to fill it every time… we have 2 standing topics now
fine to try it
Nick:
also like it, short and straight forward
clarify which place to add new topic, backlog or new ‘incoming’ category
agrees on ‘Kanban board’
github issues still for purely technical topics ‘will be reserved for operational technical issues and usage will be minimised’
update document - more like a next step, not ongoing thing. Or say ‘keep documents updated’
likes standing point: could be short, check if something needs to go on the agenda, not going into every topic deeply, maybe clarify that more
big picture: how to prioritize? this proposal is already widening this decision. Next step: bring this more to the community?
Bruno:
appreciates improvements \o/
agree with reflections on the standing point, not to be a very time consuming thing, can decide whether we need to go deeper into it or not, and otherwise would be very brief, culture around the work and weekly meeting let’s us create how we manage it. if we do end up getting bogged down in discussion, could try only once a month
wondering about the correct space to make the decisions about what to prioritize, relates to do-ocracy aspects (the people who are doing decide what/how things get done), also relates to governance, still nice to have some of that if people have motivations to work on particular things. OTOH widening the decision making forum to the wider community would be good.
keeping this pragmatic right now, the karrot team is a good space for this deciding, as we incorporate feedback from groups
right now connection maybe not good enough for group members to get involved there
consent:
Nathalie: yes!
Nick: yes!
Bruno: yes!
we’ll put this as an agreement on the karrot team & feedback group, with a review period of 4 months
we decided not to wait to check with Vas, as it’s not a very dramatic proposal, and changes can be proposed in the future anyway…
organising the board can be done during co-working, tomorrow and in general
missing a “currently working on” column? (or use forum “assign” feature)
wondering how tags look, and assigned cards
extra columns could be nice, e.g. active design process, activate development
would be nice to write descriptions for “About the X category” topics
standing topic: organizational structure [E]
a round!
Bruno:
feels like the topic is progressing since making HacktionLab proposal
don’t have anything specific now
touched on it today slightly with the question on prioritizing the workflow
Nathalie:
update on Karrot & FOSC exploration, people filled out when2meet survey, date being sent out this week
John/Jane will take lead on preparing the meeting, faciliating and notetaking, nice Nathalie doesn’t have to do those bits
it should give a bit more input on this topic
was thinking, about the board… this dev-decides → team decides → maybe community. noticing changes in team and faciliating, and asking for consent. could reflect or formalize more. we still didn’t actually clarify what the “karrot team” is and who is in it… could formalize the team structure.
struggle with ideas on involving the community more, when we are less clear about the team itself. community involvement looks really unsure, whereas doing our team structure itself can move us forward, and look at community after that. get’s overwhelming and unsure how it would work, but do appreciate that
Nick:
work coordination, each person knows what they’re doing
political structure, doing things differently to corporate tech
going beyond rumour of group leaving, how to understand needs, and open discussion
round
Nathalie:
can relate, with sense of rumour, and semi-public information, feeling a bit unsure
conversation about translation of foodsharing in #foodsharing-dev, promoting to non-german groups
could start a conversation, could drop it, an open conversation could be nice
subgroups are useful, and more formal structures on foodsharing than Karrot
Bruno:
important to get feedback if groups do decide to leave
even if we can’t provide for the unmet needs of the group right now
nothing wrong being part of another chat
fine to bring it up, having seen information on #foodsharing-dev
Nick:
complexity of feelings is interesting, part personal, part organisational
feeling good about the way things are with foodsharing
freedom to use any tools
feelings of ‘taking away’ users (both ways Karrot ↔ foodsharing)
bring conversation up, esp. around Karrot for bigger groups
Nathalie:
would be happy to bring this to a conversation, personal vs group
like to just say things
interesting to share potentials
Bruno:
good to be straightforward and open
practical thing good to act on
emotional part can also relate to, that we all have, work and passion, feeling of people taking it away or not appreciating it, good to be aware of it, brave to talk openly about it
not be carried away with the emotions for the practical steps, a good opportunity for growing the project, developing the concept and organisation
not sure best place for the conversation, 1-on-1 can be fine, or can find a good more open channel, others can also participate there, would be curious, up to you
Nick:
happy with our conversation
reflections about how to make space for emotional topics within an organistion
do a round, put some thoughts, might take some more thinking and discussionn, nlnet funding application is pending, doesnt feel like taking about basic income
stay more in the reflection phase, what worked well? what not? another round of ideas? How effective was this policy what did we like? understand what worked and maybe go to what we would suggest to change?
facilitate a review sesh, best if someone is willing to facilitate. Make a simpler proposal: extend until to find what is going with NLnet
how do we feel about it so far?
Nick: good to have sth to distribute money, made a material difference to me, guess to other ppl, now few things feel towards a dif direction. 1. Nlnet funding that we received, 2. transition: structrure and organisations and how we go forward? Feels of energy deficit open more topics, lots of uncertainties
Nathalie: still like the money agreement, money circles went really well. high idealistic standard the intrinsic bit? One tention is how we deal with the funding? I dont see such a big gap, have kind of both.
Bruno: if we get the grant then we re-reflect on how we distribute money. It feels nice as it is now. Wondering if things will collide if we receive new/other form of funding?
Vas: first time experienced money agreement based on needs, nice aspect of connecting through this topic, nice that happened, amounts changed in the past, interested to talk about basic income idea, interested how ‘intrinsic motivation’ lands with people, extrinsic also a factor
engage in conversation about Karrot/ foodsharing software usage of groups [all]
write a repy to FOSC reflecting to what we discussed [Nick]
4. Discussion points
FOSC meeting yesterday [R]
who (outside Karrot)
rust and fosc exploratory talks in the past (Jane from FOSC)
has interesting insights
John interested in local foodsaving and probably some coding/dev backround
Ahmed doing agile coaching
topics:
governance within the Karrot team (who, how we organise)
sociocracy and gov for the groups/users (features, guiding principles for governance)
fed stucture betweeen karrot groups and karrot team
focus on the gov to the Karrot team tbw as sth more tangible to start with
not a regular meeting, check again in a month, formal and informal
q: membership topic? fluid – non-fluid (rigid, well defined). What needs os projects have in general? need for dif membership models? What does it mean? How the sociocratic model can fit in os projects? keypoint: the context of os projects, alllowing dif participation types
open source can be capitalist friendly and get enclosed
how to make governance ‘open?’
CS x bring sth outside of software
how to organise self-organisation? maybe sociocracy is the way
what is the Karrot role in that? What kind of governance do we want to code to the groups?
something for Karrot, or maybe for the foodsaving community using Karrot?
didnt dick deep yet
for urban doers
no need for legal status (we need to confirm that)
The deadline for submitting your application is 14 June 2023
ppl meet to exchange knowledge: networking and paper/report to produce
10 projects will be selected
clarify if we are eligible to apply?
Karrot day(s) 2023 [E]
a regular catchup, even sth simpler, a community cafe (vas)
maybe can start discussing the idea of meeting as a team, if we see that we can do Karrot days as part of that. We meet for a few days and try to organise sth online with other groups. We can make sth easy (couple of sessions). Would make sense to organise those things together (bruno)
thinking on a purely online setup, finding a date is always a tricky part, would enjoy bringing it to an op level, play with the roles cocept, have concerns coming up in every meeting, we can build on last year exp, not super excited to bring this forward atm (Nat)
first thought was a bit of overwhelm, hearing the motivation from other ppl, will go on for 1 d thing and manageable, online feels more manageble and discreet, question who wants to steward? I m up to support (Nick)
european level foodsharing stuff, maybe other groups interested?
leave it hanging for now…
Kranti feedback [E]
would be nice to understand the situation fully, maybe do a user story, and then do something about it. Not sure if a feature is needed
vas:
had a chat with Kranti before, and invited her to the group
refered to a feature they’d like if people didn’t show up to pickups, so they can know who it was and enforce a penalty
invited to group to share with all of us
they are organised in small committees, one that goes to supermarkets, someone wanted feedback after the activity to see who actually joined (so collect that as data alongside who had signed up)
bruno:
core of problem, agreed. how to deal with people that did sign up, but didn’t show up.
maybe not clear for her how to find the “activities missed” statistics
maybe still a confusion between signing up and not showing up, vs activity missed (nobody signed up) (as karrot doesn’t know magically what happened)
a lot relates to community governance topics, which karrot could facilitate more, but not fully
if we had penalties/sanctions might be good, pausing people, softer sanctions… less than the membership review. report system? who could do that? voting? lots? of? questions? roles?
we don’t currently understand the structure of their organisation, which people would be assigned to deal with those situations
once we know about how it works in their groups, can feed that into how we could develop features that support that
nathalie:
lot of good things said
good hints in brunos reply
agreed the software doesn’t have this information if somebody doesn’t attend
would advise to understand it further, maybe always have two people for a pickup, so somebody can catch the case
not clear how much the issue is occuring, wondering if they have that understanding too
maybe feedback feature to collect who showed up could be nice, but danger of finger pointing, and public judgement
in foodsharing there is 1-2 people responsible for a particular co-operation, and would be possible to write to those people to tell them
good to understand better the group dynamics, is it because it’s growing, or accountability is missing. wondering how to deal with on a group level.
nick:
clear thing is understanding hte situation better. Strucrture of the group, how it should work, what is going wrong and then explore that together.
Community-level wisdom, a small feature or bigger feature, go through the process of understanding
standing topic of org structures, there is no contract that Karrot-team and groups on the level of software
vas:
will engage in convo on karrot
share the idea of using the feedback?
like Nathalies point it can end up like a policing situation, public shaming…
big discussion (another one!!!), free-riding behaviour is accepted… non-reciprocal behaviours, not having fixed roles, etc… if it’s this loose thing, is it ok if you don’t show up?
bruno:
next step, should make it clear to kranti, we’re very interested in taking this seriously, and helping her out, as it helps us a project
we want to have a better understanding of which part is the community organising governance part, and which part is feature-building software part, and the intersection of them (interesting juicy bit)
how can we continue developing software that supports the kind of community organising that we want to see
could suggest a session with her to discuss, not clear how much it’s a pressing issue, have to guage from her reply
nathalie:
basically agree
would like to see us responding in a way that’s taken on, or taken seriously
seems vas has some motivation there
personally like the idea to bring it to a session, and would likely join, if somebody else is organising it
wonder where responsiblities lie, one person responsible to keep convo going?
how to make it more concrete (rooted? more env friendly)
nick:
agree with everyone
falling in the gaps of resp bit. We dont really have that. Pipeline an ‘issue’. I like the intention of feeling resp to support the group, dev of features, constraint of our resources
try and not jump into everything
accountability frameworks
vas:
interesting discussion to pick up at some point… wish and will to implement ideas from kranti, or help out… we’re making the container for some groups, are we providing a service? or have our own agenda? bruno said nice thing, “the communities we want to see, and they want to see as well”
participatory design is all nice, but do we also have standards we don’t want to cross
with funding can you provide better services, does it make you a service provider? how much can we be that provider? vs what we wanna do?
Daniel self-hosting interest [E]
interested in setting up an instance for their group, and use the karrot groups as subgroups
nick pointed to co-op cloud offered more help with hosting
our self hosting guide we did before, is anyone hosting one?
nick: I don’t know of anyone doing so
bruno:
don’t know anything else about situation
nice to offer support
very interesting if they could run one, and see what they do with it, seeing how they organise a big group
question comes up about inter-group interactions, relates to breaking-the-silo, doors-not-walls, but need more work to create more spaces for interactions beyond the groups
the solution (with a general group) could work
design question for groups
people in hylo have been into these topics, working with prosocial community
karrot can improve a lot there, creating more flexilbity and other spaces, people that don’t belong in groups, etc…
nathalie:
makes total sense, would be curious to see
would still be same software, not a fork
nick: I guess
reminds of discussion about how to run sociocratic organisation with karrot, see two ways:
“places” for circles (as don’t see who is in the place, favourites, not members), very transparent
other way is own instance and “groups” for circles, many groups, but features make more sense for group-as-circle, applications, defined membership, membership review… circle voting…
wonder how it would work with loads of karrot groups? how do you show how they relate… could have org diagram seperate
very closed though, as wouldn’t see what is going in, and a whole group just for a 4-5 person group seems overkill, not perfect
very interesting
nice to see his comittment to karrot
don’t know anything about foodsharing part of it
nick:
didnt interpret as going away from fs but exploring all options maybe
would assume both explorations (Karrot and fs) continue
offered to help with data migration
interesting what shared already regarding relations between groups (nested and real group)
hylo: had indiv groups now can have multiple parent and child groups. Sth like that would make sense. Can support dif ways of relating.
if they have their own instance they have acess/ownership of their data? But if they want to delete an account then they do not reach back to us but do that themselves…
50-70 people, they’ll choose apply then get selected, or not
can include in the application if you want to give a workshop
question for us is if we’re going
we had been talking about a workshop before, and this seems like a participate form, but maybe it’s all the same
collective filling it out? or us as individuals?
vas:
checking dates… gunna be in switzerland, so quite close by, works on personal level, not sure have capacity to organise a workshop, as in june we have the CSA thing with nick, then working…
for fun of it, like the idea of going
vas wants to hang out in the bar (presumably to party)
last day in switzerland should be 20th august, so a bit tight with dates…
bruno:
YOU’RE MUTED!!!
ooh august, hard for me to attend, work/family/kids, fri-sun
not sure about logistics just for a couple of days
unlikely, but not completely out of the question, would be fun
esp. if we want to do a karrot workshop, but not clear on that status, from our or their side, have to ask if they’d like us to something, and ask ourselves…
nick:
go where the energy flows, which seems that have dropped
try the meeting in person thing
would like to have the in person hanging out
we have difficult logistics and its ok to accept that
boat will be being built, partly present, party not a lot to do
in theory attending would work
could make sense to go to share about karrot, it seems it’s all about our topics
nathalie:
committed to go
50 people seems quite small, so exclusive, yearning for something bigger
would seem a nice end of foodsharing activities, as close to having nothing there, will be out by august
wonder who will be there that I know
aware of selection process
if nobody I want to meet, less motivated
generally motivated, and would be happy for karrot people to go
for workshops, maybe could offer sociocracy workshop
doing something for karrot would be nice, info point? show and tell? short presentation, could be quite unprepared…
“workshop” is more participatory thing
spontaneous show and tell, walk through software, show it’s there… half hour, half hour questions, good bye!
bruno:
saw on application form, they might have childcare! ah! could bring one… if we all go would feel more motivated, will investigate
really like to understand better how to support the “uncomfortableness” that Nathalie described. Would like to do something to resolve it
Bruno
didn’t realise until now that there is some uncomfortableness at not working all together, some background I don’t fully understand, and some personal aspects
one way people seek to resolve, is to separate things, where do we stand on a personal level, and an organizational level, how do we co-operate? can we separate? can we untangle or not?
thinking about own-experience in foodsaving community, so many personal things and conflicts come up when people are active in the project, how can we untangle or separate. maybe something that can be made better with clearer definitions, and boundaries. what is project and what is not.
not trying to advocate corporate mentality of HR, and only focus on work, ignoring personal, but to some degree, in general that has some truth
topic of personal situations and how they relate to a project
a movement to formalising things, when there is uncertainty or conflict, a move towards making things more explicit and more formal, have observed
not sure how to connect that back to karrot
interesting to continue talking about it
relates to some aspects of open source culture, where people might have little connection
Nathalie
intention wasn’t to look at the personal level, but how our organising can support us
Tilmann not only example of unclarity around membership
Nick
feels like not understanding what’s happening and how to navigate that, would need help
interesting reference (not that would like to have it on Karrot): 42/C4 | ZeroMQ RFC
topic needs more space, feels important
Bruno
can continue, is a standing topic
money amounts from June onwards [D]
how do we do this again?
balance EUR14224.98
Bruno: gets EUR 200 and would like to continue getting the same amount
Nick: 500 for one month. It was not clear when the new amount starts after we decide. Would like to continue. Karrot is main part of his life
Nathalie: EUR 200 for now. Could go down to EUR 150. Feels contribution is limited to meetings and co-working. Would like to eventually change to an hourly rate. Happy EUR 150
Vas: absent, probably partying, will probably keep getting the same amount EUR 230 to keep on partying. Keep it like that if he doesn’t object
relfection on decision-making process of the money amounts: would be nice to start with the explicit consent/objection
valid for 3 months, June, July, August payments. (payment itself is made on whatever schedule the person wants)
we need an accountant! Nick did April payment with the amount of the month before (paying it forward or backwards?)
for which month are we making the payment?
it would be good to have a note on Wise for the month
make/check a time poll for a feedback session [vas]
co-work on CSA/CSX [vas and nick]
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
share notes from FOSC meeting with Karrot team [Nathalie]
Date: 2023-06-06 meet.jit.si/karrot
Facilitator: Nick
Minutes: All
Participants: Nathalie, Vasilis, Nick, Bruno
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 10/11
information: any (non-karrot) announcements? unavailabilities?
next meeting:
next Wednesday co-working: Nick
[Nathalie] can someone reply to the emails? I won’t make it tomorrow
next Tuesday general: Nick
pick facilitator for next week: you? your karrot needs you!: maybe Vas
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
make/check a time poll for a feedback session [vas]
co-work on CSA/CSX [vas and nick]
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
share notes from FOSC meeting with Karrot team [Nathalie]
4. Discussion points
CSA talk [E]
vas has created a framework in which to discuss it, and grounds the topic, within platform capitalism, CSA, CSX, and commons peer-production
superficial/initial parallel between CSA → CSS (community supported software)
how to pin it down, make it simple, so we can initiate discussion
is one thing that’s discussed in current paper, not main focus
Nick has been thinking a lot about sustainability of open source as a model
some uncertainty how hybrid remote works
Nathalie’s contribution to Karrot [E]
two parts
recently linked an article about consent and membership in the karrot forum, Ted talking about leaving a circle is very unilateral, but could be a proposal, to think about the needs of the organisation (to see what responsibilities people have)
periodically thinking about leaving, putting karrot aside, for some time, or for good. have several projects, and deprioritize contributions to karrot, so karrot would be first to cut if something else came up
wondering how it’s going, not one reason, but some little things, things that feel uncertain, which makes it easier to let go
sociocracy stuff feels higher priority, looking for some other projects, and if taking another project then need to free up time
history of karrot and personal connection influencing present, which echoes into the present, wondering why it bothers
need to be independent, and a sense of entanglement, and uncertain belonging, moving away from foodsharing somewhat, and still some ties there
wondering about the flow of work and the type of tasks, not so wanting to relive the structural topics, inside the team in karrot being the one looking for more structure, but not so much wanting to think about all these topics in karrot, feels heavier than in other spaces looking from the outside
did enjoy the nlnet flow, designing features, and wondered about getting more into software and maybe coding things. is this the right space for that though, thinking about who is investing time. looking for something where more people are contributing more work, with a bigger team. more focused projects.
could grow time, but question of money, would we all grow our time, not clear. wonder if it’s a tension for Nick too, if he would do more time. don’t feel like stepping up do participate more in karrot, and the topics to engage with are too big to manage with a small time
calls and co-working have a nice atmosphere, so feels nice, so still thinking. karrot days were nice, meeting in august would be nice.
wondering a bit more when off screen
unresolved tension plays some part, although not the main thing
thinking how long I would stay, what would be the process of leaving, or whether something would change. hear the efforts to find comfortable, but without feeling a future there, maybe not fair to accept process to find a place
interested to hear comments and reactions, and hoping for some clarity after hearing us
Vasilis:
two levels, emotional level and practical level
feel sad thinking about Nathalie leaving the project, as it’s worked super nice, really trust her, the energy she brought shifted karrot in a different direction that is more promising than it was before, was chatting with people in the house and the way we run the meetings and the structure she introduced led to more effective meetings, have learned a lot from her perspective, a lot of things brought to the discussions, e.g. discussions around the organic structures, which are embedded in capitalism, etc… blah
emotionally would find ways to motivate her to stay in project as a friend
on the practical level, we do suffer from not enough contributors, so would be an issue, can see sometimes she might feel lost, and uncertain of own contribution, although clearer with phd to work on
seasonal karrot thing, so maybe going through a summer, seasons change, e.g. with nlnet, karrot is still quite foodsaving centric, but heard potential interest in her about engaging in other contexts
Nick:
appreciate sharing it, when leaving a circle having a process around it, pll leaving karrot thorugh the years and almost faded away, dissaperead,slow divorce, appreciate the intentioanlity to make it clearer,
reflecting on relationship therapy stuff, when sb is ready to leave and bring up all the topics to motivate and make things appeall to stay
noticed for sometime what ur contribution could be, find the pathway for ur contribution, wouldl be happy to support this process
sadness of the autumn tries as the winter sets in, seasonal things is sth that I embrace, natural cycles not lines
my main thing woud be doing higher priority than the project’s itself
it is dif for Karrot to meet a more solid infrastructure/stucture of a well-flowing team, in reality Karrot atm is not that, it is frindge/exprimental, it was even more in the past, efforts to bring it in the current economy but this is really hard, if Karrot to be my only financial source I dont think this will happen, but Karrot keeps going, Karrots severly underesourced still makes this project vs other well funded pilots that die off quickly
I d prefer if it was most stable, would like it to bring in enough money, or have enough stuff done and have a more stable team, that is uncertain though, wonder a lot if it is needed as a piece of software, what groups would do? smooth transition? thinking more of the value we offer…same dillemas probs to which we have been encountering
Bruno:
(has kid on lap, and distractions around)
discussion brings up a lot of thoughts
wondering what things I enjoy, and don’t enjoy, or don’t meet my needs, etc. what keeps me going
regarding Nathalies exploration, thinking about leaving, agree with what’s being said, really sad, want to try and understand the reasons, kind of clear to me, but not fully
tend to try and say, nono stay! but at the end up to you, like that open up the possiblity of exploring, to actually see if there is something deeply embedded in karrot culture that doesn’t fit, or maybe we can do something about it
maybe two things, needs-related, financial aspect etc. but also think about it in terms of enjoyment, which things have been enjoyable, maybe they’re missing now, or still there? how to bring some more focus on those aspects, more intentional
karrot comes in waves, the enjoyment. sometimes can be really enthusiastic, like to put time on it. sometimes don’t have much time, going with the flow, without head in it so much, so stay in hiberation, come to meetings but not much more. could also take a pause from it and return at a later point.
we’re at quite unfocused moment for karrot now, maybe we have a need/urge to focus to go into a new period (of seasonability), which might come with more structure in the work we do, sometimes wondering what to do, what are we focusing on
if we got another financing from nlnet it would bring us more structure, even if it doesn’t happen would be nice to bring more structure and intentionality, defining how much time we’d like to dedicate, set some self-goals, and find how to work to achieve it
personally, always have the tension of unstructured and structured way, being very adapable and flexible to life, so can take a step back when I need it, and dive deep when I feel like it, being mindful of others and what they expect of me, like that
usually struggle with the tension, as it’s a bit unclear and have to pose the question, which space are people in
nice to have discussion now, an opportunity to try and sync that, esp. as Nathalie is feeling out of sync, is there a way to sync it so it would work, maybe others would move into another season of the project, on the long term though perhaps it’s not suitable on the longer term, unstructure/unstructure, sync/de-sync is not always suitable for many people during certain times, or personalities, which is proabably why many people would not join Karrot
as a conclusion, really appreciate that you bring it up, before leaving, like to believe there is some chance to maybe make it work, can also accept if it doesn’t work for you, like to see it as something to explore, is it something we cannot really provide, it’s a nice conscious choice to go onto other stuff, maybe it’s something we could provide, and maybe can find sources of enjoyment still to continue, and find enthusiasm again to be able to dedicate time to it
like to talk openly about it
Nathalie:
thank you everyone for taking the time, and in depth answers
after finishing, and the round started, feeling sadness, then conversation shifted, feel less sad again, more in a constructive space, which is nice
two things stood out
emotional side is a big one, how karrot is embedded in different connections and people, and what are my connections with those, so one way would be try and take the emotional side out, could be a break? topic is a lot from an emotional side in this project in particular
karrot is not quite a solid infrastructure, and how life is flowing right now struggling with some solidness, and being in a project without that, is difficult, so if rest of life was more solid might be different
some constructive thoughts, leaving, or less governance meetings, or less involved in the bigger discussions, having a more concrete role in specific things, e.g. only at co-working, advertising more support of the software, so not being in the general circle, something more specific, abstract vs concrete topics
would like to take the conversation and let it ripen/sit a bit
find to close the topic for now, and happy to continue, still around for now, wouldn’t increase contribution though
Vasilis:
one thing to add, Nick said karrot is project in fringes, very true, don’t have to be delusional, unless we’re lucky or take steps it’ll stay there, but it’s on our hands to try and make it work somehow, to become more stable and create this more rigid/solid/stable infrastructure, won’t go into more now
Nick:
put visioning in a seperate thing to co-working, genereal and make a more clear vision strategy e
Bruno:
we’re creating this together, feels like there is quite some room for changing/adapating/improving, happy you’re stickinng around for a while at least top tip: find the sources of joy and focus on that
unclear how the karrot project interacts with this festival, initially we had the workshop idea, but not talked about so much now
workshop offer was listed there, a sociocracy thing for foodsaving groups, so Nathalie agreed to giving a sociocracy workshop
there is a bit of a division in the registration process between presenters and participants, they pay and can cover some travel costs
seems nice to go there, has been on mind for a while
maybe worth talking to Daniel again about workshop space, not clear how full they are, there is an “open space” still
seems in karrot it switched from giving a workshop to just coming, wouldn’t push for giving a karrot presentation outside the open space
registration is open until june 15th so register now
Vasilis:
came across some posters about it, checked on the map, will be 3h on a train away unless something bad happens will try and be there, Nathalie being there makes it more motivating
regards to doing something with karrot team, today would say don’t have energy for it now, but might eventually come, but can’t take the lead, would be happy to go there and meet with people, have a chat, and have a nice weekend (if it is a weekend
Nick:
Was more motivated when I checked the buses, a bit of a long journey but not too crazy, need to make a decision before that time, right in the boat building time, good or bad, sort of inclided to plan it in and book it, as participant, could imagine try and make and informal info point, show ppl Karrot, print out a thing, dunno if that would fit in. And then closer to the time I can bail but if booked already more secure, travel costs, 30 euros attend, use some Karrot money to do that?
Bruno:
yes, was looking at buses and bus fares, and ways to do it, feel like if realistic, quite unlikely to be able to make it, but could be quite a fun trip if could take frans with me, I think it said they had some child care, will continue to investigate to see if it’s feasible
regarding karrot’s participation, should definately do something there if anyone is going, just to present and say we exist, can be useful to a lot of groups, would be a shame to lose this opportunity
Nathalie:
quite highly funded thing, so doesn’t have moneyfree vibe from early yunity days, they do say they have solidarity participation in the travel costs, strategy would be to try and apply for receiving that, as it says they can provide for travel costs
ok using karrot money, costs shouldn’t come from peoples personal accounts
things miss the context, e.g. “start membership review process”, hard to understand context and translate well
could we have auto translation? and a native speaker can edit it?
Bruno:
also struggled with lack of context, even being familiar with karrot
not clear where the particular string is placed
ideal scenario would be to have a screenshot
Vasilis:
doing greek, did 500 lines, then had a call with Bruno, to give help with tool, and that was very helpful
maybe a manual, and video tutorial, could help
Nathalie:
from feedback, did look at it, have a question, do I just add the translation then it’s done, or does it need approval? or if you see something in the software, how to find out where it is to improve it? what standard are we aiming for? not super trained in translations, feels like fine with “good enough”
general sense is if we want to engage with it and bring languages to a higher percentage, it would need someone, or a team to take care of it, something good to know, could be a nice task
Bruno:
if people contact us, or there is an issue, should give them support, would be up for helping out, have a walk through, or figuring out a context for the translations, would be a good start for people that want to translate
no review process currently, transifex has some features for reviewing, currently you can just type anything and at some point it would get live
would be nice to have, German, Swedish, … clearer defined sense of ownership, team/circle/etc.
German is only at 85%, and we don’t have professionals, so feel free to step up
translation for brazilian portgugues has lots of weird things, so would like to update it if there is time
Nick:
lot of tech stuff on how it works, share more in operational detail, two types of translators: karrot users and random internet ppl and they dont know anything about it, esperanto 100%, feautures to talk with translators, familiarising with the tool would be useful
make/check a time poll for a feedback session [vas] (8) ← increment each time it gets moved down
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
Date: 2023-06-13 meet.jit.si/karrot
Facilitator:
Minutes: All
Participants: Nick, Bruno
1. Opening
10 min Check in
5 min ADMIN
attendance (write down participants)
duration: 45mins from now
information: any (non-karrot) announcements? unavailabilities?
next meeting:
next Wednesday co-working: Nick, Vas, Bruno
next Tuesday general:
pick facilitator for next week: you? your karrot needs you!:
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
make/check a time poll for a feedback session [vas] (8) ← increment each time it gets moved down
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
send over basis for CSA talk [Vas]
4. Discussion points
vite-based karrot frontend [R/E]
showed how it’s faster to yarn dev, slower to load initial page, faster to see changes
would be nice if other people that do code could try it out to see how it feels, before I commit to fully integrating it
would need a bunch more work to switch, tests, production, etc…
Bruno will try it out, maybe in co-working tomorrow, with instructions on how to do so
funding, now that we didn’t get nlnet [E]
boo
a million reasons why it could have been, we asked for some feedback, guess they are overloaded
how to we move forward?
Bruno:
beg for money
short term, keep looking for funding
longer term, building up some kind of CSX model, community-supported
Nick:
same, but not motivated to do another application
disrupt.org? it’d be worth writing an e-mail, through outlandish (sent!)
find rich ppl to give us some money, existing connections, random
next Wednesday co-working: Vasilis, Bruno, Nathalie
next Tuesday general: yes
Nathalie on vacation July 4
pick facilitator for next week: Vasilis
2. Consent to agenda
2 min
3. Review last week’s Actions/Outcomes
make/check a time poll for a feedback session [vas] (10) ← increment each time it gets moved down
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
post to read databse change proposal again [Nathalie]
add to feedback log thing what daniel said:
An export feature containing at least all the places’ details would be nice so that these data could be exported manually from time to time as a backup.
sofa and opensociocracy? sofa fosc circle connected to opensociocracy, not clear where that connection goes
fascinating how ideas can be separated by the social practise of them, big factor in reality is actual connections, we try and separated things, but personal connection important, need solid social connections
vision, strategy, new funding model, open collective, etc… [E]
funding fatigue, money from users/groups makes sense
should tie it into strategy
assume people are into that, but let’s check!
vibe has been waiting for funding…
clearer need for nick to make it financially viable, and for projects
nathalie also expressed need for more structured work
sense that we need a sense of direction from here, together
establishing pace of work and dedication
personally (bruno), would be nice to have another wave upwards, was hoping for it with nlnet application, but maybe not nercessary… depends on ability of people to dedicate time, and what funding means for that
strategy! would like to get things done now, a lot of potentials for fixing, maybe some new features, would need a funding model, would like to support others who need money, esp. nick, probably others too
could set a goal… e.g. do the opencollective thing, investigate more funding, work out different scenarios with or without funding…
happy to find more focus, and be supportive, although personally haven’t had so much karrot time lately
need to see if we align
Nick:
form the strategy, get clear on the money needs
what should work on next after the attachments? figure that out connected to a strategy
how do we make the strategy more tangible, in our practices. An agreement doc on Karrot? anyone motivated to work on it?
Vas:
key point is need to come up with a strategy, and test a model that’ll be sustainable for karrot, financially and ethically
funding fatigue experienced throughout life personally, not long term sustainable
have been thoughts in detail, but not the right time for that
on the same page as who is funding? in favour of it being funded by those directly using karrot
question remains how to do it, so far majority of groups don’t have other funding, so tricky there
Nathalie:
also like the idea of being funded by the users
although there are state funding schemes, can feel unfair to ask the people who work to get money to spend their money to spend other things, gets wierd thinking where money comes from… when there is big money pools somewhere
applying for funding that easy and puts us in a certain box
funded by the people!
interested in opencollective, still have open question about this “collective” term
one thing they solve is not having a legal entity, so they have fiscal hosts
to truly be a collective, what about our domain, who owns things, would be nice to have a collective solution for this, e.g. contact form for site, data privacy, etc. legalising karrot topic… how much does a fiscal host help? or would we need other legal forms?
commons theory is something that fits well with the group, and with karrot, would like to see a direction more clearly speak of it, karrot has had the food focus, then defoodification, but no clear focus to replace it, maybe commons is that focus… to be clearer who we are targetting… as maybe de-foodifcation lost the focus
Bruno:
financial models, totally in favour of long term finance by the people, doesn’t need to be users only
how do we make that viable long term, have to have time frames in mind, can’t achieve financial sustainability if we just go out to the groups now saying “we need money”, could be lucky, but not so much money willingness available already with this approach, would need a different scale to find those resources, maybe more groups, more people, bigger outreach, … becoming more commons-based project
still space for funding, esp. short/mid term, but not try to lose the vision of “we don’t need those fucking funding applications”, we can do this by ourselves! independently, collectively, democratically…
pragmatic approach, how can we make that happen
could jot things down on a document, maybe for next co-working? could do it together? during co-working or meeting? another pad, 5-10 minutes to write something down, separately? then bring together at the end… doesn’t need to take a lot of time, workshop format… half an hour… as quite aligned already in thoughts and values
could do something tomorrow?
also supporting idea of rethinking how we profile ourselves, “what is it for” now, had this general thing of “community organising”, if we connect more into theory and vocabulary, could go deeper into it, broaden our connections too, needs some investigating
Nick:
also felt we got lost after de-foodification, more towards commons
how much do the groups identify with commons?
funding by the people does not mean users only, also random people on the internet donating a couple of EUR/month would meet our needs because we have low costs
thing in August, a good place to start thinking together about strategy
also likes the idea of working on a document but not much time
Vas:
how much do the groups identify with the commons… we should investigate, so we don’t make something super exclusive, we already saw how some features on karrot don’t really fit the needs of the groups
not saying we shouldn’t pitch it towards commons, but is a spectrum, have to understand groups already use karrot for some specific tasks only, so not all encompassing project for them to everything within
if we position karrot within commons, we think of 3 basis, resources, rules, and community, and start building it in that direction, now, it does seem very much that
funding model, wasn’t thinking it could be other outside people, could be interesting, could also be organisations talking about commons, peer-to-peer advocating about technology, some of them are sustainable organisations, how about going door to door, you chat, we build we don’t have money, you have it. how about donate, £50/month? groups, users, random people, institutions, research groups. SPONSORS!!!
up tomorrow in co-working to start writing some things down, then come back and check and discuss
even within food waste stuff, a lot of orgs chatting about food waste policy and role of technologies, have to examine what a sponsor, can be a patron, can lose agency… who are we accountable to
hybrid/flexible model, maybe not so easy now going to small groups telling them we need money, some of them might be yes, reward it, but maybe cannot, can write this stuff on a paper
not super novel, but talk about being mission driven and flexible rate, maybe free
thinking about process, would be good to gain feedback before making the final decision, in a structured way, could work on something, have a draft agreement, and we’d like to get money and how much would feel sustainable, agree expenses are not extremely high, so could work, wondering whether to address individuals or groups, thought to address groups first, and individuals could be additional, draft, numbers, calculations, and feedback channel
if there is money involved, and we say it’s still possible to use it without money, would it feel it’s not really for free, need a good frame to make clear they are really welcome to use it without contributing, but they can…
so, gather feedback and see if it feels like it’s a huge change, and feel stressed about it, … so to avoid it being a Big Announcement
follow up with recent feedback (Kranti, Daniel)
call poll fatigue
maybe one person just schedule something, and announce it for others, to avoid poll cycle
bruno up to do it
big groups is the thing
tech update [R]
attachments → review \o/
vite… ongoing
hanging application in karrot team
was hanging about for 2 months
declined without message
make/check a time poll for a feedback session [vas]
surprised by ActivityPub focus, didn’t see karrot in federated space before… not so into design things right now, e.g. the roles stuff. something to constantly work on would feel nice.
I guess you could almost say that
