From: Alexandre Oliva <lxoliva@fsfla.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gnutools-advocacy@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
"Richard M. Stallman" <rms@gnu.org>,
"Carlos O'Donell" <carlos@systemhalted.org>,
iains.gcc@gmail.com
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <ork1mvmjsv.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <95559138-7960-4694-A85F-E13D4E2FC218@gmail.com> (Richard Biener's message of "Sat, 06 Oct 2018 11:44:18 +0200")
On Oct 6, 2018, Richard Biener <richard.guenther@gmail.com> wrote:
> Btw, I didn't see you suggesting a concrete alternative
I didn't, indeed. I somehow got the idea that Carlos found Free
Software alternatives lacking, which would put his knowledge ahead of my
own. But that seems to have been my imagination, for I don't see any
evidence of that.
I'm not a big fan of office suites myself, and when I absolutely must
use one, I use LibreOffice, but I read there's LibreOffice Online.
https://www.libreoffice.org/download/libreoffice-online/
https://wiki.documentfoundation.org/Development/LibreOffice_Online
https://www.collaboraoffice.com/code/
I seem to recall it could be installed more or less easily (maybe by
default?) as part of ownCloud and/or NextCloud.
I don't know of anyone who offers it as SaaSS, but then, using it in
such a setting would make it only little better than Google dox.
The Free Software Way to use it would be to install our own instance on
our own server.
--
Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo
Be the change, be Free! FSF Latin America board member
GNU Toolchain Engineer Free Software Evangelist
next prev parent reply other threads:[~2018-10-06 10:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Iain Sandoe
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva [this message]
2018-01-01 0:00 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ork1mvmjsv.fsf@lxoliva.fsfla.org \
--to=lxoliva@fsfla.org \
--cc=carlos@systemhalted.org \
--cc=dje.gcc@gmail.com \
--cc=gnutools-advocacy@gcc.gnu.org \
--cc=iains.gcc@gmail.com \
--cc=richard.guenther@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.
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).