From: Ihor Radchenko <yantar92@gmail.com>
To: edgar@openmail.cc
Cc: Bastien <bzg@gnu.org>, orgmode@tec.tecosaur.net, emacs-orgmode@gnu.org
Subject: Re: Org donations page statement: explain where the donations are coming to? (was: Fwd: Re: Typo in info pages)
Date: Sat, 20 Aug 2022 22:21:10 +0800 [thread overview]
Message-ID: <87ilmnm1wp.fsf@localhost> (raw)
In-Reply-To: <87lerjm2fl.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> edgar@openmail.cc writes:
>
>> On 2022-08-20 13:46, Ihor Radchenko wrote:
>>> So, what I call "team" is equivalent to donations to the overall
>>> development. These donations (note that it's not really much money) are
>>> simply an extra motivation for Org committers. Org project has no real
>>> expenses.
>>
>> Yep, I saw the amounts. I mean 1 € per week!...
>
> To be even more precise, the amounts in https://liberapay.com/org-mode
> are mostly because we created the page recently. A more appropriate
> number is in https://liberapay.com/bzg/, which was the donation page
> that had been used since years back.
I forgot PayPal and https://github.com/sponsors/bzg (They were
alternative options until
https://list.orgmode.org/871qzqg81c.fsf@gnu.org/)
next prev parent reply other threads:[~2022-08-20 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220815103505.Horde.DWF3wKyF-3UNSStJBYza742@www.vfemail.net>
[not found] ` <878rnozpnw.fsf@posteo.net>
2022-08-16 8:23 ` Fwd: Re: Typo in info pages edgar
2022-08-19 5:39 ` Ihor Radchenko
2022-08-19 8:52 ` edgar
2022-08-20 7:12 ` Ihor Radchenko
2022-08-20 13:32 ` edgar
2022-08-20 13:46 ` Ihor Radchenko
2022-08-20 13:57 ` edgar
2022-08-20 14:09 ` Org donations page statement: explain where the donations are coming to? (was: Fwd: Re: Typo in info pages) Ihor Radchenko
2022-08-20 14:21 ` Ihor Radchenko [this message]
2022-09-20 8:22 ` Ihor Radchenko
2022-09-20 8:23 ` Ihor Radchenko
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilmnm1wp.fsf@localhost \
--to=yantar92@gmail.com \
--cc=bzg@gnu.org \
--cc=edgar@openmail.cc \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
/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/emacs/org-mode.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).