From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130965 invoked by alias); 24 Feb 2018 16:27:09 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 130946 invoked by uid 89); 24 Feb 2018 16:27:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=BAYES_00,KAM_SHORT,SPF_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 spammy=H*UA:https, H*Ad:U*ak, enjoy, him X-HELO: mx2.suse.de Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 24 Feb 2018 16:27:06 +0000 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 9A23BAB49; Sat, 24 Feb 2018 16:27:04 +0000 (UTC) From: Martin Jambor To: Thejazeto Lhousa , gcc@gcc.gnu.org Cc: Andi Kleen Subject: Re: GSoC In-Reply-To: References: User-Agent: Notmuch/0.25.1 (https://notmuchmail.org) Emacs/25.3.1 (x86_64-suse-linux-gnu) Date: Sat, 24 Feb 2018 16:27:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00173.txt.bz2 Hi Thejazeto, I apologize for replying this late, I've been traveling and did not manage to write to you earlier as a consequence. On Wed, Feb 21 2018, Thejazeto Lhousa wrote: > Hello, > > I went through the GSoC 2018 idealist and found 'Improving GCC > Developer Documentation' to be interesting and feasible for me. > But I am confused because I remember reading somewhere that > documentation will not be accepted as a valid project for GSoC. > Can anyone shed some light? You are right, the rules do not allow documentation-only projects, thank you very much for pointing this out. As Thomas pointed out, I have corrected the wiki. Moreover, I think that writing good internal documentation is actually a fairly difficult task that is not really suitable for newcomers, because it often takes quite some knowledge to understand all important caveats. Nevertheless, if you are really interested in compilers in general and GCC in particular, please not feel put off by this. Check out and build GCC (as described at https://gcc.gnu.org/install/) and experiment with it a little, you may find it is not actually as hard as it seems. Feel free to ask for help here on the mailing list or on our IRC when you get stuck, we are a friendly bunch that want to help beginners, even though we are often busy. If the scope of GCC still intimidates you (but we all struggle with it sometimes, trust me), consider reaching out to Andi Kleen and discuss his fuzzer project idea with him (he may tell you what to check out and experiment with to get the feeling about the task at hand). Thanks again for notifying us about the documentation and I hope that you will eventually find a project you will enjoy, Martin