From: Juliusz Chroboczek <jch@irif.fr>
To: "MeshPoint / Valent Turkovic" <valent@meshpointone.com>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: [RFC] Contributing guidelines[RFC] Contributing guidelines
Date: Sun, 01 Nov 2026 15:18:03 +0100 [thread overview]
Message-ID: <871p948wkk.wl-jch@irif.fr> (raw)
In-Reply-To: <emba8b35c0-114e-4d6f-8350-d3511515093f@meshpointone.com>
> I’m not suggesting these are the rules; I’m simply proposing a framework
> to start a discussion about a contribution guideline.
Valent, you have published an authoritative-sounding document that
contains a number of incorrect statements. You did not include
a disclaimer. Since this list is being archived, this document will
appear in web searches, and induce potential contributors in error.
Here's a few examples. You say
> Contributions that expose private user data, such as IP addresses or
> user names, will not be accepted.
That's formulated in a very categorical manner. Please see commit
a76f225b (the /identify command), which exposes IP addresses. This
protocol extension was carefully designed to balance the needs of users
(who want their privacy respected) and the needs of moderators (who want
to be able to ban an IP address that's being used for abuse). (The
original proposal was to log all IP addresses, which I rejected for
privacy reasons. We then had a bunch of back-and-forth discussion, which
lead to the /identify command.)
> Anything that requires an external daemon (e.g. an SQL server) is out
> of the question.
Again, that's formulated in a very categorical manner (was it written by
an LLM?). It is plainly incorrect. There are features in Galene that
require an external server (galene-ldap, galene-sip). A more correct
statement would that it must remain possible to make a simple deployment
of Galene without relying on external servers. (And even that is not
quite correct: you need working DNS and an X.509 provider.)
> - Use a dedicated branch for each pull request, based on current master.
That's rather patronising: it implies that we're entitled to tell people
how to organise their work in their private repository. As long as people
send usable pull requests or patches, we have no right to tell them what
to do in the privacy of their local repository.
I could go on, but I think you get the point. Valent, please do not
publish further authoritative-sounding lists without including a clear
disclaimer.
-- Juliusz
prev parent reply other threads:[~2026-11-01 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 15:11 [Galene] [RFC] Contributing guidelines[RFC] Contributing guidelines Valent@MeshPoint
2026-10-31 15:29 ` [Galene] " Juliusz Chroboczek
2026-10-31 22:40 ` MeshPoint / Valent Turkovic
2026-11-01 14:18 ` Juliusz Chroboczek [this message]
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871p948wkk.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=valent@meshpointone.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