Return to Video

34C3 - Organisational Structures for Sustainable Free Software Development

  • 0:00 - 0:15
    34C3 Intro playing
  • 0:15 - 0:22
    Herald: Organisational Structures for
    Sustainable Free Software Development.
  • 0:22 - 0:27
    Title says it all in my opinion and I
    think this is a very important topic.
  • 0:27 - 0:32
    The talk will be held by Mo, who has
    experience with dozens of free software
  • 0:32 - 0:38
    projects and funding sources.
    As a funder and recipient of grants,
  • 0:38 - 0:43
    contracts and donations. The stage is
    yours, give a big hand
  • 0:43 - 0:46
    and round of applause for mo please.
  • 0:46 - 0:50
    applause
  • 0:50 - 0:58
    mo: Hello everyone, nice rainy 4th day of
    Congress. Yes I'm going to talk about
  • 0:58 - 1:03
    organizational structures. What I mean by
    that and why am I talking about this?
  • 1:03 - 1:10
    I was invited to submit a talk about open
    source funding and they cut me short. They
  • 1:10 - 1:15
    gave me instead of the 60 minutes that I
    offered they gave me 30 minutes. So now
  • 1:15 - 1:19
    I'm cutting out all the part that is
    actually talking about funding. Because I
  • 1:19 - 1:25
    think before you can go and even speak
    about funding you need to understand that
  • 1:25 - 1:30
    funding can be dangerous, money can be
    very destructive for open source projects.
  • 1:30 - 1:37
    And in order to be prepared for kind of
    the next part of my talk that you're not
  • 1:37 - 1:43
    going to hear today. I want to talk a bit
    more about organizational structures and
  • 1:43 - 1:49
    another alternative title of this talk
    could be open source governance so even
  • 1:49 - 1:58
    more dry than the previous title. Before I
    go into detail of: why am I giving this
  • 1:58 - 2:07
    talk? Who am I? Why do I think I have some
    experience with all these topics? Some
  • 2:07 - 2:13
    caution, some trigger warning as you've
    might have experienced I'm using open
  • 2:13 - 2:19
    source and free software exchangeably in
    this talk and I know this can cause a lot
  • 2:19 - 2:25
    of uproar. People can die and I don't want
    anyone's feeling to get hurt I can go into
  • 2:25 - 2:31
    detail about why I'm doing this and why
    I'm using this interchangeably. Both for
  • 2:31 - 2:36
    the aspects of the licensing where it
    classically would use kind of open-source
  • 2:36 - 2:44
    licenses as well as for all the open
    source principles and guiding guidelines
  • 2:44 - 2:49
    for the development, the collaboration and
    everything that is happening on
  • 2:49 - 2:55
    organizational level. So bear with me. If
    you're a free software person I'm your
  • 2:55 - 2:56
    friend.
  • 2:57 - 3:03
    So a bit about me. In 2010 I was
    studying computer science at the Technical
  • 3:03 - 3:09
    University Dresden and as one of my side
    projects near the end of the studies I
  • 3:09 - 3:14
    started something called torservers.net .
    Torservers.net is a network of
  • 3:14 - 3:19
    organizations so we started with the first
    organization in Germany a non-profit
  • 3:19 - 3:24
    members Association. And the goal of this
    network of organizations is to run Tor
  • 3:24 - 3:31
    infrastructure. So over the years we've
    grown this network from this single
  • 3:31 - 3:37
    organization in Germany to 22
    organizations in 15 countries. Most of
  • 3:37 - 3:41
    these organizations have been set up
    specifically for this purpose to run
  • 3:41 - 3:48
    network infrastructure. And most of them
    are also charitable nonprofits so I kind
  • 3:48 - 3:53
    of accidentally learned a lot about the
    the differences between the different
  • 3:53 - 4:04
    countries. On how they look at charitable
    law and stuff like that. In 2013 I came
  • 4:04 - 4:08
    across a pretty new foundation the
    Renewable Freedom Foundation it was set up
  • 4:08 - 4:15
    in 2012 by Georg Chef the then newspaper
    owner of the Donaukurier in Ingolstadt, so
  • 4:15 - 4:21
    it's a daily newspaper and he started a
    foundation with the goal to protect and
  • 4:21 - 4:28
    preserve civil liberties in the digital
    space. And ever since we've been working
  • 4:28 - 4:32
    with dozens of organizations and dozens of
    projects across the whole sphere of
  • 4:32 - 4:40
    anything that you can basically see at the
    Congress. And we we are a small foundation
  • 4:40 - 4:47
    so we had to find our purpose in this
    space. And we are focusing mostly on
  • 4:47 - 4:54
    organizational development, taking away
    burden from people that set out to realize
  • 4:54 - 5:01
    their goals and in order to realize your
    goals you sometimes have to do stuff that
  • 5:01 - 5:09
    you don't want to do and we help with
    that. And this led to the creation of a
  • 5:09 - 5:15
    new entity in 2016 the Center for the
    cultivation of Technology. Which is a non-
  • 5:15 - 5:22
    profit limited liability company in
    Germany and a GGmbH and I will go back to
  • 5:22 - 5:29
    that and mention it later in this talk. So
    why are we here? What are we talking about?
  • 5:31 - 5:36
    I cut my talk short, I mentioned this.
    A lot of the stuff that you're going
  • 5:36 - 5:41
    to see are basically references to outside
    material. This is a complex topic and I
  • 5:41 - 5:46
    encourage you to look at the references
    and pick them up. They should be now
  • 5:46 - 5:51
    listed in the Fahrplan for this event. So
    you don't have to take pictures or
  • 5:51 - 5:58
    anything of this or follow the video to
    hunt the references they're all linked on
  • 5:58 - 6:05
    the website. And my goal for this talk is
    that there's a growing number of people in
  • 6:05 - 6:11
    our space that think critically about
    funding. That also see that more and more
  • 6:11 - 6:17
    funding is coming to this space and that
    we need to become better at at organizing
  • 6:17 - 6:24
    and learning and collectively sharing our
    experiences with funders with funding
  • 6:24 - 6:30
    entities. How to write grants and stuff
    like that and if at the end of this talk
  • 6:30 - 6:36
    maybe one or two people come up with to me
    and become part of that network that would
  • 6:36 - 6:38
    be great, that that's my hope for this
    talk.
  • 6:40 - 6:43
    So let's start on April 7th 2014. I
  • 6:43 - 6:50
    think you all well recognize this logo.
    This was one of the first times where kind
  • 6:50 - 6:57
    of in a marketing experiment people
    described a weakness in OpenSSL. This is
  • 6:57 - 7:02
    heartbleed. And heartbleed kicked off
    quite a bit of activities. There was a
  • 7:02 - 7:07
    blog post by the OpenSSL developers
    basically how they're not getting any
  • 7:07 - 7:15
    funding to do their work properly. And also
    it kicked off a lot of other research in
  • 7:15 - 7:19
    this area about how can we actually
    support open source.
  • 7:21 - 7:23
    One of the most prominent figures
  • 7:23 - 7:27
    that is walking around
    talking about these topics is Nagia Eghbal
  • 7:29 - 7:35
    this is like three references that I feel
    are very important to to look at. The
  • 7:35 - 7:39
    unstructured labor behind our digital
    infrastructure was a report published in
  • 7:39 - 7:47
    July 2016. I picked out another short talk
    of her rebuilding the cathedral at the
  • 7:47 - 7:54
    Strange Loop Conference. And she's
    maintaining a sort of a list of funding
  • 7:54 - 8:00
    opportunities so she's comparing the
    different ways to to get opensource funded
  • 8:00 - 8:05
    so if you're coming only for that part
    take a look at that list: "The Lemonade
  • 8:05 - 8:13
    Stand". Mozilla also did quite a bit of
    research they're as you know a fairly
  • 8:13 - 8:18
    large organization handling a lot of
    volunteers and a lot of volunteer
  • 8:18 - 8:24
    contributions. We also know that there's a
    lot of controversy around how well they
  • 8:24 - 8:32
    manage this and in order to improve they
    commissioned a few studies, one of the
  • 8:32 - 8:39
    studies was done by Stanford in 2009. How
    do you actually work with volunteers
  • 8:39 - 8:43
    basically the topic always is how do you
    scale and how do you keep volunteers
  • 8:43 - 8:47
    excited around your project and
    contributors. There's an interesting
  • 8:47 - 8:53
    Community Survey that I invite you to look
    at and there's a more extensive report
  • 8:53 - 9:00
    published in 2016 about the motivations of
    contributors to open source and I will
  • 9:00 - 9:07
    come back to this because this is exactly
    the crucial part when you transition from
  • 9:07 - 9:14
    a project that has been run on volunteer
    basis or that has some people involved
  • 9:14 - 9:19
    that managed to contribute to the project.
    And how to grow your project and keep that
  • 9:19 - 9:26
    spirit up and and be inclusive as a
    community. Kind of the most famous and the
  • 9:26 - 9:33
    most relevant reference here is Jono
    Bacon. Not necessarily this book. This is
  • 9:33 - 9:38
    a good book, it's a lengthy book, but he
    also gave a lot of different talks and
  • 9:38 - 9:45
    he's giving seminars about this. And I
    highly recommend his stuff. I put a small
  • 9:45 - 9:49
    note at the bottom: This book is not an
    instruction manual because it is an
  • 9:49 - 9:56
    instruction manual. And I don't like that
    style so try to read it and read
  • 9:56 - 9:59
    in between the lines. There's a
    lot of takeaways that you can have from
  • 9:59 - 10:06
    this book that are -- that you won't get if
    you follow it line by line. I think that
  • 10:06 - 10:10
    many people demand an instruction manual
    for how to manage communities and then you
  • 10:10 - 10:16
    end up with that kind of writing. But I
    still think that this is kind of the most
  • 10:16 - 10:24
    valuable book describing the motivations
    of opensource developers. He talks a lot
  • 10:24 - 10:30
    about like creating a sense of belonging
    in the community. That you need a shared
  • 10:30 - 10:36
    belief in the project and that you will
    need to have opportunity to contribute on
  • 10:36 - 10:44
    an equal basis. So this is the
    announcement of the core infrastructure
  • 10:44 - 10:49
    initiative by the Linux Foundation that is
    only roughly like two or three weeks after
  • 10:49 - 10:56
    heartbleed. So they managed to find some
    commercial companies to bootstrap a
  • 10:56 - 11:02
    program that would support open source
    infrastructure and of course the first
  • 11:02 - 11:11
    software that they supported with this and
    are still supporting is OpenSSL. And I
  • 11:11 - 11:16
    will just briefly mention a bunch of
    funding opportunities and a bunch of ways
  • 11:16 - 11:22
    how open-source projects might be able to
    get some funding. To show that there's
  • 11:22 - 11:29
    been quite a lot of movement in these
    areas. The P that you can see here is the
  • 11:29 - 11:38
    German prototype fund, that's the German
    Ministry of Education and Research that is
  • 11:38 - 11:45
    supporting this project. So there is
    German federal government money that is
  • 11:45 - 11:51
    used to fund open-source development and I
    encourage everyone of you to check out the
  • 11:51 - 11:56
    prototype fund website and look at the
    previous rounds of projects that they've
  • 11:56 - 12:03
    been supporting because I think it's an
    excellent selection. I listed a bunch of
  • 12:03 - 12:07
    others I'm not going to go more into
    detail about the funders that's for a
  • 12:07 - 12:14
    second talk, a separate talk, but you can
    find these resources like, I picked out
  • 12:14 - 12:19
    tools specifically the snowdrift wiki the
    market research they did, that Aaron did
  • 12:19 - 12:24
    is really excellent into the different
    ways of funding. And also we maintain a
  • 12:24 - 12:31
    huge list of funding sources that's, I
    think, around 300 foundations listed there,
  • 12:31 - 12:36
    not all of them fund open source
    technology. But since we are active in a
  • 12:36 - 12:44
    more broader space of like digital
    everything you will find a lot of material
  • 12:44 - 12:49
    there. One thing that I want to
    specifically pick out and highlight
  • 12:49 - 12:55
    because it hasn't been talked about before
    not that I know of. Is a program that is
  • 12:55 - 13:02
    currently in its phase of accepting
    applications. With a wonderful name of
  • 13:02 - 13:10
    ICT-24-2018-2019, it's a European
    Commission call for participation. For the
  • 13:10 - 13:19
    next-generation Internet. And this is
    relevant and interesting because the way
  • 13:19 - 13:27
    they're framing this call will show you
    quite clearly that they are interested in
  • 13:27 - 13:35
    the kind of technologies that get built by
    our communities. And sometimes the
  • 13:35 - 13:40
    language is kind of funny and the
    terminology is something that you have to
  • 13:40 - 13:46
    get used to. But I like it it's kind of
    human centric openness, cooperation across
  • 13:46 - 13:52
    borders, decentralization, inclusiveness,
    protection of privacy kind of that's
  • 13:52 - 13:59
    that's the values that also we stand for.
    And in this program the the research and
  • 13:59 - 14:04
    innovation actions that this is going to
    fund should encourage when relevant open
  • 14:04 - 14:08
    source software, open hardware design,
    access to data, standardization
  • 14:08 - 14:15
    activities. So everything that kind of our
    communities have been doing and want to be
  • 14:15 - 14:19
    doing so this is really a great
    opportunity and we will see how this will
  • 14:19 - 14:26
    end up because, and now I'm coming to the
    to the crucial point of this call. It is a
  • 14:26 - 14:30
    call for intermediaries so you're not
    supposed to apply as a project directly
  • 14:30 - 14:34
    for that kind of money because that just
    too huge the amount of money that they're
  • 14:34 - 14:43
    giving out in total budget just for this
    call is 21.5 million just in 2018. So as
  • 14:43 - 14:50
    intermediaries you can apply for these
    fundings and they're split across three
  • 14:50 - 14:55
    three different topics. One topic is
    privacy technologies.The other is peer-to-
  • 14:55 - 15:00
    peer technologies. And the third is kind
    of data mining big data stuff. And these
  • 15:00 - 15:08
    intermediaries then are responsible to
    split up that funding and give it away to
  • 15:08 - 15:13
    third parties and this is something that
    Commission calls usually exclude. Usually
  • 15:13 - 15:19
    they require you to develop everything in-
    house and make it very hard to involve
  • 15:19 - 15:25
    external participants. So this will be
    interesting to follow, the deadline is in
  • 15:25 - 15:34
    April and sometime maybe during the next
    year we will see who got this money and
  • 15:34 - 15:37
    how they're going to redistribute this.
  • 15:39 - 15:43
    Now, for dealing with money I put this nice
  • 15:43 - 15:52
    little piggy bank as a kind of contrast to
    how dangerous actually funding can be if
  • 15:52 - 15:58
    you don't think about it. So when you want
    to deal with money and I'm probably not
  • 15:58 - 16:04
    telling you any news as a as a project you
    have to decide whether you want to start
  • 16:04 - 16:10
    some kind of legal entity to help you with
    that because at certain points you don't
  • 16:10 - 16:16
    just don't want to have it go through one
    individual. So you have the option of
  • 16:16 - 16:21
    creating your own organization or you find
    an organization -- an existing organization
  • 16:21 - 16:25
    to partner with. In the hopes that it's
    kind of less bureaucratic, you already have
  • 16:25 - 16:29
    some kind of infrastructure, there's
    hopefully already some accounting
  • 16:29 - 16:35
    happening and all that stuff. So let's
    look at the two different options. The one
  • 16:35 - 16:40
    option starting your own is something that
    a lot of people feel that is the way to go
  • 16:40 - 16:46
    because they believe that they stay in
    control, right. It's your own
  • 16:46 - 16:54
    thing, you're not depending on some
    external weird partner organization. But I
  • 16:54 - 17:00
    I am warning from this model because
    you're actually creating an organism when
  • 17:00 - 17:05
    you create an organization you create some
    organism and that organism develops its
  • 17:05 - 17:13
    own life and then my experience with many
    projects is that over time the
  • 17:13 - 17:18
    organization swallows its people. And
    you're contributing to something that you
  • 17:18 - 17:25
    set out to be doing and in this
    organization. Without necessarily taking a
  • 17:25 - 17:30
    step back and deciding when to let go of
    an organization or when to restructure it.
  • 17:30 - 17:36
    It will defend itself. So, how do you do
    this? What you see here is a very
  • 17:36 - 17:44
    elaborate bylaws or chapter or the
    articles of creation of your organization.
  • 17:44 - 17:49
    And there's typically two ways to do this.
    One you go and hire a lawyer and they come
  • 17:49 - 17:56
    up with some draft document for you. This
    is kind of very often the way that people
  • 17:56 - 18:03
    do it in the US. In Europe mostly what you
    do is you copy something, you compile it
  • 18:03 - 18:08
    yourself. So in Europe you don't need a
    lawyer to create organizations. You're not
  • 18:08 - 18:16
    expected to get a lawyer involved. So what
    happens then is that you look around you
  • 18:16 - 18:21
    compare different articles from from
    similar organizations and then quite often
  • 18:21 - 18:26
    you copy different parts of these
    documents together to form your own
  • 18:26 - 18:34
    organization and the problem in both cases
    is that here what happens is that you are
  • 18:34 - 18:39
    getting some template that has governance
    structure described. That does not
  • 18:39 - 18:44
    necessarily match the governance structure
    of your project and it does not
  • 18:44 - 18:48
    necessarily match the values and the
    spirit of a collaborative environment for
  • 18:48 - 18:55
    open-source development. And this is even
    more dangerous the kind of copypasta.
  • 18:55 - 19:01
    Because you usually end up with a document
    that is in itself incoherent because some
  • 19:01 - 19:05
    of the articles at the beginning
    contradict some articles coming later and
  • 19:05 - 19:13
    when you talk to lawyers that see they see
    this over and over again. So this is not
  • 19:13 - 19:17
    something that just happens sometimes but
    this is the usual case that this is not
  • 19:17 - 19:23
    even coherent in itself. Let alone
    coherent and compatible with how you
  • 19:23 - 19:30
    actually want to run the project. And this
    is this leads to kind of a feeling that
  • 19:30 - 19:35
    you have to have these two worlds you you
    think that there are some legal
  • 19:35 - 19:42
    requirements for your organization that
    that does not exactly fit the spirit. But
  • 19:42 - 19:49
    there is opportunity there there is
    opportunity there to to express the actual
  • 19:49 - 19:55
    governance that you have in your project
    and even like probably unwritten right you
  • 19:55 - 20:01
    have some idea of how you want to work
    together. So I caution people don't just
  • 20:01 - 20:06
    copy and paste something don't go to your
    lawyer and say I want to create a non-
  • 20:06 - 20:11
    profit or I want to create a company
    because you're getting the cheap kind of
  • 20:11 - 20:18
    capitalist model of an organization. I
    call this the stack overflow effect right
  • 20:18 - 20:23
    it's copy pasting stuff from stackoverflow
    and importing it and bootstrapping an
  • 20:23 - 20:28
    organization like that. The alternative
    that you have is using a fiscal sponsor
  • 20:28 - 20:33
    that's the professional term for looking
    for partner organization and partnering
  • 20:33 - 20:39
    with an existing organization. And in the
    free software space there's a bunch of
  • 20:39 - 20:45
    those that you can pick from and all of
    these include some guidance along the way
  • 20:45 - 20:51
    especially if they're made for open source
    projects and if they're already
  • 20:51 - 20:57
    experienced with other projects. So this
    is a newspaper article that in the LWN
  • 20:57 - 21:01
    article. chooseafoundation.com is a
    website that compares a bunch of the most
  • 21:01 - 21:06
    prominent ones in the US. I want to
    highlight the Commons Conservancy. The
  • 21:06 - 21:11
    Commons Conservancy is a bit different
    model it isn't actually a fiscal sponsor
  • 21:11 - 21:17
    and it's it is a way to define your own
    governance so independently of what kind
  • 21:17 - 21:22
    of legal entities you're going to use. You
    can use the material that the Commons
  • 21:22 - 21:29
    Conservancy is producing to pick and
    choose governance models. So they have
  • 21:29 - 21:35
    documents about forking organizations for
    example. So you not only forking the
  • 21:35 - 21:40
    source code but really forking the
    organization and what happens to the
  • 21:40 - 21:46
    assets that the organization has domain
    names trademarks and stuff like that. So
  • 21:46 - 21:51
    ultimately in any case you will have to
    talk about this ugly topic and that's why
  • 21:51 - 21:58
    I use this kind of very ugly slide to talk
    about governance because that's something
  • 21:58 - 22:03
    that kind of the projects usually that I
    work with are loose collectives, are
  • 22:03 - 22:09
    politically motivated, come with anarchy
    spirit, are kind of against any form of
  • 22:09 - 22:14
    formal governance . Which is not exactly
    what anarchism is about but that's a
  • 22:14 - 22:20
    separate talk all together. Let's stick to
    this. So what we have in open source
  • 22:20 - 22:27
    actually is a lot of tools that have been
    developed, that implement the governance
  • 22:27 - 22:35
    models without it becoming kind of a long
    written statements. So when you think
  • 22:35 - 22:41
    about issue trackers, when you think about
    mailing lists the way you interact on code
  • 22:41 - 22:48
    with with revision control systems all of
    that is an implementation of inherently of
  • 22:48 - 22:57
    a governance model in open-source. And we
    are lacking those tools in the other areas
  • 22:57 - 23:03
    that become relevant for governance and
    this is basically what I want to highlight
  • 23:03 - 23:09
    in this talk so. But how do we go from
    here? How do we take all these unwritten
  • 23:09 - 23:18
    rules and this kind of spiritual or
    ethical guidelines that that we come out
  • 23:18 - 23:22
    and this will be very different from
    organization to organization. How do we
  • 23:22 - 23:26
    turn them into something that other people
    can follow? And this is important
  • 23:26 - 23:32
    especially during the phase where you
    start receiving money because then you
  • 23:32 - 23:36
    have to make a decision on how to spend
    that money and you can still make the
  • 23:36 - 23:39
    decision collectively. But over time you
    bring in people maybe from different
  • 23:39 - 23:42
    spaces and they're coming with a different
    background, they're coming with a
  • 23:42 - 23:48
    different set of ethical principles. And
    they might be spoiled already by working
  • 23:48 - 23:52
    in some bullshit company for a long time
    and then they come and they take that,
  • 23:52 - 23:58
    these these principles that they've
    learned into your nice collaborative
  • 23:58 - 24:03
    environment. And there's there's a
    tendency and I see that in many places
  • 24:03 - 24:09
    that as organizations grow up there's this
    divide between the principles for the
  • 24:09 - 24:14
    software development side and the
    principles of how the organization is run.
  • 24:14 - 24:22
    A very good book that talks about this in
    a non-technical environment about
  • 24:22 - 24:29
    organizations is this book. Frederic
    Laloux "Reinventing Organizations" and for
  • 24:29 - 24:35
    me this is very inspiring as a blueprint
    for how you can actually copy the model,
  • 24:35 - 24:42
    you will find a lot of material here where
    you can see directly how it relates to the
  • 24:42 - 24:48
    open source way of doing things. I picked
    out the quote "Impressive! Brilliant! This
  • 24:48 - 24:53
    book is a world changer!" and not because
    I believe that it is but because actually
  • 24:53 - 25:01
    as a bit of a warning because it's written
    a very enthusiastic way. So sometimes you
  • 25:01 - 25:07
    have to kind of let the author go and and
    and but still continue reading there's a
  • 25:07 - 25:11
    lot of good thinking material in there and
    one thing I want to pick out is the
  • 25:11 - 25:15
    sections where they talk about the
    different governance models in terms of
  • 25:15 - 25:21
    hierarchical structures compared to
    consensus structures. And the third and
  • 25:21 - 25:27
    the model that is highlighted across this
    book is what they call the advice process.
  • 25:27 - 25:31
    And when you look at the advice process in
    that book it's basically what our
  • 25:31 - 25:35
    communities know as rough consensus. So if
    you have an idea you have the full
  • 25:35 - 25:41
    authority to execute that idea. But you
    are you are forced to get input, you're
  • 25:41 - 25:47
    forced to get advice from the outside so
    the only way to violate kind of rules is
  • 25:47 - 25:51
    that you're not reaching out to relevant
    people for advice and relevant people are
  • 25:51 - 25:55
    the people that you work with are the
    people that might have some good ideas
  • 25:55 - 26:00
    around that topic. But they cannot block
    you the authority stays with you for that
  • 26:00 - 26:08
    decision. There's another really relevant
    section especially given what's happening
  • 26:08 - 26:13
    here with code of conducts and and all
    this. Is the clear the need of clearly
  • 26:13 - 26:18
    documented and explicit decision-making
    processes. In a way that is compatible
  • 26:18 - 26:23
    with that kind of thinking that you are a
    self-organized group and yourself we want
  • 26:23 - 26:27
    to strengthen the self organization in
    that organization. And there's really
  • 26:27 - 26:33
    interesting material in there that could
    avoid some of the weird code of conduct
  • 26:33 - 26:37
    stuff that has happened in our
    communities. So I really encourage you to
  • 26:37 - 26:43
    at least look at that section of the book.
    Another interesting thing like they have a
  • 26:43 - 26:47
    they had that he's looking at something
    some comparing some different entities
  • 26:47 - 26:53
    that use this model. In in in their own
    ways and one of them is a multinational
  • 26:53 - 26:59
    corporation in like active in 80 countries
    or something with like 20,000 employees.
  • 26:59 - 27:03
    And still they have this principle that
    anyone in the organization can spend as
  • 27:03 - 27:07
    much money as they want. As long as
    they're following that advice principle
  • 27:07 - 27:14
    that I mentioned earlier. Ao this is just
    something to inspire you when you think
  • 27:14 - 27:17
    about like managing money in an
    organization and there's a bunch of
  • 27:17 - 27:25
    projects starting to appear that are
    trying to apply open-source principles to
  • 27:25 - 27:32
    this. One is Co budget you're invited to
    look at that. The other more known is open
  • 27:32 - 27:36
    collective, open collective you can sign
    up as an open-source project people can
  • 27:36 - 27:41
    donate to your project and you can also
    establish some transparency. Because a lot
  • 27:41 - 27:46
    of time you lose that transparency of like
    what is actually happening with that
  • 27:46 - 27:51
    money, and who has access to that money
    and who can spend that money. Just briefly
  • 27:51 - 27:56
    something about funding sources I already
    mentioned the "Lemonade Stand" list.
  • 27:56 - 28:03
    There's like the three sections of like
    small donor, private foundations, public
  • 28:03 - 28:09
    funding. There's a lot to be said about
    small donors but my when people ask me
  • 28:09 - 28:14
    about crowdfunding and campaigning and
    stuff like that I I'm very reluctant about
  • 28:14 - 28:20
    that because it usually doesn't work. So
    the the only thing that works in terms of
  • 28:20 - 28:25
    raising money from small donors is that
    you can show the support of the community
  • 28:25 - 28:30
    and then get some larger donor to top that
    up and and agree oh wow that project
  • 28:30 - 28:36
    really has has users. It doesn't really
    work that well to for in most cases that
  • 28:36 - 28:44
    but that's very specific cases. So quickly
    just dealing with funders some some of the
  • 28:44 - 28:50
    learnings that I took away from from my
    work in the previous years. One that I'm
  • 28:50 - 28:54
    still struggling with is how can we make
    this planning and writing grant
  • 28:54 - 28:59
    applications fun. If any one of you has
    some exciting ideas about gamification of
  • 28:59 - 29:07
    of grant applications and I'm all ears.
    And my advice is and and that's something
  • 29:07 - 29:13
    that also a lot of people are making
    mistakes there is that plans change.
  • 29:13 - 29:18
    Right? You you you develop a plan you give
    it to the funder it's maybe for one year
  • 29:18 - 29:23
    or two year grant and they expect that
    this is going to change because it has
  • 29:23 - 29:29
    changed. It like there's no way that you
    can follow that plan line by line but
  • 29:29 - 29:36
    there's this it's it's mostly the side of
    the recipient that feels kind of weird
  • 29:36 - 29:46
    when you deviate from your plans. Do that
    change your plans communicate this early
  • 29:46 - 29:49
    and not because otherwise you're creating
    trouble at the end of the project or
  • 29:49 - 29:56
    you're doing stuff that you don't really
    want to do anymore. In terms of writing
  • 29:56 - 30:01
    grant applications a lot of things are
    kind of a mistake that people are doing
  • 30:01 - 30:06
    because they're like in the developer mode
    of thinking. Is they think in terms of
  • 30:06 - 30:11
    deliverables and deliverables in terms of
    what kind of features can we add to the
  • 30:11 - 30:15
    software. This is actually an art form
    coming up with estimates for software
  • 30:15 - 30:19
    development I encourage everyone to look
    into the material about software
  • 30:19 - 30:24
    estimation. Because it's kind of crazy I
    cannot talk more about this because I'm
  • 30:24 - 30:29
    already over time but one thing that I
    still want to mention and this is the last
  • 30:29 - 30:35
    slide. Is that in a lot of cases I've seen
    that you can think about deliveries in a
  • 30:35 - 30:39
    completely different way. You can think
    about deliverables in a way that is
  • 30:39 - 30:44
    actually supporting community growth
    rather than just feature sets and the
  • 30:44 - 30:48
    metrics of success that you can define
    there because funders want some metrics of
  • 30:48 - 30:52
    success demonstrated. Is the number of
    people that are participating on your
  • 30:52 - 30:55
    mailing lists, the number of people you
    have in your IRC channel that's all that
  • 30:55 - 31:01
    kind of stuff and redirecting some of the
    funding to the more kind of community
  • 31:01 - 31:06
    oriented hackathons, running events,
    t-shirts and all that. You know about
  • 31:06 - 31:11
    this, but usually in the moment of a grant
    application that all that gets dropped and
  • 31:11 - 31:17
    then you're struggling keeping that up so
    now that I'm over time I'm going to skip
  • 31:17 - 31:29
    like maybe a hundred of slides. And I'm
    going to end with this slide. And thank
  • 31:29 - 31:39
    you.
    Applause
  • 31:39 - 31:44
    Outro playing
  • 31:44 - 31:52
    subtitles created by c3subtitles.de
    in the year 2018. Join, and help us!
Title:
34C3 - Organisational Structures for Sustainable Free Software Development
Description:

more » « less
Video Language:
English
Duration:
31:52

English subtitles

Revisions Compare revisions