daniel/docs.coopcloud.tech
0
0
Fork 0
forked from coop-cloud/docs.coopcloud.tech
Code Pull Requests Activity

Contributor docs finalise for now!

Browse Source 
Closes coop-cloud/organising#87.
This commit is contained in:
decentral1se 2021-09-10 11:24:12 +02:00
parent 9512a88a48
commit 4b5759b634
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
2 changed files with 45 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

69
docs/contribute.md
View File

@ -2,49 +2,38 @@
title: Contributing guide
---
The project is really young so we don't have contribution guides setup yet.
> You don't have to be a programmer to contribute to this project!
The best thing to do is [drop us a line](/contact/) and we can work from there.
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.
Some handy links in the meantime:
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.
- [`abra` command-line tool repository](https://git.autonomic.zone/coop-cloud/abra)
- [docs.cloud.autonomic.zone source repository](https://git.autonomic.zone/coop-cloud/docs.cloud.autonomic.zone)
- [App catalogue repositories](https://git.autonomic.zone/coop-cloud)
- [Public roadmap repository and milestones](https://git.autonomic.zone/coop-cloud/organising/issues)
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.
!!! note
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.
Please note, our [git.autonomic.zone](https://git.autonomic.zone) instance
is currently set to "invite only" mode for `$reasons`. We mirror all repositories on Github
under [github.com/Autonomic-Cooperative](https://github.com/Autonomic-Cooperative) and will
respond to issues and pull requests there.
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.
## 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/).**
So far, in our thinking, we have agreed to the following:
- The hourly rate we offer is £18 (matches our internal [Autonomic](https://autonomic.zone/) rate)
- Please speak to us in the `#coopcloud-dev:autonomic.zone` ([docs](https://docs.coopcloud.tech/contact/)) before starting the work
- Please use the line items to separate different piece of work. Please include the hour count and ticket if you have one (e.g. [expense #44298](https://opencollective.com/coop-cloud/expenses/44298))
Open questions are:
- When we say "we" here, we mean [Autonomic Co-op](https://autonomic.zone/). We are the initiators of this project and the main developers at time of writing. We are not clear on what the relationship is on working conditions and ideas around governance between contributors to the Co-op Cloud and members of Autonomic. This is something to discuss further.
- We are a small organisation and do not have much capacity to manage the financial organsation of several contributors. We want to open up the project and work towards a shared governance of the project. For now, we're focussing on this "invite only mode" of compensation so we can keep it manageable for ourselves.
- It is not clear how to compensate "non-technical" tasks, organsational work and care work in the project. We want to get there.
- It is not clear how to organising estimating how long things will take and how much things will cost. Our funding is finite so we should be mindful of this.
We have received funding via [the
ECF](https://culturalfoundation.eu/initiatives/culture-of-solidarity-fund) and
can offer £18 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.

16
docs/strategy.md
View File

@ -15,3 +15,19 @@ The urgency for providing an alternative comes out of the understanding that the
As a movement, we cannot compete with corporate providers in terms of cost and scale. Their network effects and available capital means that no one project, product or organisation can create the required shift to a more widespread public interest technology.
Our strategy is to mutualise our resources to create this shift. Co-op Cloud is an attempt to create a new shared resource - an open and democratically managed, open standards based, copyleft licensed, libre software infrastructure 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/).**