From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by sourceware.org (Postfix) with ESMTPS id 5C7A43858D33; Tue, 10 Jan 2023 18:25:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5C7A43858D33 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=suse.cz Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 5AD6F20CEB; Tue, 10 Jan 2023 18:25:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1673375107; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=Z0yby2FwfNNeh8zTt9jB2XOnjUcRiV8UBOTdhjObSdI=; b=EuxpyN5fEr1vZ97yru/AvPOwbXNwZkEdjCXxnq1k118kiVOEp4jWJ1l1j1MAE2d6OFGtHu IFWUet7XOPWvl7g1pmroRI23ZOK62UtEYxdloCkGaz7EXSZrm5Lfs4CysjSqxpW4wl9cNQ OryXqh4vVYTg1s+bH2D0PzQE09Q00nQ= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1673375107; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type; bh=Z0yby2FwfNNeh8zTt9jB2XOnjUcRiV8UBOTdhjObSdI=; b=6RhhwR4V0ZmA5+qJO7g02jQiG754PqLIOJ7PojL8RzxWP/UEglNTAI3a+P2vO09THPMaY/ 17EUn0RQWZHu/QAQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4A3DB1358A; Tue, 10 Jan 2023 18:25:07 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id QGGuEYOtvWPUXAAAMHmgww (envelope-from ); Tue, 10 Jan 2023 18:25:07 +0000 From: Martin Jambor To: GCC Mailing List , Gfortran mailing list , libstdc++@gcc.gnu.org, gcc-rust@gcc.gnu.org Cc: Subject: GCC GSoC 2023: Call for project ideas and mentors User-Agent: Notmuch/0.37 (https://notmuchmail.org) Emacs/28.2 (x86_64-suse-linux-gnu) Date: Tue, 10 Jan 2023 19:25:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.2 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_SOFTFAIL,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hello, another year has passed and Google has announced there will be again Google Summer of Code (GsoC) in 2023 and the deadline for organizations to apply is already approaching (February 7th). 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 or if you want to do it instead, but otherwise I'll assume that I will. ======================== The most important bit: ======================== 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. ========================================================================= At this point, we need to collect list of project ideas. Eventually, each listed project idea should have: a) a project title, b) more detailed description of the project (2-5 sentences), c) expected outcomes (we do have a catch-almost-all formulation that outcome is generally patches at the bottom of the list in the wiki), d) skills required/preferred, e) project size (whether approximately 175 or 350 hours), f) difficulty (easy, hard or medium, but we don't really have easy projects), and g) 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 or ideally two. 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 have always done in the past. As far as I know, GSoC 2023 should be quite similar to the last year, the most important parameters probably are these: - Contributors (formerly students) must either be students or be "beginners to open source" (or both). - There are two project sizes, roughly 175 hours (medium-sized) and roughly 350 hours (large) in total. - Timing should be pretty much as flexible as last year. Two years ago it was 12 weeks for everyone but now projects can take anywhere between 10 and 22 weeks. (But I'd prefer if we tried to fit into 20 at maximum, even that means deadlines would get close to stage 1 end.) There will be one mid-term and one final evaluation. For further details you can see: - The announcement of GSoC 2023: https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html - GSoC rules: https://summerofcode.withgoogle.com/rules - The detailed GSoC 2023 timeline: https://developers.google.com/open-source/gsoc/timeline - Elaborate project idea guidelines: https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list Thank you for your participation and help. Let's hope we attract some great contributors again this year. Martin