From: Juliusz Chroboczek <jch@irif.fr>
To: Alexander Dietrich <alexander@dietrich.cx>
Cc: Galene Mailing List <galene@lists.galene.org>
Subject: [Galene] Re: Thoughts on global user passwords
Date: Mon, 28 Sep 2026 00:13:56 +0200 [thread overview]
Message-ID: <87ld8m8hqz.wl-jch@irif.fr> (raw)
In-Reply-To: <1248415078.226067.1790518697463@app.mailbox.org>
> My initial thought was to support global passwords only, and leave
> permissions in the group description. So the user would be "op" in
> "teaching", plus whatever is necessary for the subgroups?
The point is that we need something that's easy to explain and easy to
export in the REST-like API. Early versions of Galene had a richer
permissions model, but I found that it was impossible to map sensibly to
a REST-like structure.
-- Juliusz
prev parent reply other threads:[~2026-09-27 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <179043064484.1076.1779405941341360418@gauss>
2026-09-26 16:05 ` [Galene] Re: Thoughts on global user passwords Juliusz Chroboczek
2026-09-27 14:18 ` Alexander Dietrich
2026-09-27 22:13 ` 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=87ld8m8hqz.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=alexander@dietrich.cx \
--cc=galene@lists.galene.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