From: Greg Troxel <gdt@ir.bbn.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode@gnu.org, Neven <neven@orgzly.com>
Subject: Re: [ANN] [OT] New Android app (Orgzly)
Date: Fri, 23 Jan 2015 14:18:56 -0500 [thread overview]
Message-ID: <rmiegqlxq3j.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87a91aiie1.fsf@wmi.amu.edu.pl> (Marcin Borkowski's message of "Thu, 22 Jan 2015 23:02:14 +0100")
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> On 2015-01-22, at 17:41, Jose E. Marchesi <jemarch@gnu.org> wrote:
>
>> *NOTE* It's about an app which is *not* open source (some parts of code
>> will opened, see below). If you have a problem with that, you can stop
>> reading right about now...
>>
>> Please stop using the GNU mailing lists to promote proprietary software.
>
> It might be the case that I do not understand something.
>
> AFAIR, there was a recent discussion on another GNU mailing list about
> usability of Emacs under Windows. (Maybe it was somewhere else, I'm not
> sure, then my question is theoretical.) A few people claimed that Emacs
> under Windows is fully functional and works well. Would this also be
> considered "promoting proprietary software"?
The point here is that the FSF is a charitable nonprofit which promotes
free software. Their servers have usage guidelines:
https://savannah.gnu.org/register/requirements.php
Basically, helping Free software to work on non-Free operating systems
is ok, as long as the non-Free OS is not the proprietary target and the
software works best (or equal) on Free systems. Supporting or
advertising non-Free software is not ok.
So the opinions of our hosts are pretty clear.
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2015-01-23 19:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:33 [ANN] [OT] New Android app (Orgzly) Neven
2015-01-22 15:58 ` Xebar Saram
2015-01-22 16:02 ` Rasmus
2015-01-22 20:00 ` Neven
2015-01-22 21:05 ` Melleus
2015-01-22 21:20 ` Neven
2015-01-23 8:47 ` e.fraga
2015-01-22 16:41 ` Jose E. Marchesi
2015-01-22 16:57 ` Scott Randby
2015-01-22 22:02 ` Marcin Borkowski
2015-01-22 22:46 ` Rasmus
2015-01-24 0:05 ` Marcin Borkowski
2015-01-23 4:13 ` Scott Randby
2015-01-23 8:53 ` Rainer M Krug
2015-01-23 13:31 ` Scott Randby
2015-01-23 23:57 ` John Hendy
2015-01-23 19:18 ` Greg Troxel [this message]
2015-01-23 19:21 ` Greg Troxel
2015-01-23 23:57 ` Discussion of non-free-as-defined-by-FSF software (was: [ANN] [OT] New Android app (Orgzly)) Marcin Borkowski
2015-01-23 9:56 ` [ANN] [OT] New Android app (Orgzly) Karl Voit
2015-01-24 0:10 ` Marcin Borkowski
2015-01-22 21:23 ` Subhan Michael Tindall
2015-01-23 2:59 ` Mike McLean
2015-01-24 0:15 ` Marcin Borkowski
2015-01-23 4:34 ` Samuel Wales
2016-10-20 19:28 ` Thomas Koch
2016-10-22 2:46 ` Stefan Huchler
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=rmiegqlxq3j.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
--cc=neven@orgzly.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).