From c0b0724a0af341f5609917e371e9f3f3645ba8de Mon Sep 17 00:00:00 2001 From: cellarspoon Date: Tue, 25 Jan 2022 23:30:19 +0100 Subject: [PATCH] oragnisers guide, more saved from x-archive --- docs/get-involved/index.md | 32 ++++++++++- docs/index.md | 6 +- .../comm-org.md => organisers/index.md} | 20 ++----- docs/x-archive/contribute.md | 55 ------------------- mkdocs.yml | 3 +- 5 files changed, 42 insertions(+), 74 deletions(-) rename docs/{x-archive/comm-org.md => organisers/index.md} (59%) delete mode 100644 docs/x-archive/contribute.md diff --git a/docs/get-involved/index.md b/docs/get-involved/index.md index 0bda76e..99e5b79 100644 --- a/docs/get-involved/index.md +++ b/docs/get-involved/index.md @@ -1,3 +1,33 @@ --- -title: TODO +title: Get Involved --- + +## First steps + +> You don't have to be a computer programmer to contribute to this project! + +Firstly, come say hello in our [chat room](/intro/contact/) if you'd like to help out :wave: We are happy to have designers, critical thinkers, artists, hackers, documenters, etc. involved in this project! There is a lot of work to do, if you find this project interesting, we want to have you working with us. + +We have [a weekly check-in](/get-involved/#kite-flying-hours) for contributors of this project to let each other know what we're working on, how much time we've spent on it and how to coordinate further work. + +We have a [status page](/intro/bikemap) showing what we are aiming to achieve in the near future. That gives a good overview of where we're going together. + +From this status page, we use an [issue tracker](https://git.coopcloud.tech/coop-cloud/organising/issues) where we hold discussions about what we want to do. We categorise these issues according to the bike map using these [milestones](https://git.coopcloud.tech/coop-cloud/organising/milestones). Finally, use this [board](https://git.coopcloud.tech/coop-cloud/organising/projects/8) to keep track of what we're working on right now. We collectively review these things on a weekly/monthly basis to keep track of our time spent vs. budget available. + +Once you've found something to work on and are introduced, we'll give you an account on our [time tracking infrastructure](https://kimai.autonomic.zone) where you can log your times. This helps us reduce the burden of financial and time keeping admin falling on one person. + +We have received funding via [the ECF](https://culturalfoundation.eu/initiatives/culture-of-solidarity-fund) and can offer £16 hourly rate for your work. We've written more on why we think it is important to compensate all contributions for this project below. + +## Compensation + +We think that it is important to focus on making the libre software ecosystem sustainable. This has historically [not been the case](https://www.fordfoundation.org/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf). It feels important to contextualise this position. In the words of [LURK](https://lurk.org): + +> Big tech and an abusive misunderstanding of free and open source software practices have led us to believe that software production, server maintenance and on-line services should be free as in gratis. However there is no such things as a free lunch and software does not exist in a vacuum. If we want sustainable alternatives and a diverse cultural sector, these alternatives and the humans behind them, need to be supported. + +And a short excerpt from [Seven Theses On The Fediverse and The Becoming Of FLOSS](https://archive.transmediale.de/content/seven-theses-on-the-fediverse-and-the-becoming-of-floss): + +> Without substantial funding for ongoing development and maintenance, these projects will remain contingent upon the exploitation of the free labor of well-meaning individuals, or subject to the whims of people making time for their FLOSS hobby. + +We want to build a flourishing, inclusive, accessible project and paying people for their work (not just writing source code, but other forms of organising and care work too!) has a role to play in that. We think that making it possible to compensate contributors for working on Co-op Cloud is a way to get involved with self-organising sustainability from the start. + +We haven't worked this all out. We've opened up an [Open Collective account](https://opencollective/coop-cloud) and we're running this as an "invite only mode" approach. **If you want to make a contribution to Co-op Cloud and you'd like to be compensated, please [come and chat to us first](/intro/contact/).** diff --git a/docs/index.md b/docs/index.md index 140ff46..47271fe 100644 --- a/docs/index.md +++ b/docs/index.md @@ -20,12 +20,14 @@ We'd be happy to hear feedback about our documentation, if it was helpful, what - [Operators guide](/operators/): You run a Co-op Cloud instance or want to do so :computer: +- [Maintainers guide](/maintainers/): You maintain recipes and ensure things run smoothly for operators :tools: + +- [Organisers guide](/organisers): You're here to do some good 'ol fashioned community organising :fist: + - [Recipes](/recipes/): You want to know what recipes are packaged so you can deploy them as apps :nerd: - [Get involved](/get-involved): You'd like to help out with the project, we've love to see you stick around :heart: -- [Maintainers guide](/maintainers/): You maintain recipes and ensure things run smoothly for operators :tools: - - [CLI deference](/cli/): You need a command-line reference (`abra`, `docker`, etc.) :notebook: - [Glossary](/glossary/): You'd like clarification about project terminology :book: diff --git a/docs/x-archive/comm-org.md b/docs/organisers/index.md similarity index 59% rename from docs/x-archive/comm-org.md rename to docs/organisers/index.md index 8c162b8..87d5b12 100644 --- a/docs/x-archive/comm-org.md +++ b/docs/organisers/index.md @@ -1,26 +1,16 @@ --- -title: Community Organising +title: Organisers Guide --- -## Monthly updates on progress +## Monthly updates -We have decided we'll try to do monthly progress updates. These will be published on the Co-op Cloud blog. - -It's a pretty loose format and we're basically just copy/pasta'ing things to a public pad during the month: - -> [This month in Co-op Cloud](https://pad.autonomic.zone/YHKn4vHORmS6wjN1t2zi5A?both) - -Feel free to add your items to the monthly agenda and they will be included! +We have decided we'll try to do monthly progress updates. These will be published on the Co-op Cloud blog. It's a pretty loose format and we're basically just copy/pasta'ing things to a public pad during the month: ["This month in Co-op Cloud"](https://pad.autonomic.zone/YHKn4vHORmS6wjN1t2zi5A?both). Feel free to add your items to the monthly agenda and they will be included! All the previous posts can be seen [here](https://coopcloud.tech/blog/). ## Kite Flying Hours -The "Kite Flying Hour" is a weekly public moment where anyone can "drop by" into a Jitsi call and ask/do/propose whatever and meet some people who are currently working on the project. We haven't worked it all out but our process for now is the following: +The "Kite Flying Hour" is a weekly public moment where anyone can "drop by" into a Jitsi call and ask/do/propose whatever and meet some people who are currently working on the project. We haven't worked it all out but our process for now is the following. -- Someone from Autonomic will volunteer to be present and talk about the project for an hour weekly from 15:00 CEST - 16:00 CEST -- We announce the hour via our socials - - A [pinned toot](https://social.coop/web/statuses/106528094828958420) on [`@coopcloud@social.coop`](https://social.coop/@coopcloud) - - A [pinned tweet](https://twitter.com/Coop_Cloud/status/1412028519056609286) on [`@Coop_Cloud`](https://twitter.com/Coop_Cloud) - - A post to the `#coopcloud:autonomic.zone` room +Someone from Autonomic will volunteer to be present and talk about the project for an hour weekly from 15:00 CEST - 16:00 CEST. We announce the hour via our socials: A [pinned toot](https://social.coop/web/statuses/106528094828958420) on [`@coopcloud@social.coop`](https://social.coop/@coopcloud) and a post to the `#coopcloud:autonomic.zone` room. Here is some invitation boilerplate which you can use: diff --git a/docs/x-archive/contribute.md b/docs/x-archive/contribute.md deleted file mode 100644 index e288367..0000000 --- a/docs/x-archive/contribute.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Contributing guide ---- - -> You don't have to be a programmer to contribute to this project! - -Firstly, come say hello in our [chat room](/contact/) if you'd like to help out -:wave: We are happy to have designers, thinkers, hackers, documenters, etc. -involved in this project! There is a lot of work to do, if you find this -project interesting, we want to have you working with us. - -We have [a weekly check-in](/comm-org/#kite-flying-hours) for contributors of -this project to let each other know what we're working on, how much time we've -spent on it and how to coordinate further work. - -We have a [public bike map](https://pad.autonomic.zone/s/C3uuqfSCk) showing -what we are aiming to achieve in the near future. That gives a good overview -of where we're going together. - -From this bike map, we use an [issue -tracker](https://git.coopcloud.tech/coop-cloud/organising/issues) where we hold -discussions about what we want to do. We categorise these issues according to -the bike map using these -[milestones](https://git.coopcloud.tech/coop-cloud/organising/milestones). -Finally, use this -[board](https://git.coopcloud.tech/coop-cloud/organising/projects/8) to keep -track of what we're working on right now. We collectively review these things -on a weekly/monthly basis to keep track of our time spent vs. budget available. - -Once you've found something to work on and are introduced, we'll give you an -account on our [time tracking infrastructure](https://kimai.autonomic.zone) -where you can log your times. This helps us reduce the burden of financial and -time keeping admin falling on one person. - -We have received funding via [the -ECF](https://culturalfoundation.eu/initiatives/culture-of-solidarity-fund) and -can offer £16 hourly rate for your work. We've written -[more](/strategy/#compensation-for-contributions) on why we think it is -important to compensate all contributions for this project. - -## Compensation for contributions - -We think that it is important to focus on making the libre software ecosystem sustainable. This has historically [not been the case](https://www.fordfoundation.org/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf). - -It feels important to contextualise this position. In the words of [LURK](https://lurk.org): - -> Big tech and an abusive misunderstanding of free and open source software practices have led us to believe that software production, server maintenance and on-line services should be free as in gratis. However there is no such things as a free lunch and software does not exist in a vacuum. If we want sustainable alternatives and a diverse cultural sector, these alternatives and the humans behind them, need to be supported. - -And a short excerpt from [Seven Theses On The Fediverse and The Becoming Of FLOSS](https://archive.transmediale.de/content/seven-theses-on-the-fediverse-and-the-becoming-of-floss): - -> Without substantial funding for ongoing development and maintenance, these projects will remain contingent upon the exploitation of the free labor of well-meaning individuals, or subject to the whims of people making time for their FLOSS hobby. - -We want to build a flourishing, inclusive, accessible project and paying people for their work (not just writing source code, but other forms of organising and care work too!) has a role to play in that. We think that making it possible to compensate contributors for working on Co-op Cloud is a way to get involved with self-organising sustainability from the start. - -We haven't worked this all out. We've opened up an [Open Collective account](https://opencollective/coop-cloud) and we're running this as an "invite only mode" approach. **If you want to make a contribution to Co-op Cloud and you'd like to be compensated, please [come and chat to us first](https://docs.coopcloud.tech/contact/).** diff --git a/mkdocs.yml b/mkdocs.yml index a45f8d5..25d7145 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -46,9 +46,10 @@ nav: - "Get in touch": intro/contact.md - "Credits": intro/credits.md - "Operators Guide": operators/index.md + - "Maintainers Guide": maintainers/index.md + - "Organisers Guide": organisers/index.md - "Recipes": recipes/index.md - "Get Involved": get-involved/index.md - - "Maintainers Guide": maintainers/index.md - "CLI Reference": cli/index.md - "Glossary": glossary/index.md