Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42782 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2786 invoked from network); 22 Jan 2009 15:53:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jan 2009 15:53:34 -0000 Authentication-Results: pb1.pair.com header.from=sgkelly4@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=sgkelly4@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.178 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: sgkelly4@gmail.com X-Host-Fingerprint: 209.85.146.178 wa-out-1112.google.com Received: from [209.85.146.178] ([209.85.146.178:54396] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/51-15341-B7698794 for ; Thu, 22 Jan 2009 10:53:31 -0500 Received: by wa-out-1112.google.com with SMTP id j32so2572436waf.7 for ; Thu, 22 Jan 2009 07:53:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=26MQpXLpSj1dvP3CJEvdkuk6K664y66HoSHRwMUbzR8=; b=dASF+bxvce0LpLlJ7jrXwA4ZRzpuR9LCQ0ySEPnyewOYIJThXFPtYKh321s2BgzDRr NwHP7vPWfUEN2dZE6Uvh7GIV1rgWDn54859k8XZoCE3r/lDDPK0cRFJDR522BLrYj76x ZWONdkdMWK11RMQ4gYeHMhww6297CvxPydsDc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XVJcl31gWhb/VpPWyYU5lcfGadU1ksWaGuljwPbZeF6XWx3jAy4FlT4wazJrriIyzs 8jLioeeut5nKRFlVqs7XaDeOUVevlNVWyfvaw3dwK5MW5XzHECnWe6vrKNHZ9GEWMiB8 LwjgphyLfo5YpXR4/tzghejobZFFOD9qN9/6Q= MIME-Version: 1.0 Received: by 10.114.72.1 with SMTP id u1mr5320189waa.203.1232639608083; Thu, 22 Jan 2009 07:53:28 -0800 (PST) In-Reply-To: References: <57312195-1B2C-44C1-9FCC-A699AFF9B6A7@macvicar.net> <4C.C5.19181.B1AA7794@pb1.pair.com> <7f3ed2c30901220004q5838862fw711fc6d2482c05a@mail.gmail.com> Date: Thu, 22 Jan 2009 10:53:28 -0500 Message-ID: To: Pierre Joye Cc: Hannes Magnusson , Elizabeth M Smith , internals@lists.php.net Content-Type: multipart/alternative; boundary=001636417c17f9d6af04611445c5 Subject: Re: [PHP-DEV] Re: GSoC 2009 From: sgkelly4@gmail.com (Graham Kelly) --001636417c17f9d6af04611445c5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, As a former GSoCer I think the php-gsoc@ mailing list would be a great idea. One thing I noticed was that I really had no idea how most other studen't projects were going besides the few that poped into IRC from time to time. Another advantage of the php-gsoc list is that the internals list can be a bit much when just starting out. I remember all of a sudden getting tons of emails, most of which didn't havy any impact on my project. A GSoC specific list would probably help that and make things easier for the students (though, reading internals can be quite interesting at times and worth it for GSoC students doing internals work :D). This list could also be used as a place for potential students to ask questions, propose GSoC ideas and get to know the GSoC oriented portion of the PHP community. As mentioned by others, I think the weekly or bi-weekly report is a great idea. It would really help keep everyone informd as to whats going on. Also, more detailed project descriptions would be nice. It was kind of hard to know what to write a proposal on for just a two sentance description of the project. ~ Graham Kelly On Thu, Jan 22, 2009 at 4:38 AM, Pierre Joye wrote: > On Thu, Jan 22, 2009 at 9:04 AM, Hannes Magnusson > wrote: > > On Thu, Jan 22, 2009 at 00:03, Elizabeth M Smith > > wrote: > >> I think we really should encourage at least two active mentors for each > >> project this year. I think it helps both the students (always someone > >> to annoy) and the mentors (less stress and time out of their lives) and > >> provides a safety net if a mentor has real life issues come up. But for > >> that we need more people willing to mentor ;) > > > > If we create a "php-gsoc@" mailinglist where all the students and > > mentors, and everyone else who wants to follow the student work, and > > require students to post weekly/by-weekly status updates then there is > > no need. The community can then help the mentor out and we get more > > information about the projects. > > > > I still don't know what happened to many of the gsoc projects last > > year, despite my multiple inquires to the mentors of the projects, and > > haven't heard a beep from most of the students :( > > > > Lets keep it in the OSS style. Communicate in the open. > > Agreed. > > As a sidenote, the wiki has an account request system, simply request > an account if you do not have yet one and likes to propose ideas. > > > Cheers, > -- > Pierre > > http://blog.thepimp.net | http://www.libgd.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --001636417c17f9d6af04611445c5--