Snow Strolling #SilentSunday
Uncategorized
1
Posts
1
Posters
13
Views
-
Snow Strolling #SilentSunday
-
undefined oblomov@sociale.network shared this topic on
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@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.
-
@tess If they put in zero hours, the software is unmaintained. They are no longer maintainers in that case. The question is about maintainers.
If someone is *a maintainer*, *maintaining software*, how much time should they expect to put in?
-
@evan zero
They may spend as much as they like, of course, but they are under zero moral or ethical obligation.
-
@malte for a single project?
-
@TerryHancock @preinheimer @joergi so, does unmaintained software have maintainers?
And how about you switch the roles around? If you are deciding whether or not to become the maintainer of a piece of software, how much time should you plan to put into it?
-
-
@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.
-
@txtx you could go all the way to 744, or even a few more if you're willing to do some travel across timezones at the beginning and end of the month.
