Return-Path: Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: (qmail 78386 invoked from network); 9 Feb 2010 08:19:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Feb 2010 08:19:48 -0000 Received: (qmail 51565 invoked by uid 500); 9 Feb 2010 08:19:48 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 51461 invoked by uid 500); 9 Feb 2010 08:19:47 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 51450 invoked by uid 99); 9 Feb 2010 08:19:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 08:19:47 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [82.71.204.226] (HELO cpanelsmarthost2.zen.co.uk) (82.71.204.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 08:19:37 +0000 Received: from [82.71.204.9] (helo=zencphosting06.zen.co.uk) by cpanelsmarthost2.zen.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1NelJV-0007cg-Hc for dev@community.apache.org; Tue, 09 Feb 2010 08:19:17 +0000 Received: from 5e0385ac.bb.sky.com ([94.3.133.172] helo=[192.168.0.5]) by zencphosting06.zen.co.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NelJV-0008Le-BX for dev@community.apache.org; Tue, 09 Feb 2010 08:19:17 +0000 Message-ID: <4B711A83.30500@apache.org> Date: Tue, 09 Feb 2010 08:19:15 +0000 From: Ross Gardler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: dev@community.apache.org Subject: [proposal] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zencphosting06.zen.co.uk X-AntiAbuse: Original Domain - community.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - apache.org X-Virus-Checked: Checked by ClamAV on apache.org How are we to collect mentor projects for GSoC? In the past we have used a wiki page and had the mentors add their projects to that page. This has worked well and is close to zero overhead on our the admins part. However, it requires a duplication of effort for the mentors and is not useful beyond the GSoC period. What I would like to do is make the information we collect at this stage of GSoC useful for our ongoing mentoring work that we intend to kick off after GSoC. I therefore propose that we ask projects to record tasks in their issue tracker with a label of "Mentored". We can then pull this information into the community.a.o site via the JIRA search widgets (I think, I need to verify this - if not we can always point at a filter on JIRA). Unfortunately GSoC is only about code so some projects that we can provide mentors for are not suitable for GSoC (i.e. documentation) therefore I also propose to use the label "GSoC" for mentored projects available to GSoC students. After GSoC this list of projects with mentors available will still be useful to both the ComDev project and the development project. Some projects already use labels to indicate tasks suitable for newcomers, i would rather than adopt multiple labels that will require us to aggregate various searches. We've mentioned this before and were in initial agreement. I'm therefore going to go with lazy consensus on this to allow us to get on with preparing for GSoC. I'll conduct the necessary experiments whilst I wait for objections. Ross