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 1r0kse-007dhG-31 for pgsql-announce@arkaria.postgresql.org; Wed, 08 Nov 2023 15:54:12 +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 1r0ksc-005Cvq-Pm for pgsql-announce@arkaria.postgresql.org; Wed, 08 Nov 2023 15:54:10 +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 1r0ksb-005Cuw-Mv for pgsql-announce@lists.postgresql.org; Wed, 08 Nov 2023 15:54:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r0ksY-004aRb-Rp for pgsql-announce@lists.postgresql.org; Wed, 08 Nov 2023 15:54:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=cobkuObtwG0Ur1tdDDggU/FCwaDONA0Nb+yuvvtVOsw=; b=s+bxjb1151NC4CpGEJZmrYUmx0 eMUxlNn6zEv6D6uiZcITn7v1D+TUPBIQF+dNyivFKb6DfX3I1q2r+d7DyjCavOqXCzBp4Ej11eHiX wMBjFns/ZPUkyYF9eyfn81fQFf+SOjbWdRrI27dfhtvhNoyDvnDkuUBv8dNUcYKg74clHs8G1aiuc /ZxBrJLvAnknudbfisKlsSISSijupmPxdXvSUquhHoPuqSbvK+WNuMJn36CBX7Oa7ztKh1AcZdi0x dz2CAT+9PinC+UeDR7DNgqxwYsxBrC8JSVkdHQDYu3PqxVWRdSnGBEQztHma8yP8/lqtF3CHmK0sB kbU27xyQ==; Received: from wrigleys.postgresql.org ([87.238.57.234]) by mahout.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r0ksX-0006Xz-Qf for pgsql-announce@lists.postgresql.org; Wed, 08 Nov 2023 15:54:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r0ksT-00HU61-HP for pgsql-announce@lists.postgresql.org; Wed, 08 Nov 2023 15:54:02 +0000 Content-Type: multipart/mixed; boundary="===============1377061304309954267==" MIME-Version: 1.0 Subject: PGConf.dev 2024 - Call for Speakers and Sponsors To: PostgreSQL Announce From: Slonik Events Canada via PostgreSQL Announce Reply-To: contact@pgconf.dev Date: Wed, 08 Nov 2023 15:53:58 +0000 Message-ID: <169945883883.1769274.12166130332335861222@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 9506cdd65a6e79420ff0b40b5d99b87608e5741b1c88d766c2a445ce9f87bae2 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============1377061304309954267== Content-Type: multipart/alternative; boundary="===============8310481517900960326==" MIME-Version: 1.0 --===============8310481517900960326== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [PGConf.dev 2024](https://2024.pgconf.dev/) (May 28 - 31, 2024, Vancouver, = CA), aka [PostgreSQL Development Conference 2024](https://2024.pgconf.dev/)= , is an event focused on PostgreSQL development and contributions. The succ= essor to PGCon, PGConf.dev offers a collaborative and fun environment to di= scuss future development for PostgreSQL! The [call for papers](https://2024.pgconf.dev/cfp/) is open through Jan 15,= 2024! We're looking for talk submissions focused on PostgreSQL development= : upcoming PostgreSQL features, recently committed work, and community-buil= ding focused talks. The audience ranges from new to longtime PostgreSQL con= tributors, and we expect many talks to be more intermediate to advanced lev= el on technical topics. We will also have introductory talks on how to get = started contributing to PostgreSQL! Even if you've never presented at a PostgreSQL event before, [we'd love to = hear your ideas](mailto:contact@pgconf.dev) and can provide help on getting= your presentation ready! You can submit your talk ideas here: [https://2024.pgconf.dev/cfp/](https://2024.pgconf.dev/cfp/) [PGConf.dev 2024](https://2024.pgconf.dev/) is not possible without the [ge= nerous support of our sponsors](https://2024.pgconf.dev/sponsors/). PGConf.= dev is the premier worldwide gathering of PostgreSQL contributors, and is a= chance to collaborate on upcoming PostgreSQL development. Your sponsorship= helps directly with the ongoing development of PostgreSQL. As of this anno= uncement, we are finalizing our details on sponsorship levels. More informa= tion will be available on the [sponsorship](https://2024.pgconf.dev/sponsor= s/) page, or you can contact us at [sponsors@pgconf.dev](mailto:sponsors@pg= conf.dev): [https://2024.pgconf.dev/sponsors/](https://2024.pgconf.dev/sponsors/) Can't wait to participate in [PGConf.dev 2024](https://2024.pgconf.dev/)? [= Registration](https://2024.pgconf.dev/registration/) will open soon. We look forward to seeing you in Vancouver in May! --===============8310481517900960326== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGConf.dev 2024 - Call for Speakers and Sponsors
 

PGConf.dev 2024 - Call for Speakers and Sponsors

PGConf.dev 2024 (May 28= - 31, 2024, Vancouver, CA), aka PostgreSQL Development Conf= erence 2024, is an event focused on PostgreSQL development and contribu= tions. The successor to PGCon, PGConf.dev offers a collaborative and fun en= vironment to discuss future development for PostgreSQL!

The call for papers = is open through Jan 15, 2024! We're looking for talk submissions focused on= PostgreSQL development: upcoming PostgreSQL features, recently committed w= ork, and community-building focused talks. The audience ranges from new to = longtime PostgreSQL contributors, and we expect many talks to be more inter= mediate to advanced level on technical topics. We will also have introducto= ry talks on how to get started contributing to PostgreSQL!

Even if you've never presented at a Postgre= SQL event before, we'd love to hear your ideas and can = provide help on getting your presentation ready!

You can submit your talk ideas here:

https://2024.pgconf.dev/= cfp/

PGConf.dev 2024 is not = possible without the generous support of our sponso= rs. PGConf.dev is the premier worldwide gathering of PostgreSQL contrib= utors, and is a chance to collaborate on upcoming PostgreSQL development. Y= our sponsorship helps directly with the ongoing development of PostgreSQL. = As of this announcement, we are finalizing our details on sponsorship level= s. More information will be available on the sponso= rship page, or you can contact us at sponsors@pgconf.d= ev:

https://2024.pgconf= .dev/sponsors/

Can't wait to participate in PGConf.dev 2024? Registration will ope= n soon.

We look forward to seeing you in Vancouver = in May!
This email was sent to you from Slonik Events Canada. It was delivered on t= heir behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Slonik Events Canada.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Community Conferences. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============8310481517900960326==-- --===============1377061304309954267==--