Not all Aegir users are capitalists that will sell sites. ;) Some will be community organisations that will certainly need the concept of "groups" without them being "clients".

So I propose that we rename clients to groups. We don't need to do it in the code and DB, but at least in the user interface.

Comments

omega8cc’s picture

omega8cc commented

Hmm.. then make it configurable and leave "client" by default.

E-mail 'client' is a software, not a "client of capitalist" and server-client is not about capitalism as well, yet, it works :)

anarcat’s picture

anarcat commented

(I didn't mean to start a politico-economical debate here.)

email "client" makes sense because there is a "client" allegory.

In aegir, I believe the "group" allegory is better.

I do agree we should make it configurable anyways.

omega8cc’s picture

omega8cc commented

If this will be configurable and not default, then it is fine, but I really believe that the "group" in this context is a too generic name - I think it will confuse people and they will keep asking what this "group" is about, while the "client" name is rather self-explaining. The "Add client" action has rather obvious(?) meaning, while "Add group" implies questions like: "the group of what or who?" etc.

steven jones’s picture

steven jones commented
Title: rename "clients" to "groups", at least in the frontend » Make the name of 'clients' configurable
Status: Active » Postponed (maintainer needs more info)

Awaiting a frontend to get this working in.

helmo’s picture

helmo commented
Version: 7.x-2.x-dev » 7.x-3.x-dev

Moving to 7.x-3.x version tag (7.x-2.x never existed, we went for 6.x-2.x).

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

If we #2049623: Refactor hosting_clients to use Organic Groups, we'll get this ability for free.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Issue summary: View changes

forgot a word there