Date: 13-01-2021 Participants: Bruno and Vasilis # Meeting to discuss landing page, language, communication etc. - Vasilis talks about presentation in the conference --> Gender diversity and queer-ecology - The importance of language and words, like community vs. group - How to make Karrot less gender-biased? more gender-fluid? more performative? - Bruno: likes the discussion we had at the last meeting - adopt Katie's suggestion: "start a group, become a community" - focus on "group", but not get rid of the word community entirely but make its meaning clear - Problems with the word voluntary - state outsourcing - big charity organization: a different logic - add "automonous"? autonomy vs. heteronomy (something coming from the outside) - combination of voluntary and autonomus--> can lead us to the right wording - What do we think about "no bosses, no profit"? - no traditional admin structure - no bosses refers to the structure of the group - Suggestion: "No bosses, no admin superpowers, and no profit, whether..." - Rewrite "Democratic and trust-based group management"? - a problem with management - Replace it with "governance", even though governance features are not complete - Talk about the sreenshot - we should change it: a mockup or real groups? - having screenshots of real groups is part of engaging them - a little gallery of screenshots explaining the main features. Caption on each screenshot, to show what people can do on Karrot: - activities - wall - applications - ... - tutorial videos could be included there somewhere? But maybe while creating a group - how could we make karrot more gender neutral and avoid stereotypes - photos, language etc - gender discimination in Bruno's group - how can we design 'gende neutral' infrastructures --> take an active stance as karrot? - open up a thread on forum or open up more the disucssion with members of the other groups - conflict resolution mockup instead of a screenshot - mockups vs real group's screenshots - Part "independent groups" - rules and agreements/processes - change the screenshot on the side? Maybe including the map? - "Distribution of tasks and activities" - add more examples for meetings and activities e.g. activities like a collective bikes' mending, food-picking, collective kitchen or whatever else a group might think of... - "Activities with a specific time and place, like meetings, food pickups, community events, or whatever your group needs can be entered in the software." - "Share things" - "Create an offer of whatever you want to share or give away." - Problem with translation of "Offers" - similar to "sales" in many other languages (de, sv, pt-br, maybe more?) - Alternatives: gifts, shared items Date: 26-01-2021 Participants: Bruno and Vasilis and Nick Vasilis notes before the meeting: What do we need to have on the landing page: - logo - sign in/register - a short but clear set of sentences (which are graspable and not flowery) where we present karrot's vision and potentiatilities - open source - transparent (?) --> how data are treated I reckon is important especially for groups that would already use other proprietary platforms (e.g. fb) - affordances of Karrot and politics of its code which have led to implementing such affordances - similarly to how data are used/stored etc i think it's important for sb to be aware of the 'specific'/tailor-made affordances of karrot vs those of other apps which are not designed for sharing initiatives per se (e.g. FB) <-- how we state that withough going into details? How autonomy and democratic operation for example are hard coded? We do not need to go into details but somehow state and imply our vision which is manifested via the code. - looking back on the sentece we have incoroporated 'No bosses, no admin superpowers, and no profit, whether you are saving food, sharing bikes, caring for a community garden or maintaining a makerspace' along with lux group rules I can see some problems. It seems to me tha lux group does have a structure of managers and aministratos --> how lux group would thus react in such a turn? Wouldnt they prefer to have a software that can support their real-life structure? Could that lead em to leaving karrot and using other apps? In short the 'No bosses, no admin superpowers, and no profit, whether you are saving food, sharing bikes, caring for a community garden or maintaining a makerspace' could be a nice staring point for newborn initiaties that do not have a structure in place but how about existing groups that have some strucuture(s) in place? - examples illustrating the softwares affordances -looking back on the lading page so far... - "Karrot exists for groups of people who want to coordinate real-life activities on a local, autonomous and voluntary basis". <-- could we incoroporate sth that points at a collective coordination? e.g. ' who want to coordinate real-life sharing activities....' - I tried to merge ' Karrot exists for groups of people who want to coordinate real-life activities on a local, autonomous and voluntary basis. It is a tool for all kinds of grassroots initiatives to connect and grow, supporting the co-ordination of face-to-face activities with a layer of digital infrastructure. No bosses, no admin superpowers, and no profit, whether you are saving food, sharing bikes, caring for a community garden or maintaining a makerspace..... Karrot is made by its users: a free and open-source software developed with the feedback and participation of the people who use it. It is mainly developed by a small core team that is constantly in contact with people in different groups, in order to make sense of their diverging and converging needs and thus guide the development. We abide by the ethics of integrity and non-commercialization of data' cause I felt we're saying the same thing twice and we leave aside some important karrot bits. - I turned it into the following withough implying that all the above should be deleted --> I was just aiming at summarizing all the important bits in one graspable(?) sentece/paragraph - Karrot is a free and open-source, participatorily designed, digital tool which is developed to support (and not outplace) the face-to-face sharing actvities of various groups and grassroots initiatives. Whether groups created to organize foodsaving and foodsharing, bike-sharing, caring for a community garden, running and maintaining a makerspace etc. - Via its code and designs, Karrot aims at favoring autonomy, democratic cooperation, transparency, community-building and inclusiveness. Similarly Karrot aims at promoting a generative sharing culture while raising awareness around the values, importance and potentialities of genuine sharing practices. - Every group on Karrot is completely independent and can have their own logo, processes, rules and agreements. <-- - And more.. - I think we should work on this and more..why do we need this bit, what parts of that we need?, how we rephrase them, or should we change their placement on the landing page? ~~"It is a tool for all kinds of grassroots initiatives to connect and grow, supporting the co-ordination of face-to-face activities with a layer of digital infrastructure."~~ "Karrot is a free and open-source tool for grassroots initiatives and groups of people that want to coordinate face-to-face activities on a local, autonomous and voluntary basis." It is designed in ways to enable community-building and support a more transparent, democratic and participatory governance of your group. [screenshot] Whether you are saving and sharing food, running a free shop or a makerspace, keeping a community garden or a bike-kichen... [pictures] ~~It can be used by initiatives like food saving and sharing groups, bike-sharing, caring for a community garden, running and maintaining a makerspace etc. ~~It can support groups practicing foodsaving and foodsharing, bike-sharing, community gardening, running a makerspace etc. ~~Karrot can support your community-driven activities, whether you are saving and sharing food, running a free shop or a makerspace, keeping a community garden or a bike-kichen ~~ ~~Whether you are saving and sharing food, running a free shop or a makerspace, keeping a community garden ~~ ~~Karrot is designed in ways to support a more transparent, democratic and participatory governance of your group, whether you are saving and sharing food, running a free shop or a makerspace, keeping a community garden or a bike-kichen~~ Date 11/02 Landing page Participants Bruno, Vasilis Ideas to work on now: - Screenshot slideshow - or maybe not - showing main features - Need better screenshots. Ask Katie for Foodsharing Sthlm, activities page - One for applications (mockup) - One for different types of activities - Create an About-section, move "Democratic and participative development" section there Date 07/03 Landing page Participants Bruno, Vasilis - maybe we get some more photos from Katie or Bruno or whoever depicting other activities (e.g. meeting, collective cooking etc ) - Those could be clickable and point to stories - Democratic and participative development move it to the about page - different links also (as we previously discussed)--> - resources --> organize them by ways to participate (e.g. willing to participate as an activst, programmer, foodsaver etc) - mastodon - community forums - github - foodsaving.world (maybe not?) - Communication in the right context --> activity chat + place wall - karrot giving mockup - Maps and lists should we brake this down to two dif things? - Democratic and trust-based group governance is going to be broke down into 3 bits: - trust karrots and editing - creating places and activities - accepting/declining applications - conflict resolution process About page draft: About page: Karrot is a free and open-source digital tool/platform that is developed on a voluntary basis and in a collaborative manner with the feedback and participation of the people who use it. Karrot has no borders, has no managers and employees, it is not a start-up and not a business of any type. Users’ data are not and will never be shared with other parties nor will they be used for any commercial purposes. Karrot’s development is based upon ideas and values of sharing, cooperation and commoning and does not follow the popular narrative that technology can fix and replace everything. In this sense, it does not aim at substituting physical interactions but only supporting them. It was initially developed to support the activities of foodsaving and sharing groups. However its new deployments aim at making Karrot a practical tool which can additionally help more communities and groups, existing and new ones. For example, community makerspaces and libraries of tools, community gardens, community fridges and pantries, free shops, toy sharing groups etc. Developers, designers or anyone interested in Karrot’s code are always welcome to participate in its development. Currently, we meet (online) once a week (Mondays at 11.00 a.m. GMT) where we discuss about Karrot’s development. The call is open to everyone interested. More information about our past and future meetings can be found here --> https://community.foodsaving.world/t/weekly-call-about-karrot-development-2021/630/7. You can additionally check out the project on GitHub here --> https://github.com/yunity/karrot-frontend. Here-->https://community.foodsaving.world/c/karrot/7 you can find and participate in all forum topics related to Karrot and create a new one. Here-->https://fosstodon.org/@karrot you may read about Karrot on Mastodon. Karrot’s server is hosted by... notes 11 march Bruno: -screenshots slideshow/carussel - Vasilis: -short brief description -get involved -team (later)