Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Apr 2023 10:51:41 +0200
From:      Yuri <yuri@aetern.org>
To:        questions@freebsd.org
Subject:   Re: Postmaster Team responsibilities (was: How do I get a new freebsd- mailing list made)
Message-ID:  <b87fb47c-a1c8-dd6e-d791-22d0d78686fc@aetern.org>
In-Reply-To: <F2EE7776-85B6-4248-9C0A-05D6CAB093C0@nimnet.asn.au>
References:  <CAGBxaXkn=eG%2BozQAqt6Vi2zw37gva9JHdXYjFNMyg94_vXoM6g@mail.gmail.com> <cdae89a0-3070-1637-1166-371e776d06ee@freebsd.org> <F0D85CD2-3E1D-4F65-B707-61AA6FF24CB2@nimnet.asn.au> <4dddf05c-4c8b-770c-31e2-2321774aea9a@freebsd.org> <F2EE7776-85B6-4248-9C0A-05D6CAB093C0@nimnet.asn.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Ian Smith wrote:
> On 23 April 2023 5:04:32 am AEST, Graham Perrin <grahamperrin@freebsd.org> wrote:
>  > On 22/04/2023 18:48, Ian Smith wrote:
>  > > In the olden days, one would email postmaster@freebsd.org for
>  > advice.
>  > 
>  > For reference: /Postmaster Team/ responsibilities are at 
>  > <https://www.freebsd.org/administration/#t-postmaster>.
>  > 
>  > Gut feeling (without me asking the Team): it probably makes sense to
>  > be 
>  > certain of the requirement for a new list, before seeking advice from
>  > the Team. To minimise to-ing and fro-ing.
> 
> Oh, certainly.  So far I've seen two people discuss the possibility, which seems too few to yet be considered a groundswell ...

+1, we have too many lists already as it is, and there need to be real
reason to have yet another one.

Looking at "Installing openAI's GPT-2 Ada AI Language Model" thread, it
could very well be just on questions/ports (not so sure about hackers),
and certainly does not require a separate list.


>  > HTH
>  > 
>  > postmaster@ if any of you are reading, please correct me if I'm wrong
>  > :-)
> 
> Again old-fashioned, I've used another traditional trick (a cc) to make sure :-)
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b87fb47c-a1c8-dd6e-d791-22d0d78686fc>