From: Timothy <tecosaur@gmail.com>
To: rms@gnu.org
Cc: Vikas Rawal <vikasrawal@gmail.com>,
yantar92@gmail.com, bzg@gnu.org, c.buhtz@posteo.jp,
emacs-orgmode@gnu.org
Subject: Re: Links to javascript-based websites from orgmode.org: Paypal and Github
Date: Mon, 04 Jul 2022 12:32:35 +0800 [thread overview]
Message-ID: <87fsjhz7t0.fsf@gmail.com> (raw)
In-Reply-To: <E1o8CwD-0003xH-8k@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3808 bytes --]
Hello All,
I’ve been viewing this thread with trepidation for a while, and I’ve reached
a point where I feel compelled to add another 2c of mine.
> It’s about the GNU Project’s moral stand (nonfree software is an
> injustice, and encouraging people to use it is wrong), and what
> follows from that.
>
> The GNU Project takes a less extreme position: if a business asks
> customers to use nonfree software to communicate with the business, we
> advise people to refuse to use that software.
>
> Sometimes it’s possible to do business with that company
> and avoid the nonfree software. Sometimes it’s not.
>
> As this example shows, there are various different kinds of
> scenarios involving businesses and nonfree software. The GNU Project
> makes these distinctions and treats them differently.
This is all very well and good, however in this case we don’t seem to be dealing
with “a company” per se so much as the entire financial sector.
Hence, I find the question underlying this thread to be whether we should be so
uncompromising in avoiding directing users to non-free JS, that maintainers
should be effectively prohibited from soliciting donations.
Forgive me for this ideological transgression, but I personally find this
absurd. I hold that the GNU project and FSF should do everything reasonably
possible to promote FSF and help support the lovely people who devote time an
effort into enriching FOSS. I don’t think it’s news to anyone that FOSS devs are
overwhelmingly underappreciated and under-compensated for the work they do. We
do not do this for the money, but it dignifies the work we do and allows some of
us to devote more time to working on FOSS.
Adding significant road blocks between philanthropic individuals looking to
support a project they like and the project maintainers helps no one in the end.
In this entire 40+ message thread, only two options have been listed (besides
the FSF’s special arrangement) which do not direct people to non-free JS:
Cryptocurrancy
Which is volatile in value, regional regulation, and
individual distaste.
Cheques
Which are a dying (and in some places dead) form of bank transfer
instruction. It’s already been established that Ihor would face a US$200 fee
when collecting a cheque, and over where I am the central bank announced in
2019 that at a point in the near future the “it will be appropriate to wind up
the cheque system”. Last year a neighbouring country stopped offering or
receiving cheques altogether.
I think it’s fair to say these are not viable options, leaving accepting
donations via Liberapay, Stripe, etc. as the only practical options. Until then,
let’s not allow perfect to be the enemy of good.
As it happens though, Stripe seem to have open sourced all of their frontend
code — all of these repos <https://github.com/stripe> seem to be MIT-licensed.
Perhaps we just need to get this to be compatible with liberajs?
Alternatively might the FSF be able to accept donations on the behalf of various
projects and distribute the money accordingly? Should the FSF indeed be the only
organisation capable of taking donations in a proper manner, why isn’t this
offered as a service for the wider community instead of withholding this freedom
and just complaining that others don’t provide it?
So, to sum up the situation I’d suggest we pick from the following options:
⁃ Accept the situation isn’t great
⁃ Build/fund a new tool
⁃ Convince an existing tool to be more libera-friendly
⁃ Use the FSF as an intermediary
Asking maintainers not to accept donations (or making it prohibitively
difficult) is not a solution.
All the best,
Timothy
next prev parent reply other threads:[~2022-07-04 6:56 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 11:29 Communication problems and possible problems with the website c.buhtz
2022-02-25 12:20 ` Byung-Hee HWANG
2022-02-25 12:25 ` Russell Adams
2022-02-25 12:38 ` c.buhtz
2022-02-25 13:12 ` Russell Adams
2022-02-25 12:57 ` Ihor Radchenko
2022-02-26 9:09 ` Bastien
2022-02-25 12:30 ` Ihor Radchenko
2022-02-25 12:48 ` c.buhtz
2022-02-25 14:18 ` Ihor Radchenko
2022-02-25 14:24 ` c.buhtz
2022-02-25 15:08 ` Russell Adams
2022-02-26 9:19 ` Bastien
2022-02-25 15:14 ` Links to javascript-based websites from orgmode.org: Paypal and Github (was: Communication problems and possible problems with the website) Ihor Radchenko
2022-02-25 15:38 ` Michael Powe
2022-02-25 17:39 ` Links to javascript-based websites from orgmode.org: Paypal and Github Bastien Guerry
2022-02-26 5:50 ` Ihor Radchenko
2022-02-26 8:57 ` Bastien
2022-02-26 15:18 ` Jean Louis
2022-02-27 17:18 ` Bastien Guerry
2022-02-27 17:32 ` Neil Jerram
2022-02-27 4:11 ` Richard Stallman
2022-02-27 17:57 ` Bastien
2022-02-27 4:43 ` Bradley M. Kuhn
2022-03-20 11:27 ` Ihor Radchenko
2022-03-21 1:22 ` Bradley M. Kuhn
2022-02-27 11:29 ` Max Nikulin
2022-02-27 12:58 ` Timothy
2022-02-27 14:25 ` Michael Powe
2022-03-20 6:31 ` Ihor Radchenko
2022-06-18 1:29 ` Ihor Radchenko
2022-06-18 9:51 ` Ihor Radchenko
2022-06-18 14:31 ` Bastien
2022-06-19 15:52 ` Richard Stallman
2022-06-20 0:13 ` briangpowell
2022-06-20 1:22 ` Ihor Radchenko
2022-06-20 2:11 ` briangpowell
2022-06-20 2:35 ` Ihor Radchenko
2022-06-27 3:43 ` Richard Stallman
2022-06-27 10:11 ` Ihor Radchenko
2022-06-28 3:25 ` Richard Stallman
2022-06-28 3:35 ` Vikas Rawal
2022-07-02 3:33 ` Richard Stallman
2022-07-02 16:23 ` Vikas Rawal
2022-07-04 3:39 ` Richard Stallman
2022-07-04 4:32 ` Timothy [this message]
2022-07-04 12:38 ` Ihor Radchenko
2022-07-04 17:48 ` Michael Powe
2022-07-06 2:50 ` Richard Stallman
2022-07-06 14:42 ` Hendursaga
2022-07-08 3:33 ` Richard Stallman
2022-07-08 4:32 ` Tim Cross
2022-07-08 4:48 ` tomas
2022-07-08 5:25 ` Dr. Arne Babenhauserheide
2022-07-11 3:16 ` Richard Stallman
2022-07-11 4:37 ` Dr. Arne Babenhauserheide
2022-06-28 7:02 ` Dr. Arne Babenhauserheide
2022-06-28 8:23 ` Tim Cross
2022-06-30 3:09 ` Richard Stallman
2022-06-30 18:21 ` Dr. Arne Babenhauserheide
2022-07-01 3:34 ` Richard Stallman
2022-07-01 3:53 ` Tim Cross
2022-07-01 17:54 ` Michael Powe
2022-07-01 18:42 ` Samuel Banya
2022-07-02 17:02 ` Jeremie Juste
2022-07-01 3:59 ` Ihor Radchenko
2022-07-02 3:32 ` Richard Stallman
2022-07-02 3:56 ` Ihor Radchenko
2022-07-02 7:52 ` Thomas Dye
2022-07-02 8:43 ` Ihor Radchenko
2022-07-02 16:45 ` Thomas S. Dye
2022-07-04 12:31 ` Ihor Radchenko
2022-07-05 3:01 ` Richard Stallman
2022-07-05 3:34 ` Tim Cross
2022-07-05 8:45 ` Dr. Arne Babenhauserheide
2022-07-06 2:52 ` Richard Stallman
2022-07-06 7:15 ` Dr. Arne Babenhauserheide
2022-07-07 7:25 ` Richard Stallman
2022-07-06 17:55 ` Thomas S. Dye
2022-07-07 9:53 ` Ihor Radchenko
2022-07-07 16:02 ` Thomas S. Dye
2022-06-27 22:42 ` Tom Gillespie
2022-06-27 23:42 ` Tim Cross
2022-06-28 1:46 ` Michael Powe
2022-06-28 1:54 ` Ihor Radchenko
2022-06-28 19:48 ` Michael Powe
2022-06-28 2:29 ` Ihor Radchenko
2022-07-03 23:31 ` Jean Louis
2022-07-04 0:11 ` Ihor Radchenko
2022-02-26 8:21 ` c.buhtz
2022-02-26 9:05 ` Bastien
2022-02-26 9:13 ` Communication problems and possible problems with the website Bastien
2022-02-25 14:26 ` Russell Adams
2022-02-26 8:58 ` Bastien
2022-02-26 15:16 ` Jean Louis
2022-02-27 6:56 ` Ihor Radchenko
2022-02-27 17:17 ` Bastien Guerry
2022-02-27 18:25 ` Tim Cross
2022-02-27 23:15 ` Timothy
2022-02-28 13:51 ` c.buhtz
2022-03-20 6:44 ` Ihor Radchenko
2022-02-27 17:10 ` Bastien
[not found] <621b1e76.1c69fb81.2121d.679b@mx.google.com>
2022-02-28 5:41 ` Links to javascript-based websites from orgmode.org: Paypal and Github Richard Stallman
2022-02-28 15:06 ` Michael Powe
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=87fsjhz7t0.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=bzg@gnu.org \
--cc=c.buhtz@posteo.jp \
--cc=emacs-orgmode@gnu.org \
--cc=rms@gnu.org \
--cc=vikasrawal@gmail.com \
--cc=yantar92@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/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).