From: "Rémi Nollet" <nollet@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Re: Is the passwd file still needed?
Date: Sat, 20 Feb 2021 11:06:43 +0100 [thread overview]
Message-ID: <8a97fcc6-a435-1fc4-7be2-707a65dd3290@irif.fr> (raw)
In-Reply-To: <87sg5r5zml.wl-jch@irif.fr>
I feel permitted to a bit of bike-shedding.
If the user groups you want to create have the same semantics as Unix
groups, and if this is the right semantics to use, I would also go for
naming them “groups” and finding something else for current “groups”. I
feel like it would help the administrators to make correct quick guesses
so as to how those user groups work.
If you then need a replacement name for current “groups”, I also happen
to like “room”. For the end-user, they are nothing but a rendezvous
point, a location in which we can meet and talk to and see each other.
But if rooms are not the usual places where we meet people we want to
talk with, maybe we can try something like “bar”, “pub”, “table”? Not
sure what impression it will give to the user though. :-)
Also, I for one like real-life metaphors. They make easier to remember
names and to build a mental model. At least for me.
-- Rémi
next prev parent reply other threads:[~2021-02-20 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 9:52 [Galene] " Toke Høiland-Jørgensen
2021-02-19 10:44 ` [Galene] " Michael Ströder
2021-02-19 11:48 ` Toke Høiland-Jørgensen
2021-02-19 12:47 ` Juliusz Chroboczek
2021-02-19 13:01 ` Toke Høiland-Jørgensen
2021-02-19 13:13 ` Juliusz Chroboczek
2021-02-19 13:19 ` Gabriel Kerneis
2021-02-19 13:36 ` Toke Høiland-Jørgensen
2021-02-20 0:52 ` Juliusz Chroboczek
2021-02-20 10:06 ` Rémi Nollet [this message]
2021-02-20 11:49 ` Toke Høiland-Jørgensen
2021-02-20 12:09 ` Michael Ströder
2021-02-20 12:22 ` Toke Høiland-Jørgensen
2021-02-23 15:11 ` Dave Taht
[not found] ` <YDAEso0xTvoIg+hJ@local>
2021-02-20 12:23 ` Toke Høiland-Jørgensen
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=8a97fcc6-a435-1fc4-7be2-707a65dd3290@irif.fr \
--to=nollet@irif.fr \
--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