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 1sihwk-008HXQ-7q for pgsql-general@arkaria.postgresql.org; Mon, 26 Aug 2024 22:12:22 +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 1sihwi-00FwHs-62 for pgsql-general@arkaria.postgresql.org; Mon, 26 Aug 2024 22:12:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sihur-00FrNM-1G; Mon, 26 Aug 2024 22:10:25 +0000 Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sihup-001aF1-5B; Mon, 26 Aug 2024 22:10:24 +0000 Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-2d3c05ec278so3500817a91.0; Mon, 26 Aug 2024 15:10:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724710222; x=1725315022; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ByPgDkG0T9pALIj/X7S11pSUcoB841v2BYQokMvvrq4=; b=AcXpmT9PZpx/InzMqoJtqjT24HcWonx8J+sVUPhmwDm/jG0rU4HaWllXCdkSNd8yA5 m8KebVW4okiS5UZmSI+CCGwimRgiV0nqaF1o4HEdJM2/aoNKmmLO8rRXwL4DTnP2URNk 6fDtrBmyupLmZPavim8I1//b87ddBvUNbCjSviysXegMXkRkwDDg3oZoqzeo+SybsC6C ieEqDjwcuXj/PPotTfxeFHjdiCFGmTDWygIbUSZk6ukNbkSGCimzne38CmU464NjRxiE rNdM5KrAKbWyTS6NWUzqJ8uJ2mSTpKVQa4yAszVXQRzpC1KXUffzlgtPT1tBXPuQo30V dM4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724710222; x=1725315022; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ByPgDkG0T9pALIj/X7S11pSUcoB841v2BYQokMvvrq4=; b=DlrJ/qQuk6oYwqGZmdk0olRQ51XMHz+wDvTB29U+HqCFXgg07xZPOIU6s9oC+foWIW n8rRO2hKH3+ULhphj5v1Y1BXFs/tjIluUIrfceM55uQ0pjhGhOUgGvdlwBK8gbToR1DL MOVOnM2Wbxcyzr/x1KGfemH9QU4PYJjpc0DwJBCT0aKIqO9Zl2V0ojilZ0waW55SvYmM c9HtK1BCzw9QY+wN4FUfANW9HT0/+G0SiElWIa5U+Jf8fcw2OaOfJUzzjPdk7QvOl16Z eQiKpG8Xu8d/TMAJTOcKV3KioJ27ZLHESJrS6nqO6YHQNwKWIOH0yXek7ji4pI2THUDT 8kTw== X-Forwarded-Encrypted: i=1; AJvYcCVseosptjDrjaA3QWMfk97euSbPNjYIPuA85FkQZDVjclRgGtdumHOZaQk2YdfTAvPsMpgVNaFtWZp0ZhZkqw==@lists.postgresql.org X-Gm-Message-State: AOJu0YxXB7Ic5q0CRDqwy7QLd6HHyDNRPEDkuzsy8tCg4l5hGXyIDS5M IR8L3ZR+HMLHpjIypbpo6gA1d7b57qlJ2+DGsaSGr+VGa62Pk/RMaKkhAszcUyN/GnDlHYAUBPm T9ZeI8sAK6Du8X/1c6OFSVcaaLVSIt/b9qoE= X-Google-Smtp-Source: AGHT+IFMwPXv0o6XpkLD6CXzNaLjCPN7gZb/eJpxs8OnEgL+W4LYOcx8eCo5kon7TjzX3e8ww8lRD8n7Ju+tcHK2wu4= X-Received: by 2002:a17:90b:3d83:b0:2cf:cc13:471a with SMTP id 98e67ed59e1d1-2d646d81620mr8986811a91.43.1724710221695; Mon, 26 Aug 2024 15:10:21 -0700 (PDT) MIME-Version: 1.0 From: Chris Travers Date: Tue, 27 Aug 2024 05:09:30 +0700 Message-ID: Subject: Code of Conduct Committee Volunteer Drive To: "pgsql-generallists.postgresql.org" , pgsql-announce@lists.postgresql.org, Pg CoC Committee Content-Type: multipart/alternative; boundary="0000000000001ad0c606209d6410" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001ad0c606209d6410 Content-Type: text/plain; charset="UTF-8" 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. We are seeking people who reflect the diversity of the PostgreSQL community, with 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 estimate an average of 5 to 10 hours per month, but that could increase if there is an 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 helpful 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 you! Regards, Chris Travers Acting Chair PostgreSQL Community Code of Conduct Committee --0000000000001ad0c606209d6410 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

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

As part of t= he 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 f= or the coming year, October 1, 2024 - September 30, 2024.

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@p= ostgresql.org no later than September 15, 2024 at 05:00 PM UTC.

The Questionnaire

You= r name:

Current employer:

Current country of residence:

(We ask for employer and resi= dence because one of the goals of the Committee is to have representation f= rom 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 yo= u been on another CoC Committee, or had a similar role at another organizat= ion? (Prior experience is not required, it's just helpful to know every= one's background.)

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

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

Regards,

Chris Travers

Acting Chair

PostgreSQL Community Code of Conduct Co= mmittee


<= div dir=3D"ltr">
--0000000000001ad0c606209d6410--