How much time per month should an unpaid volunteer maintainer dedicate to an Open Source project?
-
@evan @joergi @preinheimer huge +1 on that. Maintainers of open source softwares don't owe anything to anyone.
@dannycolin
yes - and no.if you are the programmer of CURL where the complete internet relies on, or some similar project, you have a responsibility - but tbh, something like that should not be unpaid. so the problem is somewhere else tbh
-
This post is deleted!
-
@evan How long is a piece of string? I've worked on stuff that I could poke once a month to see if anyone had any issues.. Big projects are sometimes run like commercial entities with multiple maintainers. And all points in between.
But they're not maintaining software in a state where it works for me.. it's not about me.. They're doing it because they want to, and I (and many others) happen to benefit from that.
This post is deleted! -
@dannycolin
yes - and no.if you are the programmer of CURL where the complete internet relies on, or some similar project, you have a responsibility - but tbh, something like that should not be unpaid. so the problem is somewhere else tbh
This post is deleted! -
@evan You didn't say "what are your conditions to use software", you said "how many unpaid volunteer hours should there be". There is software with those problems with thousands of hours of investment, there is also software without those issues with very little.
I don't "owe" the project usage, and the maintainers don't "owe" the project maintenance hours.
This post is deleted! -
This post is deleted!
@evan Unknowable. Depends entirely on what the specific thing is.
-
This post is deleted!
@evan as much as they want, they're unpaid.
-
This post is deleted!
The health of the project is really a separate question. If you don't trust it, that's YOUR problem.
Either you offer to pay them π° or you... ahem... fork off. π
Free software is the proverbial gift horse. You want to look at the teeth, you need to pony up the cash.
IMHO. π€¨
-
This post is deleted!
@evan SHOULD is a really heavy word, especially around βunpaidβ.
I want it to be easy and possible for devs to maintain OSS.
I want it to be the norm & a cultural value that it happens.Private companies should sponsor more OSS maintenance to make it easier and more possible for more people.
-
This post is deleted!
@evan Zero to ~150 hours.
Beyond 150ish hours is of course possible, but I believe adequate sleep and rest should be had for obvious reasons.
-
@evan as much as they want, they're unpaid.
This post is deleted! -
@evan SHOULD is a really heavy word, especially around βunpaidβ.
I want it to be easy and possible for devs to maintain OSS.
I want it to be the norm & a cultural value that it happens.Private companies should sponsor more OSS maintenance to make it easier and more possible for more people.
This post is deleted! -
This post is deleted!
@evan I chose to interpret this question in an idealistic way, ie. as I'd like society to be. And as part of my premise would be some kind of guaranteed basic income, so everyone wouldn't have to sell their labor-power on a market and could choose their commitments in dialogue with a wider community. Given that, I picked 32 hours or more.
-
@evan Zero to ~150 hours.
Beyond 150ish hours is of course possible, but I believe adequate sleep and rest should be had for obvious reasons.
This post is deleted! -
This post is deleted!
@evan if they don't the project won't be as good, and that's okay, it's a hobby.
It's not the only reason people do things, by far, but it is the only way you can rely on someone to do something. Else, it's up to them.
Generally speaking I'd say if you want to have a great OSS project, you need to put time into it, but that may not be their goal. It may be to publish an idea, to learn a library or programming language, etc.
Maintenance is hard work.
-
The health of the project is really a separate question. If you don't trust it, that's YOUR problem.
Either you offer to pay them π° or you... ahem... fork off. π
Free software is the proverbial gift horse. You want to look at the teeth, you need to pony up the cash.
IMHO. π€¨
This post is deleted! -
@evan I chose to interpret this question in an idealistic way, ie. as I'd like society to be. And as part of my premise would be some kind of guaranteed basic income, so everyone wouldn't have to sell their labor-power on a market and could choose their commitments in dialogue with a wider community. Given that, I picked 32 hours or more.
This post is deleted! -
This post is deleted!
@evan zero
They may spend as much as they like, of course, but they are under zero moral or ethical obligation.
-
@evan zero
They may spend as much as they like, of course, but they are under zero moral or ethical obligation.
This post is deleted! -
This post is deleted!
@evan I'm going to assume you mean the RFC 2119 definition of "should", in which case the poll is asking how much time is recommended for a maintainer to reserve in their schedule each month, and not how much time they are obligated to. I think reserving a day of slack in one's schedule to be able to spend 8 hours moving things along in the project as needed is probably a good idea, but different projects and different maintainers will have radically different needs and constraints.