From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20851 invoked by alias); 26 Feb 2009 14:25:34 -0000 Received: (qmail 20825 invoked by uid 22791); 26 Feb 2009 14:25:32 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from e24smtp01.br.ibm.com (HELO e24smtp01.br.ibm.com) (32.104.18.85) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 Feb 2009 14:25:27 +0000 Received: from d24relay01.br.ibm.com (d24relay01.br.ibm.com [9.8.31.16]) by e24smtp01.br.ibm.com (8.13.1/8.13.1) with ESMTP id n1QEXmnr031127 for ; Thu, 26 Feb 2009 11:33:48 -0300 Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by d24relay01.br.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n1QFOkDc3960860 for ; Thu, 26 Feb 2009 12:24:46 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n1QEPLhj000975 for ; Thu, 26 Feb 2009 11:25:21 -0300 Received: from [9.8.9.116] ([9.8.9.116]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n1QEPJKl000666 for ; Thu, 26 Feb 2009 11:25:21 -0300 Subject: google summer of code From: Thiago Jung Bauermann To: gdb ml Content-Type: text/plain Date: Thu, 26 Feb 2009 14:25:00 -0000 Message-Id: <1235658320.5890.18.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00163.txt.bz2 Hi, I was wondering whether we want to participate in the Google Summer of Code. The application period for mentoring organizations is from March 9 until March 13th, so now is a good time to decide if it will be beneficial for us. I think two benefits that we get from the program are: 1. possibility of attracting new gdb developers and 2. a helping hand for features we want to develop. There are some disadvantages too. From what I read, the main problem is that mentoring a student takes some time and effort. From the GSoC Mentors Wiki: "However talented the students are who you may select, they will require significant attention from your developers, so release schedules and the desire of your community to be supportive are important considerations. Many organizations have found great rewards in mentoring, but most agree that they underestimated the amount of time that mentoring requires. As a potential administrator you should also consider that you will be responsible for getting reports and forms in to the GSoC website on time. You should make sure that your potential mentors realize that they will need to take time to evaluate students at the mid and final points of the 12 week period. Failure to meet the reporting requirements or mentoring requirements of GSoC is a serious infraction, and reflects poorly on your organization. If you have a big release coming out during the summer that will require all hands, you may wish to reconsider applying." We have some ideas for projects that a student could implement in: http://sourceware.org/gdb/wiki/ProjectIdeas Some that may be worth considering for this: 1. Help with Python scripting support; 2. Help with reversible debugging (not sure if teawater and Michael need a helping hand there); 3. Support pipes in the run command (this may be too small for a GSoC); 4. Support tracepoints in gdbserver. There may be some wishlist bugs in the bugzilla that we could lump together with 3. to keep someone busy for the summer... Some pointers about the GSoC: Main page: http://code.google.com/soc/ FAQ: http://code.google.com/opensource/gsoc/2009/faqs.html Mentors Wiki: http://gsoc-wiki.osuosl.org/index.php/Main_Page -- []'s Thiago Jung Bauermann IBM Linux Technology Center