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.magnus...@gmail.com> wrote: > Stop top-posting. > > On Sun, Jan 25, 2009 at 15:17, <ba...@barrycarlyon.co.uk> 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 > >
