From: Ihor Radchenko <yantar92@posteo.net>
To: Jean Louis <bugs@gnu.support>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org, rms@gnu.org
Subject: Re: Best android app
Date: Mon, 17 Oct 2022 12:06:28 +0000 [thread overview]
Message-ID: <87pmeqpscb.fsf@localhost> (raw)
In-Reply-To: <Y009r5e2sfDMMtNr@protected.localdomain>
Jean Louis <bugs@gnu.support> writes:
> Yes, it is common sense that in GNU project we do not steer users
> towards proprietary systems.
>
> This means that in GNU software, mailing lists and chat, and websites,
> we do not point to proprietary systems as non-free programs are
> injustice, and we shall not bring users to position to give up their
> freedom.
>
> Applying the Free Software Criteria - GNU Project - Free Software Foundation:
> https://www.gnu.org/philosophy/applying-free-sw-criteria.en.html
>
> People are free to discuss anything, but as it is GNU project, those
> who are aware may ask and wonder why is proprietary software endorsed
> or referenced on GNU mailing lists.
I am mostly using https://www.gnu.org/prep/standards/standards.html as a
reference here:
>> You should not refer to AT&T’s web site if that recommends AT&T’s
>> non-free software packages; you should not refer to a page p that
>> links to AT&T’s site presenting it as a place to get some non-free
>> program, because that part of the page p itself recommends and
>> legitimizes the non-free program.
>>
>> However, if p contains a link to AT&T’s web site for some other
>> purpose (such as long-distance telephone service), that is no reason
>> you should not link to p.
So, we may link to non-free software, but only for the purposes other
than encouraging to use it. This is a tricky distinction to master
though. In your interpretation that we are going to promote using that
non-free software, you are right. But I viewed the discussion
differently. [The reality is probably that it was too early to conclude
about where the discussion will go; and it deviated towards FSF
philosophy :) ]
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-10-17 12:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 18:31 Best android app ypuntot
2022-10-15 23:01 ` Juan Manuel Macías
2022-10-16 0:57 ` Ypo
2022-10-17 18:01 ` Max Nikulin
2022-10-17 18:33 ` Juan Manuel Macías
2022-10-16 5:26 ` Max Nikulin
2022-10-16 7:32 ` Jean Louis
2022-10-16 9:22 ` Ihor Radchenko
2022-10-16 12:13 ` Juan Manuel Macías
2022-10-16 12:32 ` Ihor Radchenko
2022-10-16 13:14 ` Juan Manuel Macías
2022-10-16 15:02 ` Ihor Radchenko
2022-10-16 19:30 ` Juan Manuel Macías
2022-10-17 11:37 ` Jean Louis
2022-10-17 12:53 ` Ihor Radchenko
2022-10-17 13:22 ` Jean Louis
2022-10-17 11:36 ` Jean Louis
2022-10-17 11:56 ` Ihor Radchenko
2022-10-17 13:24 ` Jean Louis
2022-10-17 11:34 ` Jean Louis
2022-10-17 12:06 ` Ihor Radchenko [this message]
2022-10-17 13:32 ` Jean Louis
2022-10-16 16:07 ` Max Nikulin
2022-10-17 11:54 ` Jean Louis
2022-10-17 13:18 ` Ihor Radchenko
2022-10-17 13:38 ` Jean Louis
2022-10-19 12:49 ` Max Nikulin
2022-10-19 23:46 ` Jean Louis
2022-10-25 16:56 ` Max Nikulin
2022-10-23 4:39 ` Ihor Radchenko
2022-10-23 15:27 ` Ypo
2022-10-24 9:24 ` Ihor Radchenko
2022-10-25 16:17 ` Max Nikulin
2022-10-24 11:32 ` Jean Louis
2022-10-25 7:31 ` GPL violation related to Org by priprietary app (was: Best android app) Ihor Radchenko
2022-10-25 10:24 ` Jean Louis
2022-10-25 11:20 ` Ihor Radchenko
2022-10-25 13:12 ` Tim Cross
2022-10-25 13:45 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2022-10-14 18:16 Best android app Renato Pontefice
2022-10-14 18:30 ` Jude DaShiell
2022-10-14 18:37 ` Renato Pontefice
2022-10-14 18:52 ` Juan Manuel Macías
2022-10-14 19:08 ` Jean Louis
2022-10-15 1:16 ` 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=87pmeqpscb.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=rms@gnu.org \
/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).