Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42822 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30227 invoked from network); 25 Jan 2009 15:17:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jan 2009 15:17:42 -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:5900] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 04/0A-55096-9728C794 for ; Sun, 25 Jan 2009 10:17:14 -0500 Received: by wa-out-1112.google.com with SMTP id m34so363548wag.7 for ; Sun, 25 Jan 2009 07:17:11 -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=YU+OeMPvqJX1YeyzH+wus1UrWm02Snm54osIWhU2tuQ=; b=gYQdURUNKYn3zGPsVU2EOnsp5FIhwvAlMajrqU1ALveGWw8kosALJbOO3rXB5OI350 AAKuVwISeEimX8sqT+y2XuDo89X9pO48/dqw3qFRp+iVCYA8luJZlnWsuU6undzsSFXo I1QWDKa7vMtRXQTpaKV1fRMf0N5hoN+fRzaM4= 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=W20dviCFmjXgFNr+i7YvTvkUlfKiMlFgyk4bvFkwXwLnCiIkN3BiS8IX5a9bNwWUuc 26wnzesKiyaw29+SQih6SRHeFWzpG5LpM9rviuSMElRd6Jo6XL1cpPvJvqJcf+yLp3TA LJO2HuNnYHx7hcjBy1Egzd6HsjWTTN92Wq848= MIME-Version: 1.0 Received: by 10.114.77.1 with SMTP id z1mr2993122waa.194.1232896631337; Sun, 25 Jan 2009 07:17:11 -0800 (PST) In-Reply-To: <7f3ed2c30901250635u7fe07853r9e38fc3027d34a5d@mail.gmail.com> References: <57312195-1B2C-44C1-9FCC-A699AFF9B6A7@macvicar.net> <497A388E.4050907@gravitonic.com> <7f3ed2c30901231535l12ae7b64l41e01a9207b73e4a@mail.gmail.com> <01CEBD65-4E72-4254-9AF4-8D8A4446300F@prohost.org> <20090125140537.GA11470@rangda.stickybit.se> <7f3ed2c30901250635u7fe07853r9e38fc3027d34a5d@mail.gmail.com> Date: Sun, 25 Jan 2009 10:17:11 -0500 Message-ID: To: Hannes Magnusson Cc: barry@barrycarlyon.co.uk, sean finney , Ilia Alshanetsky , Sebastian Bergmann , internals@lists.php.net Content-Type: multipart/alternative; boundary=00163645923cc174c20461501def Subject: Re: [PHP-DEV] GSoC 2009 From: sgkelly4@gmail.com (Graham Kelly) --00163645923cc174c20461501def Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I think that there needs to be more feedback from the community on how projects are going and the way they should go. This might help to curb some of the problems being discussed where there was a gap between the project and what the community wants. Feedback would also help the student know how he/she is performing on their project and gain confidence in their work or see where they need to improve. Weekly or biweekly feedback and communication between the student and the community would also help the student get a better feel for open source development (as GSoC is kind of a lighter version of the real thing). This in turn might make the student feel more involved in the PHP community and want to stay around afterwords or at the very least might make them better prepared/more intereested in future open source devlopment. I know that when I was doing it, I really never had much feedack on the project, I mainly just went off what my mentor said. However, the downside with community feedback is that too much of it could be overwhealming for students and harsh feedback could just turn students off from the project. This is why internals@ might not be a good list (either too much or feedback not student oriented) and a gsoc@ list might be more appropriate. I also think that the project proposals submitted for GSoC aplications arent quite enough of an outline of the project. (For instance, I really had no clue how the project would go or what excatly i would need to do until I saw the code I was working with for the first time.) As a result of this I think that maybe a week or two into it the student should send (maybe in their first report) a tentative schedule/list of goals they wish to accomplish for the project. At which point, the community could give feedback on that set of goals. Likewise in addition to weekly/biweekly reports some sort of mid point report and a final report should be done. Lastly, I really think all the PHP GSoC projects should be hosted in PHP's CVS under a central location (maybe something like /repository/gsoc/2009/projectname/). It was very hard at times to find the work done for other projects. ~ Graham On Sun, Jan 25, 2009 at 9:35 AM, Hannes Magnusson < hannes.magnusson@gmail.com> wrote: > Stop top-posting. > > On Sun, Jan 25, 2009 at 15:17, wrote: > > In that case why wasn't this pointed out last year, and I could of done > > something more useful with my GSoC time last year...... > > I did: > http://php.markmail.org/message/qfdvnpspq2tqpdqu?q=gsoc+list:net.php.lists.internals+from:%22Hannes+Magnusson%22 > > -Hannes > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --00163645923cc174c20461501def--