2 | | Codex |
3 | | |
4 | | Codex tools: Log in / create account |
5 | | GSoC2010 |
6 | | Contents |
7 | | [hide] |
8 | | |
9 | | * 1 Google Summer of Code 2010 |
10 | | o 1.1 Ideas |
11 | | + 1.1.1 Dashboard "Setup Completion" Module |
12 | | + 1.1.2 Bug Tracker! |
13 | | + 1.1.3 Add AJAX Paging to Admin Screens |
14 | | + 1.1.4 Sort by Columns |
15 | | + 1.1.5 Blog Import/Export |
16 | | + 1.1.6 Template Versioning |
17 | | + 1.1.7 Comment Moderation |
18 | | + 1.1.8 Media |
19 | | + 1.1.9 Move WordPress |
20 | | + 1.1.10 Enhance Profiles.WordPress.org |
21 | | + 1.1.11 Full-Throttle Trac Annihilation |
22 | | + 1.1.12 Progress Bars |
23 | | + 1.1.13 BuddyPress |
24 | | + 1.1.14 GlotPress |
25 | | + 1.1.15 bbPress |
26 | | + 1.1.16 Other Ideas |
27 | | o 1.2 Mentors |
28 | | + 1.2.1 Drop-in Mentors |
29 | | o 1.3 How to Apply |
30 | | o 1.4 See Also |
31 | | |
32 | | Google Summer of Code 2010 |
33 | | |
34 | | Howdy Students! Though we are just getting started with our materials for 2010, you can get a head start by checking out information from previous years. Please see our GSoC 2010 Application Template, and last year's ideas. The very best way to up your chances of being selected for a project is to start learning the WordPress code base now, get familiar with the development process, and submit a couple of patches so we can get an idea of your abilities. We've also listed some resources for getting started on our GSoC home page. |
35 | | |
36 | | Note: Ideas should only added to this page by approved mentors, as they can only be taken on with a mentor to supervise. If you would like to propose an idea for a student to do, please suggest it to the core team to see if it's something they want to pursue (try wp-hackers, wpdevel.wordpress.com, or the IRC chat at irc.freenode.net #wordpress-gsoc or #wordpress-dev). If you want to propose ideas for WordPress in general, please do so at the Ideas forum. |
37 | | Ideas |
38 | | |
39 | | If you have your own idea for a project, include it in your application and describe it thoroughly. |
40 | | |
41 | | Know you want to propose a GSoC project around WordPress, but aren't sure what you want to do? Below are a few ideas we think would work well as GSoC projects. Also see the popular ideas submitted by members of the WordPress community. If you share one of their passions, why not make that idea your own? Also, check out the ideas from last year. |
42 | | Dashboard "Setup Completion" Module |
43 | | |
44 | | This is an idea that's been suggested many times and it never seems to make it into a release. We'd love for someone to take this one. When you first set up a WordPress site, there are certain steps you have to go through. Pick a theme, change your password, edit your tagline, choose your comment settings, etc. It would be great if on the Dashboard screen there was a module that kept track of how many of these things you've done, and marked off your progress, much as LinkedIn does when you set up a profile. Each successive login would offer the user an option to finish/enhance their site setup by completing another thing(s) they haven't gotten around to yet. |
45 | | Bug Tracker! |
46 | | |
47 | | Have you ever wished for a bug tracker that was built on WordPress? Every now and then when we feel pain using Trac, we look around but never see anything better. Some of the core contributors think that a very decent issue tracking system could be built on WordPress, allowing us to have complete control over the tool we use to manage the development of our, well, publishing tool. Some features would include creating tickets, assigning owners and reviewers, milestones, etc. (look at our Trac setup to see what we've got now). We'd need SVN tie in for commits as well. Depending on the scope of the project, someone else could write the SVN part if you just write the bug tracking application on WP. |
48 | | Add AJAX Paging to Admin Screens |
49 | | |
50 | | Something we've never gotten around to is adding AJAX paging to the list-type screens (edit.php, etc). Currently, getting to the next page of items means a screen refresh. For this project, add ajax paging to all the list-type screens in the WordPress admin. We have all the underlying PHP, but it needs some JavaScript love. |
| 3 | From GSoC ideas list: |
| 4 | >Add AJAX Paging to Admin Screens. Something we've never gotten around to is adding AJAX paging to the list-type screens (edit.php, etc). Currently, getting to the next page of items means a screen refresh. For this project, add ajax paging to all the list-type screens in the WordPress admin. We have all the underlying PHP, but it needs some JavaScript love. |