public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: rms@gnu.org, David Edelsohn <dje.gcc@gmail.com>,
	gnutools-advocacy@gcc.gnu.org
Subject: Re: GNU Toolchain web site mock-up
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <ormurm1kn1.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAE2sS1jjDmCiqZdwckn=vj-yR25WDAZx-z6+cV-JDUjjO9RaNQ@mail.gmail.com> (Carlos O'Donell's message of "Tue, 9 Oct 2018 10:01:19 -0400")

On Oct  9, 2018, "Carlos O'Donell" <carlos@systemhalted.org> wrote:

> Any drafts in HTML with code will be reviewable by Alex.

But that would require people to post it somewhere I could get to.
Either Google Dox would end up being no different from using any local
office tool, which means Google Dox would be used privately only, so
that there's no point in advertising its use, or I'd be at a
disadvantage position for needing these additional steps to collaborate,
while some others would be collaborating directly through the
proprietary software and SaaSS web service.

The inadequate format and
tooling for distributed and decentralized collaboration would create
even worse issues than those I've experienced occasionally, trying to
contribute to projects that unfortunately adopted Github and insist
contributors to set up an account and submit Github pull requests,
rather than patches/patchesets or traditional git pull requests.
Neither setting up an account nor creating pull requests is possible
without running non-Free Software provided by Github, so...  you see
where this is going.

Either way, with Github or an office suite, I don't quite quite see how
I'd propose patches, and how they'd be integrated.  Being one of the
members of this advocacy project from the very beginning (when it turned
from dje's individual initiative to a groupo effort), I don't wish to be
left out, or placed at a disadvantage, when there are tools we could use
to collaborate to promote GNU, that are a lot more aligned with GNU.


Now, I see I had misunderstood the intended use of the proposed tools.
When Google Dox was mentioned, I thought of plans in text form, not of
web sites proper.  I have never used Google Dox, but the idea of
designing a web site on it comes across as quite alien to me.

Anyway, if at this point the idea is to propose web site designs, to be
later implemented using some proper Free Software tools, I guess I need
not even participate.  I don't have much perception to looks, what I
intended to cotribute to the project was written material
(e.g. articles).  However, there are other GNU contributors who may wish
to contribute to the design of the sites' looks, and we don't want to
exclude them from participating by requiring the use of proprietary
tools, so I'd still appreciate clarification as to the extent of the
intended use of the so far suggested proprietary tools and SaaSS sites,
and make sure that we won't stop or make it difficult for anyone to
participate by selecting inadequate tools for GNU.

-- 
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

  reply	other threads:[~2018-10-10  4:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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     ` Richard Stallman
2018-01-01  0:00       ` Carlos O'Donell
2018-01-01  0:00         ` Alexandre Oliva [this message]
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00           ` Richard Stallman
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=ormurm1kn1.fsf@lxoliva.fsfla.org \
    --to=lxoliva@fsfla.org \
    --cc=carlos@systemhalted.org \
    --cc=dje.gcc@gmail.com \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --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).