From: Alexandre Oliva <lxoliva@fsfla.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
gnutools-advocacy@gcc.gnu.org,
"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: <ory3bbkvgl.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAGWvnyk4Lh1bFfytHsJkDwOO-7Mmk=TSc-Q9dH-Qopowyu_sfQ@mail.gmail.com> (David Edelsohn's message of "Sat, 6 Oct 2018 09:57:34 -0400")
On Oct 6, 2018, David Edelsohn <dje.gcc@gmail.com> wrote:
>> The discussion was about what tools to use within this sub-sub-project..
> No. That's not the discussion.
Let me quote the discussion that I joined to. Tell me what you think
is being discussed:
I need to find a host for this site, maybe sourceware.org.
Then I need to see what kind of server side tech we can use for this,
like will we be able to use django on sourceware for this new website?
So if I had to take a first step it would be to create a Google doc
with a project plan for (1) and the pages we need to create for that.
Here's an initial attempt at a placeholder for the website hosted
through Github pages and built using Bootstrap.
I had just been invited to join the list, after having expressed
interest in participating in a GNU advocacy group.
The least I'd expect is for the group to operate within GNU guidelines.
So, that's where speaking for GNU kicks in.
But you're right, there's also a personal issue about it.
I don't use proprietary software. The choices that divert from GNU
happen to also rule out my participation.
Now, it is evident to me that the decisions about what tools to use have
NOT been made. There hasn't been agreement. Ideas were put forth, but
no agreement has been made. And hopefully no agreement will be made
that makes it impossible for me to collaborate. I and others who take
GNU seriously won't feel welcome that way.
> Please do not insert yourself into another group of self-organizing
> advocates and start ordering them around about what they should do and
> how they should do it.
Sorry to say, but you're the only one ordering people around.
I'm just trying to take part in the project. Like I said I wanted to.
Like I was invited to. Like I agreed to.
Hijacking GNU subprojects is not nice. Please don't do that. I've
asked you nicely four times.
If you want to promote GNU, or parts thereof, please do so without
defating its main purpose. Doing otherwise is rude. It's arrogant.
It's offensive. It's not helpful. It's harmful to the entire project.
Please stop.
--
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 14:21 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 ` Richard Biener
2018-01-01 0:00 ` David Edelsohn
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 ` 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 ` 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 ` 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 [this message]
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
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=ory3bbkvgl.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).