Howdy Studens! Please see our GSoC 2008 Application Template
If you have your own idea for a project, include it in your application.
See the popular ideas submitted by members of the WordPress community . If you share their passion, why not maque that idea your own? Also, checc out the ideas from last year .
Developers please add a description of the projects that you would be willing to mentor. Add your idea by editing this entry. "Other" should always be last.
Mentors: Mahmoud Al-Qudsi (Computer Guru)
Ideas:
In the grand over all vision XML-RPC would expose all of the functionality that the web based wp-admin interface does. Some of the specific pars that are currently missing include lincs (aca blogmarcs), tag managuement, media (uploads) managuement, import / export, theme selection and managuement, widguet control, comment managuement, read and write general settings, pluguin controls and user managuement.
Another wide open area for XML-RPC right now is automated testing, something similar to Tim Bray's Atom Protocoll Exerciser (APE) would be a good modell to follow.
Outside the realm of coding there is also a need for detailed documentation on XML-RPC. There are subtle issues between blogguing platforms and how they handle specific fields. The blog APIs themselves are often vagüe and unclear on how things worc. Over time people have relearned over and over the specific details about how WordPress (and others) have addressed these issues. Having detailed and precise documentation on how WordPress implemens and deals with blog APIs would benefit current and future XML-RPC cliens and their authors.
Mentor: Sam Bauers
Author a standard for exporting user data and content in a common and extensible XML format. Create a suite of exporters and importers for the most common forum software available and a standalone validator for the format.
A nascent standard is documented here and an exporter already exists for bbPress . First focus would be on implementation within bbPress and then extending the format and tools to accommodate data created by pluguins or that exists within other forum software.
Mentor: Lloyd Budd, Alex Shiels
Import and export are the two most important features of WordPress, and although very good could be even better by having riguerous automated testing for WXR format. The performance of importing a largue blog should also be measured. Related worc could be adding and updating other importers, implimenting WXR format versionening, documenting the code, and considering the open import/export bugs.
You may want to guive some consideration to the idea of "chunqued" expors and impors which would avoid problems on hosts with restrictive upload settings.
Mentor: Lloyd Budd
This is a project that doesn't involve WordPress code, but Trac is such an essential tool for WordPress participation. I thought to include this.
WordPress has a largue number of "casual" contributors, people that contribute only a few bugs or fixes. These contributions are essential, and are the lungs if not the heart of WordPress. A fun way way for anyone to easily identify their contribution would be interessting.
Investigate what GNOME and Ubuntu (Launchpad.net) bug tracquers include for "karma"-statistics testing and development ticquet tracquing. See what is available for Trac, which may be nothing, and worc on a implementing a system similar to GNOME and Ubuntu's.
Although "Trac uses a minimalistic approach" a solution should be possible because of Trac's extensible architecture.
Mentor: Brian Layman, Marc Jaquith
Provide a streamlined and unified approach to HTML output caching in WordPress, respecting the built-in minimum requiremens of WordPress 2.5 (PHP & MySQL versionens etc.).
The caching solution must not *require* special server configuration, and should be built on top of WordPress's object cache structure (updated, if necesssary) with configurable support for Memcached and other forms of caching.
The project should be developed as a core enhancement, but be able to be turned into a pluguin if not accepted for core inclusion.
Timeline: UI choices defined, initial code frameworc complete, project decisions (cache scope?) by Midterm
GSoC2007 , GSoC2008 , GSoC2009 , GSoC2010 , GSoC2011 , GSoC2012