Weekly Edition
Return to the Press page
| |||||||||||||
Growing pains for Google's Summer of Code (Linux.com)
Linux.com looks at
some lessons learned from the second Summer of Code. "As the second
Google Summer of Code (SOC) winds down, most participants agree: the
program, which pays selected students to work on a free or open source
software (FOSS) project for three months, is a unique and exciting
opportunity, but needs to continue efforts to become more organized. Those
who were previously involved tend to agree that this year was less chaotic
than last year. However, whether they are organizers at Google or students
or members of mentoring organizations (the projects accepting students),
most participants this year also see the need for more structure. Many of
them also offer concrete advice about how participants can get more out of
the program if it happens next year."
(Log in to post comments)
Room for Improvement Posted Sep 18, 2006 17:05 UTC (Mon) by frlinux (guest, #27370) [Link] I wasn't involved at all in any of the past 2 years of the projects but as the news say, it has been improving from last year so I am sure Google is learning from its experience and making sure that it will just become better every year.
Growing pains for Google's Summer of Code (Linux.com) Posted Sep 18, 2006 22:28 UTC (Mon) by abhaykalla (guest, #40592) [Link] Google's summer of code project has many bugs at different levels. google doesn't interact with the students properly about what their expectations are. the programme doesn't specifically describe the goals and the coding methods that the programmers should use..
Growing pains for Google's Summer of Code (Linux.com) Posted Sep 19, 2006 5:55 UTC (Tue) by piman (subscriber, #8957) [Link] The projects are proposed and designed by the students; that's the intention.
Now, most students couldn't come up with a requirements list if it was tattooed on their arm, and couldn't design their way out of a paper bag. (Some can, and they produce good code during the SoC.) The "coding method" is whatever produces the best deliverables that fit your requirements, and your requirements are whatever you wrote in your project proposal.
In free software, no one tells you your goals or your methods; if you're starting a new project it's all up to you, and if you're working on an existing project, most of the time you'll have to argue your goals to the existing developers, and absorb their methods as you go. If you can't do that, then you can't be a good free software programmer.
|
|||||||||||||