From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward502b.mail.yandex.net (forward502b.mail.yandex.net [178.154.239.146]) by sourceware.org (Postfix) with ESMTPS id 5B1163858D38 for ; Wed, 24 Jan 2024 13:46:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5B1163858D38 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yandex.ru ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 5B1163858D38 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=178.154.239.146 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706103980; cv=none; b=poBn/y6qKeaixct+ECV0ksnb48wIgkQnP4UU8CRDSgzgfkPjRf0F2Ybsym1nnDgNJuU0FUH1olSOVnipTvx7t2lBJgmFEwZ5USy2w1D7VqnFiE0281M4z6MGBx6zDRp8efnOVcuPKJer/KIW6MvGhujYD2Z7osZzWRhfkp0k+6E= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706103980; c=relaxed/simple; bh=NmOQnoIb68VUs1ksekpq0LcsvGt+0UhPqhXA3lQzc7E=; h=DKIM-Signature:Message-ID:Subject:From:To:Date:MIME-Version; b=IspsTVLkRLmZ2TVq6pgjbtFnqc5JA1vhJBTRkUjVHk1O5PYIyOU3CwwU61d+w+46OMpbQzM2lDwJhRwOVLT+ebUHILi2Vb0BF66piCSfyIBw4lbNveleOv72EewqjrGZqOUy61aPJJg2rwP8GEN6xOudWvff/4dtBx+ufoApoo0= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from mail-nwsmtp-smtp-production-main-91.myt.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-91.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:5392:0:640:98e3:0]) by forward502b.mail.yandex.net (Yandex) with ESMTP id CE6745EF9B; Wed, 24 Jan 2024 16:46:15 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-91.myt.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id EkTbJr9o9Ko0-nhRiLqiN; Wed, 24 Jan 2024 16:46:15 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1706103975; bh=NmOQnoIb68VUs1ksekpq0LcsvGt+0UhPqhXA3lQzc7E=; h=In-Reply-To:References:To:Message-ID:Subject:Date:From; b=rNR+MmtdcITz6J6rqcFriIw17nun3yU2XqttotBoTjrBimdtj8FJM5UUj3D8/13qz RiWkq8JQ3ToNTgxrb0v1XZ+VpIAAlPmbGNhJgMhSD4axjhB5IMFtlNZg5RyJgtfeVx byMEmMM7PHPgyMnYP7Wc+6LvCKrjZFZI1iGrTiVM= Authentication-Results: mail-nwsmtp-smtp-production-main-91.myt.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <784b1e1ed079019dd16cd9c5ed0e08dff9c735fd.camel@yandex.ru> Subject: Re: Where to send issues From: Konstantin Kharlamov To: Carlos O'Donell , =?UTF-8?Q?Luk=C3=A1=C5=A1_Ji=C5=99i=C5=A1t=C4=9B?= , libc-help@sourceware.org Date: Wed, 24 Jan 2024 16:46:14 +0300 In-Reply-To: <882e2cdb-fce8-c514-2af0-38a86cdc7526@redhat.com> References: <7f7e6e9ad516d189fd073c3d078eec5d9d77643e.camel@yandex.ru> <882e2cdb-fce8-c514-2af0-38a86cdc7526@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.3 MIME-Version: 1.0 X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Awww, thank you very much! I'm glad to hear the situation is improved so much! I'll see if the patches still apply, thank you again! On Wed, 2024-01-24 at 08:44 -0500, Carlos O'Donell wrote: > On 1/24/24 03:19, Konstantin Kharlamov wrote: > > On Wed, 2024-01-24 at 11:15 +0300, Konstantin Kharlamov wrote: > > > On Wed, 2024-01-24 at 09:05 +0100, Luk=C3=A1=C5=A1 Ji=C5=99i=C5=A1t= =C4=9B via Libc-help > > > wrote: > > > > Hello everyone, > > > > this is exciting as this is my first time ever using mailing > > > > list. > > > > I'm writing this, because I wanted to know, where to submit a > > > > minor > > > > typo in > > > > the GNU libc manual or whether there's a way I can fix it > > > > myself. > > > > Thank you all in advance. Have a nice day. > > >=20 > > > You can fix it yourself and send to a > > > libc-alpha@sourceware.org=C2=A0ML. > > > But > > > Glibc is very tough to contribute to because of lack of reviews > > > for > > > patches, so patches often just hang in there for years. I've seen > > > it > > > both from the side (you often see people ping over and over) and > > > I > > > have > > > myself a series of small fixes from 2019 or something that I was > > > pinging but to my knowledge by this day nobody reviewed it. > >=20 > > Ah, and you also need to sign some documents to be able to > > contribute > > to glibc =F0=9F=98=82 FTR, I have signed it, it's just an oddness that = GNU > > projects have. So, yeah, there's that as well =F0=9F=98=84 >=20 > Today the project accepts contributions without copyright assignment. >=20 > https://sourceware.org/glibc/wiki/Contribution%20checklist >=20 > You can just use DCO e.g. "Signed-off-by:" if you can attest to the > Developer > Certificate of Origin as Linux kernel developers do. >=20 > > > So unless you are motivated to ping over and over, I'd advice > > > just > > > fill > > > a bugreport. You can do that here > > > https://sourceware.org/bugzilla/enter_bug.cgi, chose "libc" as a > > > product. >=20 > I'm sorry to hear that you had a bad experience trying to contribute > :-( >=20 > It is indeed a problem that FOSS projects lack sufficient maintainer > resources > to review incoming patches. >=20 > We try to help out with that by having a weekly Monday morning patch > queue review. >=20 > https://sourceware.org/glibc/wiki/PatchworkReviewMeetings >=20 > The intent of the meetings is to allow the community to attend and > raise patches > they would like reviewed. >=20 > We track 2 metrics for the patch queue: > - How many currently need to be reviewed e.g. State NEW delegate > NOBODY. > - How many days on average the patches have been in the queue. >=20 > The latter metric is at ~260 days, which is a number I watch to see > what we > can do e.g. spend a week reviewing patches or not. >=20 > We are trying to use pre-commit CI to make it easier to commit > simpler patches. > https://patchwork.sourceware.org/project/glibc/list/ >=20 > I see patches from you in 2019 which predate our start of the patch > queue review > and the pre-commit CI work. Please feel free to repost them if they > still apply > and we'll see if we can get them committed. >=20