unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Ricardo Wurmus <rekado@elephly.net>, Steve George <steve@futurile.net>
Cc: "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 11:16:33 +0200	[thread overview]
Message-ID: <29442227-9dca-4da7-9fb1-622bcc1188b4@elenq.tech> (raw)
In-Reply-To: <875xpgo8cc.fsf@elephly.net>

On 2024-10-25 11:11, 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.
> 

Ricardo, I can agree with you but how do you reward just being there and 
doing the dirty job?

That's what worries me the most.


  reply	other threads:[~2024-10-25  9:17 UTC|newest]

Thread overview: 32+ 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 [this message]
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
2024-10-25 12:58 ` Thompson, David
2024-10-25 14:31   ` Christopher Howard
2024-10-26  6:57     ` Steve George
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-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-26 15:04 ` Discussion on Guix funding // future 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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=29442227-9dca-4da7-9fb1-622bcc1188b4@elenq.tech \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    --cc=steve@futurile.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).