unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Zacchaeus <zaccysc@gmail.com>
To: guix-devel@gnu.org
Subject: Contributing to Guix without rDNS
Date: Wed, 29 Jan 2025 17:29:36 -0800	[thread overview]
Message-ID: <87plk5ks1r.fsf@zacchae.us> (raw)

Hi Guix Devel,


I just found out that sending a patch to guix-patches@gnu.org (all
gnu.org emails) requires reverse DNS, which requires a static IP and
consent from an ISP.  I'm a digital nomad that self-hosts email on
devices strewn accross the US, so obtaining a static IP is not feasable
for me (I don't have accounts with any ISPs).  I'm a little disappointed
that gnu.org wants me te centralize my email, the OG decentralized
protocol: even Google doesn't block my email.  Since gnu.org blocks my
emails, I cannot send my patches to improve Guix.

Is there some way I can contribute to Guix without a static IP address,
or using some centralized gatekeeper?


-Zacchae


PS. Yes, I dug up my Google credentials to send this email.  No I will
not use that as a long-term solution.  It is rediculous that I need
Google to even get in contact with a GNU project.


             reply	other threads:[~2025-01-30  1:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30  1:29 Zacchaeus [this message]
2025-01-30  3:51 ` Contributing to Guix without rDNS Brennan Vincent
2025-01-30 20:39   ` Zacchaeus
2025-01-30 21:32     ` Brennan Vincent
2025-01-31  5:58       ` Vivien Kraus
2025-01-31 16:37         ` Brennan Vincent
2025-01-30 22:03     ` Ricardo Wurmus
2025-01-31  0:37       ` Zacchaeus Scheffer
2025-01-30  6:53 ` Ricardo Wurmus
2025-01-30 19:00   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
  -- strict thread matches above, loose matches on Subject: below --
2025-01-30 22:13 Zacchaeus

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=87plk5ks1r.fsf@zacchae.us \
    --to=zaccysc@gmail.com \
    --cc=guix-devel@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.
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).