From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 3T9gIxlyhWW3jScAWB0awg (envelope-from ) for ; Fri, 22 Dec 2023 06:25:13 -0500 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=Gd3DCZcY; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 7E9811E0C3; Fri, 22 Dec 2023 06:25:13 -0500 (EST) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 6A63B1E091 for ; Fri, 22 Dec 2023 06:25:11 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id C31FE3858016 for ; Fri, 22 Dec 2023 11:25:10 +0000 (GMT) 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 EF79C3858D28 for ; Fri, 22 Dec 2023 11:24:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EF79C3858D28 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 EF79C3858D28 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=1703244299; cv=none; b=N2RXt7n2OE66+aZCLCrFOn2bQDoOFMoFBCqmQ+aquiglJ6/CB2JRhsuiyz24RbQzX4PDUIMr7SbsmQfeQBa468BR8OXWbUGZVFgNl312FLjm1rQvqAai90N5t/suCTB3DNhq5XTaIqWAOQZk6zmXMoDX/k472t0hD/94kgkUq84= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703244299; c=relaxed/simple; bh=okEqI+uMrCbwzNoQ46/DMFgeI3Iy/wvhsDX674HCDRY=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=aD9k4clJajALVDkp/L3h+i49WQj/tpfDFXG8LRfbpoLjWee4W6Z71r+HHD7IZ6+nZsbBln8k3fsDL22wV1t532Z9GwCcdk88/pRkPiNrrPdn92ME8yRNQYK/tTjXHwe93a/4OTobAXItkkQOevJccOpW7RfUwj510HN3ljEfYno= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1703244297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mj5iV29d0kE4OTubFMRtr0/KOkHD5Sygjp4EpiwWmF0=; b=Gd3DCZcYGdESJujJvJ+FhN9D1ix5DiXXpkJS3kF+vQTuWx6lteXCVa7bRIbfEXuBdxUao1 0UBfijJJV86lTJbZEHJD6R0MR9r1cUwRU0MNzF93xrqu1fVMIp6EL892EKyLp3+xU1FlOR acg79RmKTT8zzF8dolZGDBKiZNrjhN0= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-563-AZN4wk1UOmS9UvkkooiV0A-1; Fri, 22 Dec 2023 06:24:55 -0500 X-MC-Unique: AZN4wk1UOmS9UvkkooiV0A-1 Received: by mail-wm1-f72.google.com with SMTP id 5b1f17b1804b1-40d3bb7c274so15367535e9.2 for ; Fri, 22 Dec 2023 03:24:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703244294; x=1703849094; h=mime-version:message-id:date:references:in-reply-to:subject:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mj5iV29d0kE4OTubFMRtr0/KOkHD5Sygjp4EpiwWmF0=; b=VHOAWVb9bxhkEd/TiU3d3D1GP3rvZMxzKPZQ5D5epIr8NJ3kVnmQXoAcVQplfrZb21 kHzs0h8b/nY71mHdkTvLga/wKYVsCqh5hMF7tGh1W2Ov40Cr2px6R56Agv1vfb6Tnn2z PZSgg3Zkd/okkgKiqh6OO0JcV7XSFg1H+qiULqCnG2YIYM/cZihNAdTjFR5IRkOrSw6G vzwrO7AOvOp5nCqtR0inRarCGCL+77QESHtNjId+bqWhqUUzW+F6SY9SbfrEYKM665yE bA4xw2IP8kpkTl3GvmIaTToFPqZ7XJwLrpF5cJs7IcDJfRcWwwDKPwGMcSF2kTJTb2Ms 7JNw== X-Gm-Message-State: AOJu0YzsAEg5OwPi5A+L7SnTeYOMBc6zUGCcHiL2DXqj1prZxd5yRMJd W86/eb+KKYYxpecRCeueikrYRSl6aK4uVkbRt3qBH9DHG0DAnXNnqfn8VB7DLWmnEUZns/McnyF 2ftdB1ObKtFpC7FntI82zlcrDp0PsXDaj1Q3Av6Zmk+zEg+ZzlsJvaaFWXR5+EYPl4g/Q1SBTPY CUA3RlBDlLIGZoKQ== X-Received: by 2002:a05:600c:13d3:b0:40c:6d83:4721 with SMTP id e19-20020a05600c13d300b0040c6d834721mr376407wmg.319.1703244293790; Fri, 22 Dec 2023 03:24:53 -0800 (PST) X-Google-Smtp-Source: AGHT+IGUczgDkg5yNowH+wEd2M/jTHuuSsBf1Om4sFzOKL363VCTtWm6SIsNUVwRxwQMJYa9Z3ESKw== X-Received: by 2002:a05:600c:13d3:b0:40c:6d83:4721 with SMTP id e19-20020a05600c13d300b0040c6d834721mr376402wmg.319.1703244293336; Fri, 22 Dec 2023 03:24:53 -0800 (PST) Received: from localhost (105.226.159.143.dyn.plus.net. [143.159.226.105]) by smtp.gmail.com with ESMTPSA id ay14-20020a05600c1e0e00b0040c6ab53cd2sm6768277wmb.10.2023.12.22.03.24.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 03:24:53 -0800 (PST) From: Andrew Burgess To: gdb-patches@sourceware.org Subject: Re: Introducing a GDB Code Of Conduct In-Reply-To: <87edg7nsen.fsf@redhat.com> References: <87edg7nsen.fsf@redhat.com> Date: Fri, 22 Dec 2023 11:24:52 +0000 Message-ID: <878r5mzdh7.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Andrew Burgess writes: > Greetings GDB Community! > > Many GNU toolchain projects have adopted a Code of Conduct (CoC) > recently, and I believe that GDB should do likewise. > > A CoC is not about imposing new rules onto the GDB community, but is an > opportunity for us to document how we already treat each other within > our community, so that new people looking to engage with us can easily > understand what is expected of them, and what they can expect from > others. Additionally, the CoC gives a clear mechanism by which any > issues a community member may have can be raised. > > I have discussed this proposal briefly with the other global > maintainers, and their feedback was either supportive, or neutral on > this topic, so I'm now opening this conversation to the wider GDB > community. > > The text of the proposed CoC can be found at the end of this email, and > I look forward to hearing people's thoughts. > > Like anything, the CoC should grow and evolve as the GDB community > continues to grow and evolve, this is not a once and done deal. But, we > need something in place to evolve from. > > With that in mind, unless someone identifies a show stopping issue with > the text below, then I am proposing that I will make this live some time > around mid-December 2023. After that changes to the CoC can be handled > in the normal way, via discussion on the list. I've now added the code of conduct to the GDB website. However. I still need some volunteers to join the code of conduct committee. The only requirement is that you have been active in the GDB community for at lest the last year, that you be willing to sign up to the gdb-conduct mailing list and be willing to engage with any issues that are reported there. I predict / hope that we'll not see anything much reported there, so my hope is that this will be pretty much a non-task. Remember, this is not about *changing* the way the GDB community works, but about preserving the great environment we already have. Membership of the conduct committee will be made public on the GDB website. If you are willing to help out with this, then let me know and I'll get you added in the New Year. Thanks, Andrew