all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Ricardo Wurmus <rekado@elephly.net>,
	 Ekaitz Zarraga <ekaitz@elenq.tech>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>,
	 Simon Tournier <zimon.toutoune@gmail.com>,
	Tanguy Le Carrour <tanguy@bioneland.org>
Subject: Re: Discussion on Guix funding // future
Date: Fri, 25 Oct 2024 16:49:04 +0100	[thread overview]
Message-ID: <5tcu4mhx5f6hf2fmuhmrcnb32qubfo3lznbhonoqu74reudd4l@eikcb4gbgxhx> (raw)
In-Reply-To: <ZxuMkyDB25ceGSR3@3900XT>

On 25 Oct, Efraim Flashner wrote:
> On Fri, Oct 25, 2024 at 11:11:31AM +0200, Ricardo Wurmus wrote:
> > Steve George <steve@futurile.net> writes:
> > 
> > > One concern with supporting developers is whether it demotivates them
> > > in the long-term: from intrinsic to extrinisic motivation. Basically,
> > > the answer is that pay doesn't motivate but it does 'enable' for
> > > committed contributors: the Linux foundation survey shows this,
> > > there's also various academic pieces on FOSS motivation.
> > 
> > Paying some people also has the potential of eroding motivation for
> > those who are not paid.
> > 
> > *Employing* people and having their salaries be paid from donations held
> > by a foundation is a can of worms that I personally would shy away from
> > opening.  An easier and less daunting way to inject monetary rewards
> > into volunteer-based activities is to fund awards for certain
> > accomplishments.  This would strip all the complications of employment
> > and still allow for less desirable work to be rewarded.
> 
> I can no longer find the reference, but Debian experimented with having
> someone (or several someones, its been many years now) paid to fix
> release-critical bugs before one of their releases. That release went
> out about 2 months "later" than other releases, with the assumption
> being that few people were willing to do the work for free that someone
> was explicitly being paid for.
(...)

Interesting, didn't know about this, I'll see if I can find it.

Generally, I've seen the converation about "sustainability" in projects change in the last few years. The focus that 'Github Sponsors', Linux Foundation and some of the security issues brought to the issue has had an impact. This has made people much more of the need for sustainability and more likely to help out. Projects have responded - as one example, Open Collective has 2533 open source projects that are receiving donations.

> I'm worried about some sort of "recognition of exemplary work" pay-out,
> it suggests that others' work isn't exemplary enough for recognition and
> commiseration.

Yeah agreed, that wouldn't be a great idea. What the surveys say works is work that *volunteers* do not want to do, or cannot do.

> The best I can think of currently is to offer grants for travel to
> events (FOSDEM, etc) or to help fund computers and/or office furniture
> with the belief that it would make their contributions easier/faster or
> more productive. With the idea of paying for things, not paying people
> directly for their time.

Understood and seems to be a common way of supporting contributors. Both FreeBSD and KDE supported contributors computing and travel expenses.

There's other approaches that could be tried, that don't involve creating an "exemplary work" divide. I think we can be open to experimentation. It's OK to tell people we're experimenting and try things out. And, if something doesn't work try something else or decide it doesn't work in our context. If we only do the same things, in the same way, we'll get the same (reproducible?!) results ;-)

Steve / Futurile

[0] https://opencollective.com/opensource




  reply	other threads:[~2024-10-25 15:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 22:08 Discussion on Guix funding // future Ekaitz Zarraga
2024-10-25  8:12 ` Steve George
2024-10-25  9:11   ` Ricardo Wurmus
2024-10-25  9:16     ` Ekaitz Zarraga
2024-10-25  9:37       ` Ricardo Wurmus
2024-10-25 11:05         ` indieterminacy
2024-10-25 11:22           ` Steve George
2024-10-25 11:51             ` indieterminacy
2024-10-25 12:05         ` Efraim Flashner
2024-10-26 17:16         ` Tomas Volf
2024-10-25 11:06     ` Steve George
2024-10-25 12:13       ` Ricardo Wurmus
2024-10-25 12:18     ` Efraim Flashner
2024-10-25 15:49       ` Steve George [this message]
2024-10-25 12:58 ` Thompson, David
2024-10-25 14:31   ` Christopher Howard
2024-10-26  6:57     ` Steve George
2024-10-28 16:47       ` Christopher Howard
2024-10-25 19:13   ` Ekaitz Zarraga
2024-10-25 23:25     ` Attila Lendvai
2024-10-26 12:49       ` Greg Hogan
2024-10-26 13:48   ` Guix (and Guile's) promise, and how to (hopefully) get there Christine Lemmer-Webber
2024-10-26 14:49     ` Ekaitz Zarraga
2024-10-26 20:22       ` Ludovic Courtès
2024-10-27  0:38         ` Ekaitz Zarraga
2024-10-29 23:04           ` Ludovic Courtès
2024-10-28 10:09         ` Andreas Enge
2024-10-28 10:20         ` Andreas Enge
2024-10-26 16:40     ` Suhail Singh
2024-10-26 22:07       ` Ludovic Courtès
2024-10-27  1:33         ` Suhail Singh
2024-10-26 22:28       ` indieterminacy
2024-10-26 21:12     ` Ludovic Courtès
2024-10-28  9:21   ` Discussion on Guix funding // future Andreas Enge
2024-10-26 15:04 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2024-10-25 14:21 Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-10-25 21:26 ` Greg Hogan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5tcu4mhx5f6hf2fmuhmrcnb32qubfo3lznbhonoqu74reudd4l@eikcb4gbgxhx \
    --to=steve@futurile.net \
    --cc=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    --cc=tanguy@bioneland.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.