From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: emacs-orgmode@gnu.org
Subject: Re: BeOrg
Date: Wed, 03 Jan 2018 17:58:11 -0200 [thread overview]
Message-ID: <87fu7msoj0.fsf@hyperbola.info> (raw)
In-Reply-To: <87zi5v8i1s.fsf@gmail.com> (Tim Cross's message of "Wed, 03 Jan 2018 19:26:07 +1100")
Morever, considering the availability only in Apple's App Store, how
will users exercise freedom 1, which also includes the freedom to reuse
the adaptation in the same environment/device? This "retake' of freedom
0 in freedom 1 is also mentioned in [1].
Currently:
- BeOrg doesn't seem to be "open source" (according to the Open Source
Initiative's Definition, see [2]), unless of course we're missing
something and the full license text, copyright notice, license notice
and complete corresponding source are referenced/mentioned or
distributed when the app is used, which I see as unlikely;
- doesn't seem to be free/libre either, because it depends on a package
manager which has no easy way to completely manage trusted signatures
understood by such package manager and requires installation only of
signed packages (this last requirement isn't bad, but the absense of
the trust management feature makes it worse). This is somewhat
analogous to the situation found in almost all manufacturer-provided
smartphones with Android and bootloaders preinstalled, besides this,
iThings also come with Restricted Boot (not to be confused with Secure
Boot or with EFI/UEFI, for the differences see [3]).
[1] <http://dcc.ufmg.br/~lcerf/rms.webm>. First audio track has original
speech in English, second one has translation in Brazilian
Portuguese. However this nete is only accurate for the speech, because
the intermediate audio language is somewhat mixed.
[2] <https://opensource.org/osd>.
[3] <https://media.libreplanet.org/u/libby/m/embracing-secure-boot-and-rejecting-restricted-boot-matthew-garrett/>.
2018-01-03T19:26:07+1100 Tim Cross wrote:
> Bottom line is that referencing this software in the org manual would
> contravene the GNU guidelines and underlying philosophy of the
> GPL. While you will find references to non-GPL software/platforms, these
> are not references which promote non-free solutions, but references in
> support of adopting free solutions on non-free platforms.
>
> One of the biggest threats to software freedom and a significant issue
> for the FSF is the attractive lure of convenience. I feel it would be a
> mistake to ignore the guidelines in favour of promoting a non-free
> solution on the basis it would be beneficial to users. The FSF and GPL
> are built on a clear philosophy of supporting and promoting software
> freedom and to sacrifice those principals because there is only a
> non-free solution to satisfy a need is short sighted and
> contradictory.
>
> It appears the software is actually free to download and has an 'in app'
> donation request. It also appears the software makes extensive use of
> other 3rd party libraries. This makes me wonder if it would be
> reasonable to contact the author and ask if they would be prepared to
> change the license to an acceptable open source one. This would not
> prevent them from continuing to request donations and would then enable
> Org to reference the software on the org site and in the manual, which
> would in turn likely increase app visibility and lead to more donations
> to the author. This could be a win for everyone, including the author.
>
> Of course, the other question to ask is "If beorg is so much better than
> available open source equivalents, such as mobileOrg, how has one
> individual been able to do that when the org community cannot?"
>
> Tim
>
> Ilya Shlyakhter <ilya_shl@alum.mit.edu> writes:
>
>> The org features page at https://orgmode.org/features.html, and the
>> Org manual, mention MobileOrg, but not the newer BeOrg app
>> ( http://beorgapp.com/ ). Maybe add a reference to it?
>
>
> --
> Tim Cross
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
next prev parent reply other threads:[~2018-01-03 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 17:32 BeOrg Ilya Shlyakhter
2018-01-02 17:39 ` BeOrg Eric S Fraga
2018-01-02 17:52 ` BeOrg ilya shlyakhter
2018-01-02 19:20 ` BeOrg Nicolas Goaziou
2018-01-02 19:48 ` BeOrg Ilya Shlyakhter
2018-01-02 20:43 ` BeOrg Nicolas Goaziou
2018-01-02 22:17 ` BeOrg Peter Davis
2018-01-03 0:30 ` BeOrg Thomas S. Dye
2018-01-03 2:06 ` BeOrg Ian Dunn
2018-01-03 2:43 ` BeOrg Ilya Shlyakhter
2018-01-03 5:00 ` BeOrg Scott Randby
2018-01-03 20:00 ` BeOrg Adonay Felipe Nogueira
2018-01-03 8:26 ` BeOrg Tim Cross
2018-01-03 19:58 ` Adonay Felipe Nogueira [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-05 2:08 BeOrg edgar
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=87fu7msoj0.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=emacs-orgmode@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).