goal is to make decisions together that support everyones needs
took learnings from NVC (Non Violent Communication) - going to needs level
from a thought â but something underlying that speaks to a need
have a proposal, and people have concerns, but go to underlying needs, and make statements about the underlying need
then get creative to see how we integrate this need
speak a lot about âconsiderationsâ, concern â consideration
prominent learning, when go to needs level, relatable needs, can get more shared and solved
avoiding to get stuck on the positions/ideological perspectives, where you can get into fights
one takeaway: not much about convergence/divergence⌠we actually diverged a lot, at the end had to work out where we go⌠takeaway was to allow the divergence if thatâs where itâs going, letting it flow a bit
nick:
miki kashtan, lot of work in NVC field
overwhelmed with terminology
we need these types of processes
personally was a bit overwhelmed: what are the necessary pre-conditions?
having a trusted group with a shared intention
got a bit long discussion in the session
even if it goes very broad, facilitator can help with story telling and framing âthis is really an important topicâ, âthis is a good basis for our next stepsâ
process and digital tools?, easily gets technocratic, point people to processes and websites, could use pad and videocall
Nathalie:
not super clear thoughts, did I enjoy it or not?
expected a bit more theory input, very practise oriented
lots of things have heard in other places
quite a complex case to facilitate (the example in the workshop with 20 people)
was also thinking about how to guide workshops, enjoyed the openness and practise space
but wasnât so clear it would be practise space more, maybe could have used it more for that, didnât speak and wonder why
big group vs small group, sociocracy encourages small groups and trust building
but here said you can do it with 80 or 300, as needs donât scale up with people (as needs are shared/common)
different levels of thinking/decision making
can see how this technique could work with larger groups
personally, did notice nicks stress, attention was split, having the call and the pad (nick and nathalie wrote notes in a shared pad)
interesting how digital can support process⌠in the end itâs about people talking and making connections, what degree can software provide it?
Nick
strong facilitation, key role and shape the session, make decisions how to proceed
make decision without any discussion possible, e.g. check for objections/ concerns
being reminded of other times, example didnât feel relatable
jay
sounds like an interesting session!
nlnet timeline extension?
made a coworking item!
Next:
opencollective (linking opencollective and karrot instance) [vas]
5. Actions and Outcomes
rework from scratch agreement related to data interventions [vas]
write follow up about CSS on forum post [Nathalie]
sit down and think what to do after Bristol personally [Nathalie]
forum post on Bristol days - ongoing [vas]
start working on guidance document for âperformance reviewsâ [Nathalie, Vas]
more money admin: do tranfer and check expenses [Nick]
transfer money to karrot [Jay]
pad release party [Nathalie]
nick email eszter and nathalie [Nick]
get our head around nlnet tasks [coworking]
continue working on getting polls ready to merge [Nick]
rework from scratch agreement related to data interventions [vas]
write follow up about CSS on forum post [Nathalie]
sit down and think what to do after Bristol personally [Nathalie]
forum post on Bristol days - ongoing [vas]
start working on guidance document for âperformance reviewsâ [Nathalie, Vas]
more money admin: do tranfer and check expenses [Nick]
done!
transfer money to karrot [Jay]
pad release party planning [Nathalie]
nick email eszter and nathalie [Nick]
yes!
get our head around nlnet tasks [coworking]
we did it! but nick didnât email nlnet yet
continue working on getting polls ready to merge [Nick]
yes, progress! but still more, see updates
4. Discussion Points
updates
outage on sunday, Tilmann saved us
because of an automatic update on Redis. A restart on Karrot made it work again. Nick thinks about a way to solve it and make it more resilient, but not implementing that now
email issue
ongoing, still needs more investigation
polls
some details left to figure out
close to a merge!
update from last coworking
frontend and backend running now for Jay!
step by step approach
schedule next (design) session to focus on roles and permissions
Needs a topic and an artifact. Possible topic: prefiguration (prefigurative technology), maybe in connection to CSS. Possible artifact: Karrot
Butze, Leoni and Vas (if he wants) and whomever of us would like to be, ask Matt
Workshop will be hybrid
CHI will be in Yokohama, Japan at the end of April
Bruno: courios, will see if he has time to read and contribute.
Natalie: what does Philip need from us in this meeting? what will the workshop look like? Interested in the topic
Butze: get feedback, let you know and ask if Karrot can be the artifact
maybe not something we need to decide on, but anyhow all are fine with it.
a short discussion about double roles and keep this discussion for the future
Nick: lot of richness in the ambiguity about the roles of academia and activism. - Karrot in post-growth theme fits well. - curiosity at the sidelines. - if there is a session we can watch online.
Butze will draft something tomorrow at the co-working
money admin
updated amounts after lates money flow (see Karrot)
all clear, Nick approved Nathalieâs expense
share the responsibility so itâs not being a burden on the person thinking of it the most
not feelinglike a burden for now
question about Nick transfering from personal account
he did not look into it.
unsure about money situation in the near future when Nlnet money is over
reflection about OCâs design with the boxes showing what they think we should see, but not really interesting/relevant to us
Philip worked on this last co-working, seems good enough to make a workshop out of this
âprogressive interfaceâ wording, âDesign for Incremental Appropriation (DIA)â as another suggestion
politcal meaning of âprogressiveâ
Reactions
likes DIA wording, broader context, not just the interface, appropriate technologies is a topic too, for us itâs about the interface, but could be seen broader
Philip as first author, Karrot team as a whole mentioned? or naming affiliation
terminology within a context, progressive enhancement in software (html, js), what is the context of the audience? would our karrot groups understand DIA
if itâs something academic and thatâs the context, the term seems fine
meaningful and promising, also came up in conversation with Bountiful Bristol, guiding a group, how to build a group, develop a resource library, talk to people
progressive and music comes to my mind
how to make most out of it? Philip to continue working on this and getting feedback
not yet being practised but discussed, interface in a metaphoric sense
creating karrot together, how we produce software, getting engaged with the groups/ users and understanding them
how to the design the feature as part of the workshop?
will reach out once reading through it
appropriation in the context of cultural appropriation
likes idea of expanding interface
progressive and post-growth? Philip will go with DIA term but makes a note how karrot is using progressive interface
show karrot to the post-growth community, maybe meet new people/ contributors?
still happy about co-authors
Bruno: yes!
how we operate, take decisions, distribute money, mention this aswell? not only about the product but the process behind that, has many facets
add a sentence to describe our culture, not so easy to pin it down
statistics inconsistency
report from Daniel
Nathalie gave intro to the issue, statistic page and feedback tab on place
need to bring this topic into this call
recreate it? donât have access to Luxembourg data
other type of data report, export data and customise report, long thread in karrot group
push problem to technical user in group
how to recreate the issue?
ask Daniel more?
rounding error
look into Warsaw group
query on statistic page is really complicated, but some work was put into this in the past
need to gain motivation to dig into this
find a time for Vasâ focus-âperformance reviewâ session
use a coworking session or general call
do a short general call and to performance review after
session to ask for feedback, structure borrowed from sociocracy
proposal: split next meeting in 2 parts, 1.5h in total
seems fine
Nathalie and Vas will prepare
Next:
opencollective (linking opencollective and karrot instance) [vas]
5. Actions and Outcomes
rework from scratch agreement related to data interventions [vas] II
write follow up about CSS on forum post [Nathalie] II
sit down and think what to do after Bristol personally [Nathalie] II
forum post on Bristol days - ongoing [vas] II
start working on guidance document for âperformance reviewsâ [Nathalie, Vas] II
transfer money to karrot [Jay] II
pad release party planning [Nathalie] II
e-mail Nlnet [Nick] I
continue working on getting polls ready to merge [Nick] I
communicate with coop cloud about our payment [Nathalie] I-
continue working on sanctions design [Bruno]
vas do your invoices [Vas]
add a sentence to workshop paper [Bruno, Vas]
check own group to see if thereâs inconsistency on statistic, add to board [Bruno]
Bruno: fine to me. 1st one is good, work on yourself, donât feel very affected by that, its a nice action point, sharing negative feelings is better having a chat with Nathalie, came mostly from Nathalie, had also a feedback on what Nat meant, have a chat with Nat, keeping a balance to the personal and the project, its a matter of balance and group dynamics, writing CV of Karrot could be interesting and a video presentation could be good in general, CSS thing looks nice, we can just start with it, there is nothing stopping it to start it right away, regular updates thatâs good, be clear on the status of what ur doing, that connects to the guilt feeling, not gonna happen (its on hold, abandon this or that). Welcome the feedback, one thing I was missing the appreciation toward following up with the groups, keeping up those connections, maybe incorporate that. So ther is a question of why this was left out? (time, motivation etc?)
Nick: putting the guilt in the fire, its good, embrace active motivation, no need to keep the guilt, âwhat is my motivation nowâ is potentially helpful with that, agree with doom and gloom, like that wholeself approach, brunoâs point to remind that nathalie that is not quite what i meant, i d rather have u in the calls with doom and gloom, karrot also functions as a human connection thing as well, I m happy to have ppl to show up as humans, funding thing is very welcome, particularly considering that u got some insights from the academic world, would like to see a more âstrategicâ approach on funding karrot, css thing and curious if it feels good or if u feel pressured on that, if there is a way to engage with it just now can be useful from ur âkarrotâ point of view. if u get a position then its good, and a paper alike would be useful to have it. CSS been in limbo for long time, writing with people so didnt get a sense where we are at, is it gonna fall in the gaps?. Feedback on dev feautures this is where I d love more focus on, it a core part of what comes out of our discusssions, the tangible things, as soon as one thing is deployed then all comments/views/concerns come up, more proactive feedback can be useful and very welcome. Following up with groups is sth I see valuable.
vas:
didnât leave out connecting with groups on purpose, need to make sure there is time/energy, can incorporate it as âintentionsâ plan, to work towards the direction
doom & gloom: was constructive what I heard from Nathalie, in two minds. not sure how good it is for me to verbalize stress, I know I can share it. maybe needed this advice. unsure how to proceed right now
guilt: comes from inability to have schedule/plan etc. donât feel can contribute a lot, always in small amounts in this or that⌠can see how that sense can come contagious, happy to put it in the fire! or even pretend not to feel guilty ⌠feels clearer to feel motivated to reach out to the academics, etcâŚ
CSS: a bit hesitant, happy butze and matt and keen to work on it together. canât change perspective that there is big difference between academic paper and trying it out in real life, cannot take on responsibility of it in karrot on my own. receptive to ideas of Just Trying It Out too.
feedback on using pad inside karrot
scroll was jumping up back to cursor, liked using it, opened it on mobile, everything syncâd ok, wondering how it works with copy and pasting, how to use it for next solikyl meeting? lots of open questions then, how to organise pads, put content into different places in karrot, etc.
karrot suite (like adobe suite), maybe could have an own pad in karrot to keep track of diary notes, @-mentions using full display name is quite long (for vas), great having pad
Nick: wanted a full screen, struggling a bit with my windows, unify one window where u got faces and pad and chat all together would be nice, the @mentions use the display name, the karrot suite/sweet I like, saw recently a all-in one productivity suite, all-in-one community organising tool would be a way forward?
write up summaries of the conversations I had (notes from last co-working with Eszter/ Bruno, key thoughts from chat with Nick, feedback from Daniel) and post on forum
collect all relevant links for rfp and ask someone to submit it
make improvements based on todayâs feedback
clarify work on âDevelop permissions systemâ
Reaction
Bruno: nice things
@ mentions is a nice touch
roles and the profile page
display of the roleholders at each place
connecting role to place: another way to do it would be that this role can be linked to a place, so when someone gets a role then they are prompted to connect the role to the place, will allow for some flexibility, would reduce the complexity possibly
newcomer role is not clear on the design what is the dif between that and member role
system roles: some kind of visual cue that they refer to system roles so you can distinguish them from the groupsâ self-made roles
Nick:
I think its very nice, good idea to get Daniel feedback as well
members page could also show roles, but leave it for now
how does âapprovedâ role fit in? get rid of it? itâs a trust-based role. not many groups have it now
role in places: enabling role for each place vs blank mode (assign any place). board member example: board member of a store? store coordinator for not a store? there should be a store coordinator, even if not filled. Which roles are relevant for which places? Show vacancies.
complexity comes with roles at places, adding bureaucracy. Place list could be enormous for some groups
newcomer: anyone that doesnât have another role (expect member). Maybe we donât need it? shows green indicator when signing up for activities. There were reasons it was implemented
Vas:
design looks very elaborated, very happy with this
not much to add
approved role? how do we fit it in there. Adopt it to the new design.
Nathalie:
thank you for useful feedback and happy how it lands
makes sense to me to create the roles in the places
agree with the complexity
Consent round: on the proposal for roles, on the broad concept as presented by Nathalie
Bruno: I consent but not fully convinced of how display vacancies outweights the complexity added
Vasileios: I consent
Nick: I consent and note that further details can be refined
C&T= communities and technologies conference in siegen this summer
some updates/reflections/concerns
expecting paper to get accepted this time
some doubts around distinction between existing collaboration software production methods (e.g. open source)
bruno:
sounds worth elaborating the tom-ayto tom-aaaarto distinction
highighting differences between commons based peer production, etc.
perhaps difference between users and producers is bigger in other models, and expertise required
nice! curious to read a draft
nick:
from karrot perspective: weâre missing a model. Once we get a model we can start doing stuff! User participation, contribute money, how to meaningfully bring users in it
waiting period to get a model
paper and concept: focus on conference and what the academic world says
proceed with what karrot is doing, then academia can write about it
karrot-centered perspective: should we just proceed or wait for a concept?
for me concept is very distinct, e.g. open-source is not an economic model, itâs an capitalist term actually
CSS direct grass-roots vibe, out it into practise
keen to bring it in discourse with other people, wait till there is a paper/ open thing to share. E.g. gfsc
nathalie:
would benefit from another presentation, once have capacity
feel a bit bad not really reading through your work
maybe can bring it to the space, or co-working, and get head into it
not really sure about the academic discourse, or what the definitions are, so right now canât really comment on the content level
agree with question of are we waiting for something to come out to start, or can we make our own sense of it, but would like to know what is out there already, and what is still missing, what would we need to define in terms of applying it
happy youâre still working on this!
nice to understand community driven things as subset of open source, and nice to bring it Matt with his community tech focus
is this conference in siegen relevant for karrot as a team?
vasilis:
good feedback
a bit of a division between what we say, and what the academics I need to reference are saying
I have to balance world of acadmics, e.g. post doc application, and can be valuable having something coming back for karrot that is peer-reviewed, and presented in a conference, and get some funding to pilot it in a project
different between frameworks and models, model is quite strict - take it and put it somewhere and it works. framework is more open and flexible, and have itâs own life in a project.
have a dictionary/lexicon at the end, and define key points and terms
discussions around local/hyper-local, heterogeneous/homogeneous
something to start building on, and other terms coming to support it, developing a language of communciation for how you can try out a framework