Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAdJ5-0000ba-AA for pgsql-www@arkaria.postgresql.org; Thu, 20 Jan 2022 19:41:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAdJ4-0003ME-5L for pgsql-www@arkaria.postgresql.org; Thu, 20 Jan 2022 19:41:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAdJ3-0003M5-UK for pgsql-www@lists.postgresql.org; Thu, 20 Jan 2022 19:41:13 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nAdJ1-0002UD-4X for pgsql-www@lists.postgresql.org; Thu, 20 Jan 2022 19:41:12 +0000 Received: by mail-wm1-x329.google.com with SMTP id q141-20020a1ca793000000b00347b48dfb53so16384869wme.0 for ; Thu, 20 Jan 2022 11:41:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:content-language:to:from :subject:content-transfer-encoding; bh=Tna4AEtImJOQbmapdz7VHN/LdXA7T1ophDjXsRjeb0c=; b=Xq4UI2MG0UkWvGhbo4lf962k7fdjCZ2RCrXqlV4Eo/3gfD02IFzz9/q01br4CKhz1H 1zDYvl/ph2c7fhmcRnSzj0oAE9A2MELznMmSXOfC7wQaIFCE6Gxrx8Z6ZOp2MLUcM75H vbARJzPOE2RzfVSrmGELUdByc3gApiaxdEui09RNmPBE4gQ11sPvB/NI7LFf9pwUDSq4 qURPgO0mXf5ALOWtfe/91BA/CtL7r7fX95ktR74QVQoW/ORXGu5toLD4hCBXMUT8eyya fZ6n3BPMjvKvkML3A1aB6NWOY2COZQrArPMABG2rzXPCnQ1VAyhbXl5jiJvXE/tis4o+ vErw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:from:subject:content-transfer-encoding; bh=Tna4AEtImJOQbmapdz7VHN/LdXA7T1ophDjXsRjeb0c=; b=CxEZQmYa5ONAvRQeO0VOGjAsfuJob5dsXV0sKQdsuN/8BsWLxXDHR0iGxGbX0vouqS 5x/ZwUkMxIUrGi9zjYHG1QyaxHjyezGjOgnsxZX83aBDpn69tkemSfUQhkqArnUQTPlg ER29oyOfyNCYccbNA+Q9e86FUnuYsLtRTeBXVd64I7O1B37tP0yQi8VPy1r1qo/6Q5Sy vvl2bg+oJ6tksJrVN4JiIx38HonS6NOhMkLcvRXBNBWXviDSF0XQ1am2wpRWEVsVKDFn M2TsTZVSbq1pCvlY5EB4DbNRkyj61eB0K9shgE5/Q62rTR0HSwtvbt5r5vY4q40gyrAa xGsg== X-Gm-Message-State: AOAM532GH9MtLjxJ5GZ+7D143hLjjXcutWaC0F5vG/OxLYUuwB/m0deM YkDDL3l0oBkPEK0qost6LeQ2pPv8H1hCrg== X-Google-Smtp-Source: ABdhPJzTGWSLCiFjb8VE8ld7vbkNzWD/isUBOv6hfVC53jab8SvBvbPqYkJ2UTIcZAMD3hlMpSxJ3Q== X-Received: by 2002:a05:600c:4e44:: with SMTP id e4mr10500573wmq.113.1642707669465; Thu, 20 Jan 2022 11:41:09 -0800 (PST) Received: from [192.168.2.176] (p508c7a26.dip0.t-ipconnect.de. [80.140.122.38]) by smtp.gmail.com with ESMTPSA id e15sm4659071wrg.91.2022.01.20.11.41.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Jan 2022 11:41:09 -0800 (PST) Message-ID: <1bf8df8c-20e6-ce5d-b456-6bd7329104bd@gmail.com> Date: Thu, 20 Jan 2022 20:42:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Content-Language: en-US To: pgsql-www@lists.postgresql.org From: Ilaria Battiston Subject: GSoC 2022 [-www] Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Greetings -www, You possibly have already seen this email in -hackers, but I felt like reaching out to you specifically since this year we have so many full-stack development projects :) feel free to check them out and please let me know if you have any feature or idea to be implemented by contributors, even if you won't have time for mentoring! --- Our beloved Google Summer of Code is back for 2022! They have once again changed some of how GSoC is going to work for this year, for a variety of reasons, so please be sure to read this email and posts linked for the updates if you're interested! In short, this year both medium and large sized projects can be proposed, with more flexibility on end dates. Everyone interested in suggesting projects or mentoring should review the blog post here regarding the changes: https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html Now is the time to work on getting together a set of projects we'd like to have GSoC students work on over the summer. Similar to last year, we need to have a good set of projects for students to choose from in advance of the deadline for mentoring organizations. HOWEVER, as noted in the blog post above, project length expectations have changed. Please decide accordingly based on your requirements and availability! Also, there is going to be only one intermediate evaluation, similarly to last year. GSoC timeline: https://developers.google.com/open-source/gsoc/timeline One other thing to note is that anyone over the age of 18 will be eligible in 2022 in addition to students, broadening the pool of potential applicants and changing the terminology of applicants to "contributors". The deadline for Mentoring organizations to apply is: February 21. The list of accepted organization will be published around March 7. Unsurprisingly, we'll need to have an Ideas page again, so I've gone ahead and created one (copying last year's): https://wiki.postgresql.org/wiki/GSoC_2022 Google discusses what makes a good "Ideas" list here: https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html All the entries are marked with '2021' to indicate they were pulled from last year. If the project from last year is still relevant, please update it to be '2022' and make sure to update all of the information (in particular, make sure to list yourself as a mentor and remove the other mentors, as appropriate). Please also be sure to update the project's scope to be appropriate for the new guidelines. New entries are certainly welcome and encouraged, just be sure to note them as '2022' when you add them. Projects from last year which were worked on but have significant follow-on work to be completed are absolutely welcome as well - simply update the description appropriately and mark it as being for '2022'. When we get closer to actually submitting our application, I'll clean out the '2021' entries that didn't get any updates. Also - if there are any projects that are no longer appropriate (maybe they were completed, for example and no longer need work), please feel free to remove them. The page is still work in progress, so it's entirely possible I missed some updates where a GSoC project was completed independently of GSoC (and if I removed any that shouldn't have been - feel free to add them back by copying from the 2021 page). As a reminder, each idea on the page should be in the format that the other entries are in and should include: - Project title/one-line description - Brief, 2-5 sentence, description of the project - Description of programming skills needed and estimation of the difficulty level - Project size - List of potential mentors - Expected Outcomes Let's have another great year of GSoC with PostgreSQL! Thanks! Ilaria & Stephen [1]: https://www.postgresql.org/about/policies/news-and-events/