unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
	"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: conflicts in the gnu project now affect guile
Date: Fri, 18 Oct 2019 17:09:24 +0200	[thread overview]
Message-ID: <20191018150924.ykbltmpf3xq6fxzh@pelzflorian.localdomain> (raw)
In-Reply-To: <iWWr0xw0OtkfNm7AE4d71ft1VIEa0tVv_FPB2N5whheKQqe2y3cS320Kf_nzIB9hbzH5-DNCgvVV0v366rMlKN1F8JPCaRcxtk17Wr6k_-0=@protonmail.com>

On Fri, Oct 18, 2019 at 11:29:35AM +0000, Todor Kondić wrote:
> You know, there is a big IT department within our institution and telling them I will base some serious work on technologies such as GNU  Guile and Guix did raise a few eyebrows (those not raised are probably the cause of their proprietors not being informed enough).
> 
> […]
> Couple of notes:
> 
> 1) Are there any ladies on these lists? I am *dying* to hear from them
> 2) Related to (1) ... a brief look at the maintainers who signed the Joined Statement gives an impression that it leans heavily to the politically Western hemisphere; just a comment, maybe food for thought
> 3) The RMS scandal was brought to my attention by a female coder colleague who previously knew nothing of RMS's, or FSF's or GNU's work in the "Open Source Community"; another nibble for thought
>


There have been few contributions from women,
e.g. <https://lists.gnu.org/archive/html/guile-devel/2017-03/msg00042.html>
(I do not know what its status is), but I believe bringing GNU Guile
to professional use could help diversify.  Thank you for that!

Regards,
Florian



  reply	other threads:[~2019-10-18 15:09 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 11:29 conflicts in the gnu project now affect guile Todor Kondić
2019-10-18 15:09 ` pelzflorian (Florian Pelz) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-18 11:45 Mark H Weaver
2019-10-16 13:14 Andy Wingo
2019-10-16 14:11 ` Thompson, David
2019-10-16 15:33   ` Christopher Lemmer Webber
2019-10-16 16:10     ` Eli Zaretskii
2019-10-19 17:05       ` Mark H Weaver
2019-10-16 18:27     ` Jean Louis
2019-10-16 18:27   ` Jean Louis
2019-10-16 19:30   ` pelzflorian (Florian Pelz)
2019-10-18  9:44     ` Alex Sassmannshausen
2019-10-16 18:12 ` Jean Louis
2019-10-16 21:56   ` Tadeus Prastowo
2019-10-16 22:05     ` Adrienne G. Thompson
2019-10-18  3:16       ` Richard Stallman
2019-10-18  3:17     ` Richard Stallman
2019-10-18 10:37       ` Tadeus Prastowo
2019-10-16 19:21 ` Mikael Djurfeldt
2019-10-16 21:03 ` Linus Björnstam
2019-10-17  0:18 ` Arne Babenhauserheide
2019-10-17  1:24 ` Mark H Weaver
2019-10-17  7:07   ` Jan Nieuwenhuizen
2019-10-18  7:24     ` Mark H Weaver
2019-10-18 11:20     ` Christopher Lemmer Webber
2019-10-18 13:14       ` Mark H Weaver
2019-10-18 13:33         ` Christopher Lemmer Webber
2019-10-18 13:49           ` Thompson, David
2019-10-17  1:40 ` Mike Gran
2019-10-17  2:11 ` Neil Van Dyke
2019-10-17 18:11 ` Mikhail Kryshen
2019-10-18  9:26   ` Alex Sassmannshausen
2019-10-19  4:03     ` Mikhail Kryshen
2019-10-18  1:06 ` Mark H Weaver
2019-10-18  6:31   ` Nala Ginrut
2019-10-18  9:20   ` Mikael Djurfeldt
2019-10-18 14:22   ` Ludovic Courtès
2019-10-19 22:55 ` Taylan Kammer
2019-10-20  3:08   ` Mark H Weaver
2019-10-20  3:54     ` Nala Ginrut
2019-10-20 19:12     ` Taylan Kammer

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.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191018150924.ykbltmpf3xq6fxzh@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=tk.code@protonmail.com \
    /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).