Date: 2022-08-09 12:00 (UTC+2)
Where: Jitsi Meet
Facilitator: Nick
Minutes:
Participants: Nathalie, Nick, Bruno, Vasilis
1. Opening
- 10 min Check in
-
5 min ADMIN
- attendance
- duration: check-in after 1h, 2h max
- minutes: last time minutes - anything needs attention?
- information: any announcements?
- Vasilis got a flat tire
- next meeting:
- design meeting this evening (8pm central europe)
- co-working tomorrow as usual
- pick facilitator for next week*: (* a few meetings ago we decided to try and do this in the opening section)
- Nathalie
2. Consent to agenda
- 2 min
3. Review last weeks Actions/Outcomes
- 5 min
- contact Kranti about specific issue, with mind for it becoming ongoing “helpdesk”/cafe form? [Nick]
- schedule work on “Guide for participants on how to contribute (for potential contributors)” to co-working session on the 10th of August, send reminder [Bruno]
- email Jos [Nick]
- see about handing over co-op cloud self hosting task? [Nick]
4. Discussion points
- debrief server failure [R]
- Sorry for the Karrot outage today (2022-08-06) 😭
- one disk was broken but we don’t know for how long, Tilmann found out when he tried to reboot
- took some time to find that out after it could not boot
- a lot of organisational legacy stuff, back from Foodsharing days
- got assistance from the provider Manitu and they were really nice in their support
- there will probably be some costs (support + disk replacement?)
- good to have at some point in the future our own server
- Nick and Tilmann had to juggle a bit with their own plans, but it felt like a nice team work
- it was a nice opportunity to make it human and not (work/service-like) professional to Karrot users
- stressful situation, especially when it’s still not diagnosed
- brings up the question of responsibility and vulnerability: if Tilmann and Nick were completely unavailable, would other people step up to fix it?
- could other people in the team have been more supportive?
- since it’s a very technical issue, not much in this sense, but not making it very serious and stressful helped
- could we set up some kind of emergency routine?
- update prototype testing [R]
- testing with Daniel from Luxembourg yesterday
- good insight, with ideas to fix some things
- location: at the moment we create activities as part of a place, that may or may not have a location, and might be nice to be able to set a location directly for an activity
- suggestion is that the email address should be verified (for signing up)
- discussion around the chat, when could you join the chat? verify email? join chat before signing up?
- if you want to ask a bit more about it, how would that work?
- public activities being visible during the application process
- e.g. introduction meetings to support onboarding processes
- might be a view on the group preview page to see the public activities
- some would be nicer to have as private links, rather than listed on the group preview page
- might be able to facilitate better intergroup exchange, e.g. can click on another group and see what they’re up to
- … and some notes to evaluate further
- prototype itself had some more superficial issues, but didn’t affect the idea itself
- testing with Dave tonight
- do 1 or 2 more, but not a lot, and have it done
- also had an idea to test with non-karrot users
- for the milestone?
- going through notes and memories for this breaking the silo design process, and write a short friendly text/summary, and put on the blog…
- nice continuing evolution of design process, with penpot tool, etc… hopefully can empower more people to lead these processes to evolve new ideas within karrot
- money flow [R]
- just making sure we did it all
- end of august plan another money circle
- look at who is receiving money and how much, and how people felt, check balance, new people, new wishes?
- 1st november, review the whole agreement
- broader review on the whole system
- Money distribution in Karrot
- activities updated on karrot
- deadline (or other) stress [RE]
- including nlnet stuff
- nick: little pa"nick"! state (Nick) the amount of stuff and duration (1st of Oct) feel overwhelmed, ‘life struggles’ as well, resynchornize my brain with the state of reality
- nat: totally relate, wasnt part of this agreement, I feel like extra (a bit), limited to the non-tech things, its good if some money come in but I m not super dependent on it, reconsider our relation with the funding
- vas: also part of phd research, get pressure from supervisors to write, end of sept to write something for a conference, want to prioritise nlnet milestones, important the milestones are done to some extent, contributing to more than karrot, but personal lives of contributors, milestones signed up to are doable
- bruno: thought a little already, felt a little pressure, really need to be more disciplined and mange time better, hopefully will manage to do them all, ambiguous feeling, a bit more stress, don’t like deadlines, but also a little pressure can be good, sometimes people perform better under pressure, giving structure/motivation, gives him a little more focus, trying to get balance, can relate to nicks feelings, reflections on sense of obligations, nlnet maybe used to projects like ours, if we have good communication should be no problem, are the obligation feelings about seeking validation from figures of authority? also pressure from financial aspects?
- nathalie: nice to have a goal, giving some structure, low motivation so good parts of pressure, ideal would be if something is only for the money, not wanting that, but clashes with reality… leads to having no money. maybe we should say no to something in the milestones… not end up with a big crush in last week of september
- vas: agree with nathalie, if we can decide in the next days that something isn’t happening, can remove some pressure? reflecting on relationships with funding institution, doesn’t currently feel like pressure from them, liked the approach to not be accountable to external orgs, but to the community (which would be totally different funding concept, e.g. crowdfunding), real-life is maybe a combination… was still good move to apply to it
- bruno: I agree… continuous evaluation of what we’re going to make or scrap, do what we can do maybe crowdfunding future is good…
- nathalie: in context of karrot days, was it a distraction from the milestones?
- update on data layer stuff [R]
- made a mega checklist on the PR
- GitHub issues
- housekeeping stuff
- some have been marked as stale, would like to check with others if they are really relevant
- would be nice to have a clearer understanding of how to manage the issues and how to assess their relevance
- maybe on another occasion, meeting, or co-working could evaluate them
- we used to have roadmap meetings to organise them
- last time was a while back https://github.com/karrot-dev/karrot-frontend/blob/master/ROADMAP.md
- maybe we can make some more specific tasks about how to go through the list
- could be postponed until after nlnet deadline, maybe a good time to reflect how to do our own milestones
5. Actions/Outcomes
- evaluate milestones in two weeks [all]
- contact Kranti about specific issue, with mind for it becoming ongoing “helpdesk”/cafe form? [Nick]
- email Jos [Nick]
- see about handing over co-op cloud self hosting task? [Nick]
6. Closing Ceremony
-
10 min
-
checkout
vasilis will join on wednesday still
New and refined features on Karrot just out of the oven! 
]
