Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sikv2-008xyQ-8a for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 01:22:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sikuz-00HWE8-59 for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 01:22:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sikuy-00HWDu-PQ; Tue, 27 Aug 2024 01:22:45 +0000 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sikuu-001g2f-9s; Tue, 27 Aug 2024 01:22:44 +0000 Received: by mail-pg1-x533.google.com with SMTP id 41be03b00d2f7-7cd9cfe4748so3069844a12.2; Mon, 26 Aug 2024 18:22:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724721759; x=1725326559; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=kQAVeLo3eZy64liFeJbcRFW9aY34P1Mx+vHpS9bBf9E=; b=MkJkxU7VEeOijHnINeYIat1SU5Jrf5W+H99s4US/WHUCLhV1cVscA7otuxoUDDz9Fi Gr2nT204DRdw6W7TPxi5rzANNzGMpcxlx2geIt4DpGip2fdEA09EQcoy9eXqhKsq/1MX G4e0AWyorqdP7Aomjf/T9L/X0C2+auB8RqcCstC1iV+JJgacBnTDfAnIQr65ATYKfdcS w9ZFVPJUtHkI6/5dlyJFe5g5qT2EQhj9TvTg7IC8b/mzXBqCpy9oOXQYZQ6//DwkEuFf SvdQBDm7MAbscF8G9BOiQdD61VGaPrwsdk1IaqdySfY1IJZ+beoJkYay0n484ld/s1d9 5a3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724721759; x=1725326559; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=kQAVeLo3eZy64liFeJbcRFW9aY34P1Mx+vHpS9bBf9E=; b=GR3umQdjebxrT6dSxtwDTQOns4p/5NOuE71QH/jxx0lwvOUBSqYLKqJ6k5I9T5+XFw SXkM5HwWJgU7/vp8hy3tFfgD233gw37ZCmQumO59bx69jehF0Hv2troTk30IDh4JoEtv B1/uq5dsj6O2AEnXWPQd+Up/rmj3+QEY35t1nXnSwenE/R/0BJx94DF+JGT7W1uB1Bsj n+iJBMFGPWbH2xHD+t4eBLaJxSimGWFf45YLHS8+RLZt/BFSmVfZDODGiqBqP1dKZGP7 ykT/5vsuJFQWnSrYRPjkRKK0Kx+bHZtACSgDwybhD4ms1Ssrx4iNgJdzBdn3Qjc7Bwm+ EuDQ== X-Forwarded-Encrypted: i=1; AJvYcCUdjo8KYjCDaRDoXUITKrhMKgFm6TKrRKIwmykP1YRQgVLJolclJTIsT5sXxIOe7pMmEBQZa5AghyPqzJ8B0A==@lists.postgresql.org X-Gm-Message-State: AOJu0YweXrBYtr3FPfLOOzNXn3gPH4MksfsM30hEnvALbnRwkeX/67Yx 00M1fP/qQObP777eDb3ESSL57moEGg0X6Rmt5dV5VXeAXqgdf34GYDi09oHfF9ESpTJ2tHYefFn GuXbxIqUMOiVDki0cCrK2Zvaag+tmpIOm X-Google-Smtp-Source: AGHT+IHFZg570ng1pne5MQ5ho/2fYlgVxB277eYiLTygrkqsZsHaEeGZGOb0vDjlCIQ5JmWVSBaaq/NCVogWn+IpBtc= X-Received: by 2002:a17:90b:3144:b0:2d3:c8ed:f0be with SMTP id 98e67ed59e1d1-2d646d0ae37mr10447830a91.28.1724721759148; Mon, 26 Aug 2024 18:22:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Chris Travers Date: Tue, 27 Aug 2024 07:23:39 +0700 Message-ID: Subject: Re: Code of Conduct Committee Volunteer Drive To: "pgsql-generallists.postgresql.org" , pgsql-announce@lists.postgresql.org, Pg CoC Committee Content-Type: multipart/alternative; boundary="000000000000ca666d0620a013f7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ca666d0620a013f7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 27, 2024, 5:09=E2=80=AFAM Chris Travers wrote: > This message is being sent from the Community Code of Conduct Committee, > with the approval of the Core Team. > > As part of the Community CoC policy, the Committee membership is to be > refreshed on an annual basis. We are seeking up to 3 volunteers to serve = on > the Committee for the coming year, October 1, 2024 - September 30, 2024. > Correction. The term ends on 30 September 2025. > We are seeking people who reflect the diversity of the PostgreSQL > community, with the goal to have members from multiple countries and vari= ed > demographics. > > The time commitment for Committee involvement varies, based on internal > administrative work and the number of active investigations. We estimate = an > average of 5 to 10 hours per month, but that could increase if there is a= n > increase in the number of incident reports. > > If you are interested, please complete the questionnaire below, and email > your responses to the Committee at coc@postgresql.org no later than > September 15, 2024 at 05:00 PM UTC. > > The Questionnaire > > Your name: > > Current employer: > > Current country of residence: > > (We ask for employer and residence because one of the goals of the > Committee is to have representation from a variety of geographical areas. > We also want to avoid a concentration of members from one company.) > > 1. What interests you about being on the CoC Committee? > > 2. Have you been on another CoC Committee, or had a similar role at > another organization? (Prior experience is not required, it's just helpfu= l > to know everyone's background.) > > 3. What else do you want to tell us about yourself that is helpful for us > to know about your potential involvement with the CoC Committee? > > Please be sure to send your reply to the CoC email listed above. Thank yo= u! > > Regards, > > Chris Travers > > Acting Chair > > PostgreSQL Community Code of Conduct Committee > > --000000000000ca666d0620a013f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Aug 27, 2024, 5:09=E2=80=AFAM Chris Travers &l= t;chris.travers@gmail.com>= ; wrote:

This message is being sent from the Community Code of Conduct= Committee, with the approval of the Core Team.

As part of the C= ommunity CoC policy, the Committee membership is to be refreshed on an annu= al basis. We are seeking up to 3 volunteers to serve on the Committee for t= he coming year, October 1, 2024 - September 30, 2024.

Correction.=C2=A0 The term end= s on 30 September 2025.
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">

We ar= e seeking people who reflect the diversity of the PostgreSQL community, wit= h the goal to have members from multiple countries and varied demographics.=

The time commitment for Committee involvement varies, based on = internal administrative work and the number of active investigations. We es= timate an average of 5 to 10 hours per month, but that could increase if th= ere is an increase in the number of incident reports.

If you are= interested, please complete the questionnaire below, and email your respon= ses to the Committee at coc@postgresql.org no later than September 15, 2024 = at 05:00 PM UTC.

The Questionn= aire

Your name:

Cur= rent employer:

Current country of residence:

(We ask for employer and residence because one of the goals of the = Committee is to have representation from a variety of geographical areas. W= e also want to avoid a concentration of members from one company.)

1. What interests you about being on the CoC Committee?<= /span>

2. Have you been on another CoC Committee, or ha= d a similar role at another organization? (Prior experience is not required= , it's just helpful to know everyone's background.)

3. What else do you want to tell us about yourself that is help= ful for us to know about your potential involvement with the CoC Committee?=

Please be sure to send your reply to the CoC email listed above= . Thank you!

Regards,

Chris Travers

Actin= g Chair

P= ostgreSQL Community Code of Conduct Committee


--000000000000ca666d0620a013f7--