Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22779 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13836 invoked by uid 1010); 15 Apr 2006 06:46:36 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13820 invoked from network); 15 Apr 2006 06:46:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2006 06:46:36 -0000 X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.5 (sometimes 2.4) (4) Received: from ([204.11.219.139:49809] helo=lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id EA/BF-19715-BC690444 for ; Sat, 15 Apr 2006 02:46:36 -0400 Received: from [192.168.200.106] (c-24-6-5-134.hsd1.ca.comcast.net [24.6.5.134]) (authenticated bits=0) by lerdorf.com (8.13.6/8.13.6/Debian-1) with ESMTP id k3F6kVFp017132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 14 Apr 2006 23:46:32 -0700 Message-ID: <444096C7.8000104@lerdorf.com> Date: Fri, 14 Apr 2006 23:46:31 -0700 User-Agent: Thunderbird 3.0a1 (Macintosh/20060404) MIME-Version: 1.0 To: Lukas Smith CC: internals References: <44405E58.8040808@lerdorf.com> <44409342.4030706@php.net> In-Reply-To: <44409342.4030706@php.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Summer of Code From: rasmus@lerdorf.com (Rasmus Lerdorf) Lukas Smith wrote: > Rasmus Lerdorf wrote: >> Google is doing their Summer of Code thing again this year. You can >> read more about it here: http://code.google.com/summerofcode.html > > A few days ago I started a wiki for PEAR to get organized for this. But > not much content has been generated so far. Only some ideas have been > kicked around (latest: adding an optional PHP4<->PHP5 E_STRICT converter > to the PEAR installer ;) ). > > Anyways .. obviously we are missing a foundation, but maybe we can > squeeze in somehow. Should we coordinate this, or should each subproject > of php.net try to get in on its own? I think we can lump them all together under PHP. And while having suggestions is definitely good, we also need to stay open to interesting proposals. -Rasmus