From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 65ED13858D1E for ; Wed, 24 Jan 2024 13:44:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 65ED13858D1E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 65ED13858D1E Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706103876; cv=none; b=xDyXO+/mKQbxXLEuFB0kS+4RPeyaL0N+Fto78dgeT2M2/O2oJHT+zLGR8UbzBT+VXvSAJwfaBajLTQPK1/JDZqlabEKJhZ6xZL7Ch1OqfE/D8PJIqFFtKuDTx7l5l54StfIvzGTmhbc8i8o4Dl2YcUxDHNcgpCbgIsHkRaAsoBg= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1706103876; c=relaxed/simple; bh=G5HaY0ZUc3HpZKnkc89/ptGROkC+urHDCt7KouUmRDA=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=pMLS4fdhyf1hiSmaDC9bb/teg6X7wMzVL4oxSX1z0dXwxsMjgW0Wy7yUlApq9VlQ600pJXyPWVueXZlfNBTiBhn5rrpSJKGKZSxsbpD9a6Uc2w+FrU79pA7/q9gXmKesHhCACwHtfcmlCYcMWEdwFNTNW9IVaSOFPIT7AhqD6bA= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1706103874; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+vxfTe/TeDBsRAxh2vznY1YOaVpSafUMjUMAsieEt9I=; b=IAcz3O0vAKjw6959XGgTxrKcBl1L3ozs5ssiM+XPN8p4BG5gbfEAQf66Q38mskM0doodHA KOkzEz5psfaF+Xcu7LV5TsVhSnA7C8SP0s0BB1KTQqRRtW0Jsxy/mIg5FI7wC7XcciecfH J8RfXEOki71SuQdM4TIuqfIZoMtJ23Y= Received: from mail-qt1-f200.google.com (mail-qt1-f200.google.com [209.85.160.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-543-rOoskVuONSCxKSLMgROYkw-1; Wed, 24 Jan 2024 08:44:33 -0500 X-MC-Unique: rOoskVuONSCxKSLMgROYkw-1 Received: by mail-qt1-f200.google.com with SMTP id d75a77b69052e-429d0905823so101719591cf.0 for ; Wed, 24 Jan 2024 05:44:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706103871; x=1706708671; h=content-transfer-encoding:in-reply-to:organization:from:references :to:content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+vxfTe/TeDBsRAxh2vznY1YOaVpSafUMjUMAsieEt9I=; b=WWxaz+v98KCXx1ZLLovn/XXXFRCitIxZdg2DIACdoBLPbXxPxP5/BG005H7CEAXmiz fj/L9hQ/to/A3yLSiofYa2XssyOUnzhY8B+Cvi6VbBhtcxNADog9aPnBdQTXItmAU/iv JaHaM1RyvGWK8jyDzgO10C8maBU17KD4qM72zET3oazTXIHib3z91tZgXO/ZSiqP1RVD dbLqJfLmCnwWWEWErqvm/VVR1r9RzrT9YXYd9Jl2SulkK2nVPzveZdSMrHcPMPgPrr4G AzTaFW4nspGsQKbX+3cNTBfTMxOkGQmcwcIggG83pszZ9nOFd+aQgbEqApKajQvwpBuP uBjA== X-Gm-Message-State: AOJu0YwZrE9re6AsARp5+XL4hG0qQSUFE6lW2cexAV9srfJ42GeWYDe8 SbjXPnD5mOdNAfV5sVZHcmfjwuixfmdVtPWagLQZNYlYzt65GbMSaJX7LnKhCAR4SftFnfapSMk KmFdtWvEFRI8AR5YWik5GNKfKEs5EfjJTBt/JILCqwlBpZR6rQikw/8as6l3jLNgB X-Received: by 2002:ac8:4414:0:b0:42a:2e33:4b80 with SMTP id j20-20020ac84414000000b0042a2e334b80mr1666185qtn.66.1706103871255; Wed, 24 Jan 2024 05:44:31 -0800 (PST) X-Google-Smtp-Source: AGHT+IF/tckyQuJ/L1cSZMERzrRyhqUnZfpoe/4wqkaZsKCu5TaPKc1WIUIhxKD3o7pIRsJ2VW34aw== X-Received: by 2002:ac8:4414:0:b0:42a:2e33:4b80 with SMTP id j20-20020ac84414000000b0042a2e334b80mr1666175qtn.66.1706103870946; Wed, 24 Jan 2024 05:44:30 -0800 (PST) Received: from [192.168.0.241] ([198.48.244.52]) by smtp.gmail.com with ESMTPSA id eo10-20020a05622a544a00b0042994f83b25sm4395601qtb.35.2024.01.24.05.44.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Jan 2024 05:44:30 -0800 (PST) Message-ID: <882e2cdb-fce8-c514-2af0-38a86cdc7526@redhat.com> Date: Wed, 24 Jan 2024 08:44:29 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: Where to send issues To: Konstantin Kharlamov , =?UTF-8?B?THVrw6HFoSBKacWZacWhdMSb?= , libc-help@sourceware.org References: <7f7e6e9ad516d189fd073c3d078eec5d9d77643e.camel@yandex.ru> From: Carlos O'Donell Organization: Red Hat In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_WEB,SPF_HELO_NONE,SPF_NONE,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: 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áš Jiřiště 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. >> >> You can fix it yourself and send to a libc-alpha@sourceware.org ML. >> 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. > > Ah, and you also need to sign some documents to be able to contribute > to glibc 😂 FTR, I have signed it, it's just an oddness that GNU > projects have. So, yeah, there's that as well 😄 Today the project accepts contributions without copyright assignment. https://sourceware.org/glibc/wiki/Contribution%20checklist 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. >> 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. I'm sorry to hear that you had a bad experience trying to contribute :-( It is indeed a problem that FOSS projects lack sufficient maintainer resources to review incoming patches. We try to help out with that by having a weekly Monday morning patch queue review. https://sourceware.org/glibc/wiki/PatchworkReviewMeetings The intent of the meetings is to allow the community to attend and raise patches they would like reviewed. 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. 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. We are trying to use pre-commit CI to make it easier to commit simpler patches. https://patchwork.sourceware.org/project/glibc/list/ 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. -- Cheers, Carlos.