From: Steve George <steve@futurile.net>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Ekaitz Zarraga <ekaitz@elenq.tech>,
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 12:22:55 +0100 [thread overview]
Message-ID: <7fleyy5mw7qfubxp6v7suulvaoc3ps3qsmm5vijrwibo7k6ldn@rzvgeyhp4utx> (raw)
In-Reply-To: <d6b81bddebccf390c7220b364980274d@libre.brussels>
On 25 Oct, indieterminacy wrote:
> On 2024-10-25 11:37, Ricardo Wurmus wrote:
> > Ekaitz Zarraga <ekaitz@elenq.tech> writes:
> >
> > > Ricardo, I can agree with you but how do you reward just being there
> > > and doing the dirty job?
> >
> > For reviews, for example, one could find an arbitrary set of metrics and
> > hand out an award with a monetary component at an annual event. I'm not
> > speaking of sustainable funding of that work, but of a mechanism to both
> > publicize the importance of the work and to add a social component to
> > recognizing it.
>
> I suppose one could tie the concept of volunteering activity with a voucher
> system,
> which could then be pooled/collected with to a Guix theme for funding.
>
> For example, it could well be that patch reviewers have a desire to valorise
> a specific activity.
> Getting a specific volume of patches signed off could reach 70% of the
> threshold.
> The remaining 30% is made up from the 'circles' concerning the languages Foo
> and Bar.
>
> ... perhaps there are some anarcho-syndicalists out there who can recommend
> something more nuanced.
(...)
There's lots of simple and light-weight methods *IF* there's an organisational structure that can do it. And really, these things don't have to be complex.
FreeBSD and Clojurist Together are great examples of small teams that provide small grants to support work in areas. So I think there's lots of ways we could explore the territory and experiment a bit.
Steve / Futurile
[0] FreeBSD have a simple process for example - https://freebsdfoundation.org/our-work/grants/
[1] https://www.clojuriststogether.org/projects/
next prev parent reply other threads:[~2024-10-25 11:23 UTC|newest]
Thread overview: 42+ 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 [this message]
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-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-11-01 17:03 ` Attila Lendvai
2024-11-01 21:14 ` 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-11-01 11:50 ` (unrelated and off-topics) Visiting a future of GNU Simon Tournier
2024-11-01 13:53 ` Ricardo Wurmus
2024-11-08 8:47 ` Andreas Enge
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
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=7fleyy5mw7qfubxp6v7suulvaoc3ps3qsmm5vijrwibo7k6ldn@rzvgeyhp4utx \
--to=steve@futurile.net \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=indieterminacy@libre.brussels \
--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 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).