From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id B83CB3858410; Thu, 6 Jan 2022 16:20:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B83CB3858410 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.cz Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id A986C1F385; Thu, 6 Jan 2022 16:20:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1641486018; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=fU2NeQJI73S6mPeqv/GyU8qhaPQXB4WpcoHE6RhA1ac=; b=ox1bwZyjRFwj0ICfWbcgnBqdBnZGulwxyNoziwRfbuNLz3n21LRLuZ8Ur/CVq2Qppqq6z5 OC8MOBpy+UKSK2nOMN+lyjDzSaIJoUIKFxVktYD3CVYbZHIfdEi4ido2quqa8M3kTjLRe/ Q+sGYAGqom/rvSM53EdlurZ/91SgAzw= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1641486018; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=fU2NeQJI73S6mPeqv/GyU8qhaPQXB4WpcoHE6RhA1ac=; b=fYR1jXNs3AqYI0wJFE7vOR5qCrPNWl6wAkt7wigLwFAqpd+YRm5V1ikO9R5PEzVcWBr84w EtCQOS6UMw3kVeDg== Received: from suse.cz (virgil.suse.cz [10.100.13.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 96803A3B83; Thu, 6 Jan 2022 16:20:18 +0000 (UTC) From: Martin Jambor To: GCC Mailing List , Gfortran mailing list , libstdc++@gcc.gnu.org Subject: GCC GSoC 2022: Call for project ideas and mentors User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/27.2 (x86_64-suse-linux-gnu) Date: Thu, 06 Jan 2022 17:20:18 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_ASCII_DIVIDERS, KAM_SHORT, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2022 16:20:21 -0000 Hello, another year is upon us and Google has announced there will be again Google Summer of Code 2022 (though AFAIK there is no specific timeline yet). I'd like to volunteer to be the main Org Admin for GCC again so let me know if you think I shouldn't or that someone else should, but otherwise I'll assume that I will. There will be a few important changes to the GSoC this year. The most important for us is that there will be two project sizes: medium-sized projects which are expected to take about 175 hours to complete and large projects expected to take approximately 350 hours (the size from 2020 and earlier). I expect that most of our projects will be large but I think we can offer one or two medium-sized ideas too. Google will also increase timing flexibility, so the projects can run for longer (up to 22 weeks) allowing mentors to go on vacation and students to pause and focus on exams. Talking about students, Google is going to open the program to all adults, so from now on, the participants working on the projects will be called GSoC contributors. Slightly more information about these changes can be found at https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html I am sure we will learn more when the actual timeline is announced too. ======================== The most important bit: ======================== Even before that happens, I would like to ask all (moderately) seasoned GCC contributors to consider mentoring a student this year and ideally also come up with a project that they would like to lead. I'm collecting proposal on our wiki page https://gcc.gnu.org/wiki/SummerOfCode - feel free to add yours to the top list there. Or, if you are unsure, post your offer and project idea as a reply here to the mailing list. ========================================================================= Eventually, each listed project idea should have a) a project title/description, b) more detailed description of the project (2-5 sentences), c) expected outcomes, d) skills required/preferred, e) project size and difficulty and f) expected mentors. Project ideas that come without an offer to also mentor them are always fun to discuss, by all means feel free to reply to this email with yours and I will attempt to find a mentor, but please be aware that we can only use the suggestion it if we actually find one. Everybody in the GCC community is invited to go over https://gcc.gnu.org/wiki/SummerOfCode and remove any outdated or otherwise bad project suggestions and help improve viable ones. Finally, please continue helping (prospective) students figure stuff out about GCC like you always do. So far I think all of them enjoyed working with us, even if many sometimes struggled with GCC's complexity. I will update you as more details about GSoC 2022 become available. Thank you, let's hope we attract some new talent again this year. Martin