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 1rRxjS-00AT81-58 for pgsql-announce@arkaria.postgresql.org; Mon, 22 Jan 2024 17:05:11 +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 1rRxjR-005K98-8J for pgsql-announce@arkaria.postgresql.org; Mon, 22 Jan 2024 17:05:09 +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 1rRxjQ-005K8E-6z for pgsql-announce@lists.postgresql.org; Mon, 22 Jan 2024 17:05:08 +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 1rRxjN-002ozt-As for pgsql-announce@lists.postgresql.org; Mon, 22 Jan 2024 17:05:06 +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=GERpYRzgstzDKZj53T7FE7ldzl+2k7LP+3Q/D0fqUMA=; b=tzAILEhz/pnS13V6gq/BO0nSQ/ QAcsOW/w4u/LPPxr2vO4l6Javq/hMEbf0bUwKGVmakeF2zFtAIVJFggz5aExB964ecDVPtrxdWUMo ca7n0JMXVVAWZ7H+zKAYiYPfh/V2/Fv368Ghn7Gy3HJQuliDQo5WYp2/5eS1d7JdFQqY+Uhf7JCn3 Km0Y5m3z1c2J/wmhromJ3z/aIykDCsHj20BoLxmyM8Rz1JhQa6bjlapTeL+nZn28WYJs44ugjoaZH GUlHAJBI2oy2IePX5c3iS5A1rjB6UWHw3tA/G6jTkeYTZhiFv1agH0aiT/ky76yRBkcyrKYW1av+k xwz0a4CA==; Received: from wrigleys.postgresql.org ([2a02:c0:301:0:ffff::34]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rRxjL-008azN-TK for pgsql-announce@lists.postgresql.org; Mon, 22 Jan 2024 17:05:04 +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 1rRxjK-002ZMF-6f for pgsql-announce@lists.postgresql.org; Mon, 22 Jan 2024 17:05:02 +0000 Content-Type: multipart/mixed; boundary="===============0200016969522063741==" MIME-Version: 1.0 Subject: Prague PostgreSQL Developer Day 2024 / Call for Papers & Sponsors To: PostgreSQL Announce From: "CSPUG (Czech and Slovak PostgreSQL Users Group) via PostgreSQL Announce" Reply-To: info@cspug.cz Date: Mon, 22 Jan 2024 17:04:19 +0000 Message-ID: <170594305988.661.3817314903911660917@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 4a1ea69ed6bae95c97df7dd4d81a41cfc512df157317131b19cbff141e81e206 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0200016969522063741== Content-Type: multipart/alternative; boundary="===============6458295865855967287==" MIME-Version: 1.0 --===============6458295865855967287== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Prague PostgreSQL Developer Day 2024 (P2D2 2024) will be held on June 4 and= 5 in Prague, Czech Republic. The conference focuses on topics for PostgreS= QL users and developers. For more information about the event, please see t= he website at [https://www.p2d2.cz/](https://www.p2d2.cz/)=20 We are now accepting proposals for talks and trainings in both Czech and En= glish. As in previous years, the conference is a single-track event with a = mix of talks in Czech and English. To submit a talk, use this form: https://p2d2.cz/call-for-papers The talk sessions are generally 45 minutes long (but may be shorter if requ= ested) and may be on any PostgreSQL-related topic. We're also looking for t= rainings (either half-day or whole-day) for the first day (June 4). To subm= it a training proposal, use the same form as for regular talks (there's a f= ield to pick talk/training). Finally, we are considering to include a session of lightning talks (short = talks, five minute each). A separate call for proposals will be made for th= em during the event. The submission deadline is March 1 (which is Friday), end of day. Selected = speakers will be notified / confirmed shortly afterwards. The proposals will be considered by committee who will produce a schedule t= o be published about a month before the event. All selected speakers will get free entry to the conference (excluding trai= ning sessions). We do offer covering travel and accommodations for foreign = speakers (generally enough for two nights in a hotel and travel within Europe). If you require assistance with funding to be able to attend= , please make a note of this in the submission notes field. We have also opened our call for sponsors. As usual, we we'll offer three s= ponsorship levels - the details are available at: https://p2d2.cz/rocnik-2024/sponsorship If you wish to become a sponsor, or have questions/suggestions regarding sp= onsorship, please contact us at sponsors@p2d2.cz (we're happy to answer any= questions about the event and sponsorship conditions). We look forward to hearing from you, and seeing you in Prague! --===============6458295865855967287== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Prague PostgreSQL Developer Day 2024 / Call for Papers & Spo= nsors
 

Prague PostgreSQL Developer Day 2024 / Call for Papers & Sponsors=

Prague PostgreSQL Developer Day 2024 (P2D2 = 2024) will be held on June 4 and 5 in Prague, Czech Republic. The conferenc= e focuses on topics for PostgreSQL users and developers. For more informati= on about the event, please see the website at https://www.p2d2.c= z/

We are now accepting proposals for talks an= d trainings in both Czech and English. As in previous years, the conference= is a single-track event with a mix of talks in Czech and English.

To submit a talk, use this form:

 https://p2d2.cz/call-for-papers

The talk sessions are generally 45 minutes = long (but may be shorter if requested) and may be on any PostgreSQL-related= topic. We're also looking for trainings (either half-day or whole-day) for= the first day (June 4). To submit a training proposal, use the same form a= s for regular talks (there's a field to pick talk/training).

Finally, we are considering to include a se= ssion of lightning talks (short talks, five minute each). A separate call f= or proposals will be made for them during the event.

The submission deadline is March 1 (which i= s Friday), end of day. Selected speakers will be notified / confirmed short= ly afterwards.

The proposals will be considered by committ= ee who will produce a schedule to be published about a month before the eve= nt.

All selected speakers will get free entry t= o the conference (excluding training sessions). We do offer covering travel= and accommodations for foreign speakers (generally enough for two nights i= n a hotel and travel within Europe). If you require assistance with funding to be able to attend= , please make a note of this in the submission notes field.

We have also opened our call for sponsors. = As usual, we we'll offer three sponsorship levels - the details are availab= le at:

https://p2d2.cz/rocnik-2024/sponsorship

If you wish to become a sponsor, or have qu= estions/suggestions regarding sponsorship, please contact us at sponsors@p2= d2.cz (we're happy to answer any questions about the event and sponsorship = conditions).

We look forward to hearing from you, and se= eing you in Prague!
This email was sent to you from CSPUG (Czech and Slovak PostgreSQL Users Gr= oup). It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to CSPUG (Czech and Slovak PostgreSQL Users Group).

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/.
 
--===============6458295865855967287==-- --===============0200016969522063741==--