From: Ricardo Wurmus <rekado@elephly.net>
To: Steve George <steve@futurile.net>
Cc: 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 14:13:20 +0200 [thread overview]
Message-ID: <87r084mlcv.fsf@elephly.net> (raw)
In-Reply-To: <4rvi67kmuao4qlice5odnfmsgnfygfmaxjok4xcyki77kqiref@nyel3oupgtid> (Steve George's message of "Fri, 25 Oct 2024 12:06:19 +0100")
Steve George <steve@futurile.net> writes:
> On 25 Oct, 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.
> (...)
>
> Yes, I've heard this concern both in other FOSS communities and in Guix.
>
> I actually haven't see any evidence that this is the case. Maybe you have?
I have not personally observed this in communities like ours, but I'm
not particularly perceptive and more importantly lack experience with
other communities resembling ours, so this isn't saying much.
I only know of studies of traditional "workplace" environments
(for-profit and non-profit), where wage equity and a perception of
fairness in terms of co-worker wages have a much stronger impact on
employee satisfaction and extrinsic motivation than the absolute value
of remuneration. A stronger preference for perceived fairness with
respect to peer wages has been observed in non-profits where the level
and importance of intrinsic motivation is assumed to be higher than in
for-profit environments.
It is not clear whether these findings are applicable to our loose
organizational structure, but I found it worth mentioning.
> If there were more developers
> able to sustain their efforts on Guix, I'd personally be happy for
> them.
I would, too.
--
Ricardo
next prev parent reply other threads:[~2024-10-25 12:41 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
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 [this message]
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=87r084mlcv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--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).