1 of 17

Community Supported Software An alternative for community tech?

Karrot

(Nick & Vasilis)

2 of 17

Few things about Karrot and us

-what is Karrot ?

- a digital tool for community-driven projects

- supported by a small team of contributors (‘Karrot-team’)

- an open source political project ‘designed with’ rather than ‘for’ the initiatives that use it

- used today by 35-40 groups; most of which are foodsaving and sharing initiatives

-who are we ?

- Nick and Vasilis from the ‘Karrot-team’

3 of 17

4 of 17

Karrot’s features

  • Apply to join a group
  • Messaging
  • Co-ordination, activities
  • Trust carrots
  • Membership review
  • History audit
  • Agreements, offers

5 of 17

About this presentation

  • Discuss the idea of Community Supported Software as a model to develop (socially and financially) sustainable community tech
  • Builds on the concept of Community Supported Agriculture & Economy
  • Introduction and Discussion
  • Short very first report
  • Future plan: experiment with the idea/model

6 of 17

How the idea of a Community Supported Software was born?

- fragility of community tech projects like Karrot

- personal engagement with Community Supported Agriculture

How to develop community tech within the hostile environment of platform Capitalism?

7 of 17

History of open source (economics)

  • 50s/60s - Produced by academics and corporate researchers
  • Bundled with hardware, until USA vs IBM antitrust case 1969
  • Closed source norm, enter Richard Stallman, GNU 1983, and GPL 1989
  • Open source as rebranding of free software without activism element 1998 - ”emphasize the business potential of the sharing of source code.”

8 of 17

Fragility of open source ecosystems

9 of 17

Evolving open source?

-OpenSSL heartbleed, failed economics of software commons

- MongoDB / Elasticsearch move to SSPL

- Open core

- Crisis of values, open source technologies are also being abused to sustain systems of inequity, violence, and oppression” -> ethical source, contributor covenant, barriers to participation by women, BIPOC, and LGBTQ contributors

- Tech for good “Developers, coders, designers, user experience people… all came together to see how they could solve the world’s biggest challenges, before going back to their day jobs on a Monday morning . (All the while wondering how they could make the move into a professional role doing this very thing) -> double/triple bottom line

10 of 17

Other economic models

  • Gift economy
  • Co-operativism, coopyleft license
  • Commons
  • CSA / CSX

11 of 17

Fragility within Karrot

  • Underfunded
    • Small donations
    • NLNet
    • Some (failed) applications to fund Karrot
  • ‘Understaffed’
    • 4-5 ‘Karrot-team’ members
  • Design ‘disagreements’
    • Karrot’s design - communities’ needs
    • Design process
    • Community Cafe
    • Karrot days & Interviews
    • Forum(s)

12 of 17

Who are we accountable to?

  • Adapt our vision and communities need’s to funders’ calls
  • ‘Waste’ energy
  • ‘applying-for-funding fatigue’

13 of 17

From Community Supported Agriculture to Community Supported Software

14 of 17

Community Supported Agriculture

-means of productions are co-owned, decisions are made collectively, are not for profit etc

-Farmers and ‘Consumers’ form a cooperative, share the risks and any surplus

-subscription in money and in kind (shifts/’beans’)

-Member-Farmers earn a decent living and are accountable to the other members of the cooperative

  • Could a similar model work on the realm of software?

15 of 17

Community Supported Software

- Member-Farmers → Member-Designers (workers, developers, main contributors…)

- Member-’Consumers’ → Member-Users (groups in Karrot)

-Member-Designers & Member-Users form a Community Supported Software Cooperative

- Member-Users contribute in money (?) (subscription) and in kind (shifts)

- Member-Designers earn a living

- Member-Users directly contribute to the project (land/garden), share time with other-members (breaking the silo)

  • Food is very different to software….writing code is very different to pruning….

16 of 17

Discussion

-reflections/comments

-identify challenges, potentials

-discuss future steps

17 of 17

Concerns? Adaptations? Nuances? Issues?

  • Funding?
  • Member-Users shifts/’Karrots’?
  • Scale?
  • Context? Cases?
    • Groups as in Karrot
    • Individuals?
    • A new project taking its baby steps?

- ……….

- ...........