Google Announces Summer of Code 2008
morrison writes "The 2008 Google Summer of Code is on. We have discussed this four-year-old tradition before (2005, 2006, 2007). Google will once again be hosting a program that gives computer science students a $4,500 stipend to work on open source software projects. Last year, Google funded over 900 students' projects in more than 90 countries. As noted in the program FAQ, this year they hope to do even more. The #gsoc IRC channel on Freenode is already buzzing with activity."
My open source Visual Basic extension for Word 97 has been rejected 3 times already; I'm gonna try one last time.
--
WHO ATE MY BREAKFAST PANTS?
Obama needs some tweaks.
--
WHO ATE MY BREAKFAST PANTS?
Actually, Google Highly Open Participation contest produced some excellent pieces of code that were all submitted by "high school" students. If I didn't know better I'd say they were professional developers.
Fix the Firefox memory leak! No wait, something more realistic... how's about world peace?
The anti-ballistic-chair defense system. Google's going to need it some day.
Hail Eris, full of mischief...
E pluribus sanguinem
Thousand Parsec (a game framework for turn based strategy games) was one of the mentor organisations last year.
The effect on our project was really huge, not only did the students do some very cool work. We now have the creditability to approach Universities and help get their students involved with our project.
We already have one student working on Thousand Parsec as part of a high school internship and two students from the University of South Australia working on a Java MIDP client.
Thanks a huge amount to Google and the Summer of Code team, hopefully we can get in again this year and have even more fun!
Thousand Parsec - http://www.thousandparsec.net/
...is that enough resources get geared to having KDE 4.1 as complete as can possibly be. Guys, KDE 4 rocks and can be made better. Go guys.
I successfully participated last summer working with Nmap. Leslie (from Google) and Fyodor were wonderful to work with, and I hope I can get in again this year!
Great job, Google!
I don't think we'd make it into GSoC, but if you are into Python and Glade you should checkout Gladex. We're even a Featured Project on Launchpad.net! Gladex isn't in the Ubuntu or Debian repositories yet, but we do have a PPA going of an alpha release. Alternatively, you can download the stable packages directly.
.glade file created in the Glade User Interface Builder and generates code in Perl, Python, or Ruby. The generated code uses libglade to draw a GUI and is not raw pygtk code (support via a plugin is in development). Support for additional languages can be added through the plugin API.
Gladex is a Python application which takes a
Welcome to the land of the free...pay toll ahead...no photography...please open your bag...
I know from looking the last 2 years that the projects for both PSI and MythTV were accepted and started but never completed to a point where the maintainers put code into the full product.
Are there ANY success stories?
Are there ANY success stories?
Absolutely. My fellow SoC students and I participating with Nmap last year have lots of code in Nmap proper. And the years before that (Nmap has participated every year of the SoC) there were a whole lot of cool things added to Nmap proper from SoC work.
Agreed. I really need new ATI drivers. Neither the free drivers nor fglrx will allow me to suspend my laptop.
This is a bit of an urban legend at this point.
1 - Any complex app will likely have some memory leaks. The code has been very thoroughly examined and cleaned up for Firefox 3.
2 - Most "leaks" come from poorly written extensions/add-ons. Run without them and check out the difference.
3 - There is a feature in Firefox that you can easily turn off, that people mistake for a memory leak. Firefox keeps fully rendered versions of pages in memory, in addition to the standard cache on the hard disk. If you hit back, Firefox doesn't need to re-render the page. Browse a while, and Firefox will use up plenty of memory. If you don't like this behavior, then turn the feature off.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
Why? For most users, having fast (and accurate!) back/forward is more useful than having Firefox allocate less RAM. The feature even automatically turns itself off if you don't have a lot of physical RAM.
Turning off bfcache might be useful for rudimentary leak detection, but a proper leak-detection tool is less likely to be confused by fragmentation, other caches, or the OS simply not reclaiming memory that the application has relinquished.
The shareholder is always right.
> This isn't limited to computer science students.
Quite true, but why do Google restrict participation to students?
The first goal listed on their SoC FAQ is:
``Get more open source code created and released for the benefit of all''
So why exclude professional developers who could crank out code?
I would dearly like to take a two-month sabbatical from work and
concentrate solely on writing code. There are huge voids in the
provision of free astronomical tools that could be addressed. But
finances dictate otherwise.
Instead, vast swathes of time and money will be wasted as students
learn about version control, rediscover elementary mistakes and
become entrapped in the politics of open source.
Thanks for nothing, Google.
Quite a few FreeBSD SoC projects make it into the system or ports, or at least had some of their work help with it; a quick glance at the SoC wiki pages I see enhancements to libalias and ipfw (I think some of this eventually made it; we now have kernel NAT with ipfw), bsnmpd bridge monitoring, FUSE port, gvinum enhancements, GEOM storage virtualisation, Apple hardware support enhancements, and what became the name service caching daemon.
Other things may not have made it in, but were good research projects both for the project and for the students; FreeBSD now has a very functional port of OpenBSD's hardware sensors suite, though it wasn't accepted into base because of architectural concerns. gjournal started life as a SoC project, and while rejected it did help spur development of a new more functional one, and the student went on to produce gvirstor, the aforementioned GEOM storage virtualisation layer which *did* make it. The Linux KVM port got far enough to boot FreeBSD 7 as a guest and will hopefully continue development. I'm sure I've left lots out.
Just because a SoC project doesn't make it into a "product", doesn't mean that project wasn't a success. Even if it never produces something deployable, it's given a student some experience in development, it's given the project some interesting if not necessarily immediately useful code and it's helped lay groundwork for future development, even if it only does so by providing those concerned some experience.
BZFlag participated in the Google Summer of Code for the first time in 2007. Our participation was documented in this detailed article (Warning: 15 MB PDF).
Another higher-level summary was put together for a presentation and is available here (Warning: 5 MB PDF)
See the presentation for the quick introduction. I highly recommend the article to any students and projects/mentors that are seriously thinking about participating for the first time.
On the whole, it's a great opportunity for projects but you do have to put in a lot of time and effort. You have to have your act together. If you do, the students and the projects will both have a great time.
Cheers!
Sean