This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Close down glibc-sc mailing list.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>, Mark Brown <ms_brown at sbcglobal dot net>, libc-alpha at sourceware dot org, "Joseph S. Myers" <joseph at codesourcery dot com>, Roland McGrath <roland at hack dot frob dot com>, "Ryan S. Arnold" <ryan dot arnold at linaro dot org>, Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>, Alexandre Oliva <aoliva at redhat dot com>, Jakub Jelinek <jakub at redhat dot com>, Andreas Schwab <schwab at suse dot de>
- Date: Wed, 20 Jan 2016 15:10:09 -0500
- Subject: Re: Close down glibc-sc mailing list.
- Authentication-results: sourceware.org; auth=none
- References: <E1aLIs3-00021d-VR at fencepost dot gnu dot org> <569D7328 dot 5030502 at sbcglobal dot net> <569E9328 dot 2000403 at redhat dot com> <569EC10E dot 2010600 at sbcglobal dot net> <569ECAA2 dot 2050405 at cs dot ucla dot edu> <569F1078 dot 6010201 at redhat dot com> <20160120055813 dot GQ14840 at vapier dot lan>
On 01/20/2016 12:58 AM, Mike Frysinger wrote:
> On 19 Jan 2016 23:43, Carlos O'Donell wrote:
>> On 01/19/2016 06:45 PM, Paul Eggert wrote:
>>> On 01/19/2016 03:04 PM, Mark Brown wrote:
>>>> I think that there are some preparatory, diplomatic steps that
>>>> would need to be taken first.
>>>
>>> I agree. Although I don't see the need to devote a list to informal
>>> back-channel communication (I already get too much email like that as
>>> it is and I'm sure you do too...), there are occasions where such
>>> communication can be helpful. Perhaps we can suggest that FSF
>>> leadership simply contact us privately as needed if there's something
>>> that calls out for privacy. If they don't know offhand which of us
>>> would be best to contact about a particular matter, I suppose they
>>> can just contact (sigh) me.
>>
>> They should contact *anyone* who is a steward for the glibc project
>> (GNU project maintainer). Such a person will know how to reach
>> everyone else.
>
> what if we make the main contact point part of the current release
> manager's duties ? e.g. Adhemerval Zanella is managing glibc 2.23,
> so he would be the contact, but as soon as the manager is picked for
> the 2.24 cycle, it'll pass on to that dev ? i suspect it won't add
> anything for the most part, and most people wouldn't see any at all.
While the release managers are very responsible people I don't want to
make them secretaries to the responsible GNU maintainers. Several of us
have accepted the responsibility of the glibc project as part of the GNU
project. We should be dealing with anything that comes down the pipe :-)
Cheers,
Carlos.