From: HiPhish <hiphish@posteo.de>
To: Tonton <tonton@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Tue, 30 Oct 2018 01:38:42 +0100 [thread overview]
Message-ID: <8922916.CgCP4BZ6rP@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <20181030005454.0c3fe335@merlin.browniehive.net>
On Tuesday, 30 October 2018 00:54:54 CET you wrote:>
> You, me, Alex and the rest of Guix share a culture. I'm assuming that is the
> culture Alex refers to, not the cultures of our distinct offline locale.
What culture am I sharing with you? I am not a hacker, I only care about code
quality, just as only care about the plumbing of my toilet and not plumber
culture. I also care about software Freedom because I have been bitten in the
behind often enough by proprietary software to know that it is wrong. I care
about Guix because functional package management is the only sane way of
package management. What is the alternative to Guix? Flatpak and other opaque
systems suitable for bundling proprietary software?
> Also, the burden of proof really is with HiPhish. Harassment in tech, and
> FLOSS especially has been well documented. See for example:
> http://geekfeminism.wikia.com/wiki/FLOSS
> https://lwn.net/Articles/417952/
> https://www.theregister.co.uk/2017/06/05/open_source_developer_survey_2017/
> for a start.
I asked for proof, not "she said, he said". Except this is just "she said".
What if that "groping" as some guy brushing at her butt in a crowd by
accident? I have a really hard time believing that there is an epidemic of
serial gropers at tech conferences. Does that mean no one gets groped? Of
course not, even I had my butt slapped in the past by girls, but so what?
Here is a question for you: why are you taking these reports for granted? Do
you not consider the possibility that isolated issues are being blown out of
proportion by malicious agents? The incidents don't even have to be fake, the
offender might be a malicious agent as well. Free and Open Source projects are
a problem for proprietary software companies and any means to disrupt the
projects is acceptable. Why do you think the CC is so focused on punishment
and not healing?
next prev parent reply other threads:[~2018-10-30 0:38 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 11:58 Promoting the GNU Kind Communication Guidelines? HiPhish
2018-10-28 12:33 ` Gábor Boskovits
2018-10-28 16:14 ` Alex Griffin
2018-10-28 20:55 ` Thorsten Wilms
2018-10-29 11:27 ` Alex Sassmannshausen
2018-10-29 17:00 ` Thorsten Wilms
2018-10-29 17:50 ` Ricardo Wurmus
2018-10-29 23:54 ` OF-TOPIC: " Tonton
2018-10-29 11:29 ` Alex Sassmannshausen
2018-10-29 8:23 ` Björn Höfling
2018-10-29 10:10 ` Thorsten Wilms
2018-10-29 11:13 ` Alex Sassmannshausen
2018-10-29 17:15 ` Thorsten Wilms
2018-10-29 17:43 ` Ricardo Wurmus
2018-10-29 20:44 ` Björn Höfling
2018-10-29 11:08 ` Alex Sassmannshausen
2018-10-29 18:50 ` HiPhish
2018-10-29 23:54 ` Tonton
2018-10-30 0:38 ` HiPhish [this message]
2018-10-30 5:13 ` Nils Gillmann
2018-10-31 9:27 ` Alex Sassmannshausen
2018-10-31 12:29 ` HiPhish
2018-10-31 12:46 ` Alex Sassmannshausen
2018-10-31 13:23 ` HiPhish
2018-10-31 14:14 ` Jelle Licht
2018-10-31 14:55 ` HiPhish
2018-10-31 15:41 ` Stop it. Formerly - " Pjotr Prins
2018-10-31 17:51 ` Leo Famulari
2018-11-01 14:40 ` Ludovic Courtès
2018-11-01 15:11 ` Alex Griffin
2018-11-02 2:04 ` Mark H Weaver
2018-11-04 9:15 ` Mark H Weaver
2018-11-04 14:30 ` HiPhish
2018-11-04 21:01 ` Thorsten Wilms
2018-11-06 12:55 ` Ludovic Courtès
2018-11-06 17:23 ` Marius Bakke
2018-11-06 17:41 ` HiPhish
2018-10-31 12:30 ` HiPhish
2018-10-31 13:48 ` Jelle Licht
2018-10-31 14:55 ` HiPhish
2018-10-31 17:17 ` Thorsten Wilms
2018-11-01 10:35 ` Mark H Weaver
2018-10-31 13:48 ` Thomas Danckaert
2018-10-31 14:06 ` Alex Griffin
2018-10-31 14:55 ` HiPhish
2018-10-31 16:41 ` Thorsten Wilms
2018-11-01 2:58 ` Mark H Weaver
2018-11-01 9:14 ` Mark H Weaver
2018-11-01 8:40 ` Steffen Schulz
2018-10-29 11:37 ` Promoting the GNU Kind Communication Guidelines? (-> convivenza) Nils Gillmann
2018-10-29 11:45 ` Nils Gillmann
2018-10-29 12:01 ` Alex Sassmannshausen
2018-10-29 12:48 ` Promoting the GNU Kind Communication Guidelines? Giovanni Biscuolo
[not found] ` <9066320.aHiQMI0tiE@aleksandar-ixtreme-m5740>
2018-10-29 18:49 ` HiPhish
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 0:46 Alex Griffin
2018-10-30 2:09 ` Alex Griffin
2018-10-28 23:37 HiPhish
2018-10-23 11:15 Mathieu Lirzin
2018-10-23 13:38 ` Tobias Geerinckx-Rice
2018-10-23 14:39 ` Mathieu Lirzin
2018-10-24 1:06 ` Alex Griffin
2018-10-24 3:02 ` Jack Hill
2018-10-24 10:02 ` Ludovic Courtès
2018-10-24 14:21 ` Alex Griffin
2018-10-26 21:36 ` Tonton
2018-10-26 22:37 ` Alex Griffin
2018-10-28 18:42 ` Tonton
2018-10-28 19:50 ` Alex Griffin
2018-10-28 20:25 ` Alex Griffin
2018-10-28 21:12 ` Thorsten Wilms
2018-10-28 21:26 ` Alex Griffin
2018-10-29 8:59 ` Björn Höfling
2018-10-29 10:49 ` Thorsten Wilms
2018-10-29 13:43 ` Alex Griffin
2018-10-29 17:48 ` Christopher Lemmer Webber
2018-10-29 22:58 ` Tonton
2018-10-29 18:16 ` Cook, Malcolm
2018-10-24 10:23 ` Ludovic Courtès
2018-10-24 16:06 ` Mathieu Lirzin
2018-10-25 10:23 ` Ricardo Wurmus
2018-10-25 15:25 ` Mathieu Lirzin
2018-10-25 23:03 ` George Clemmer
2018-10-26 2:43 ` Gábor Boskovits
2018-10-26 21:25 ` Alex Griffin
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8922916.CgCP4BZ6rP@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=guix-devel@gnu.org \
--cc=tonton@riseup.net \
/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/guix.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).