I submitted our application to be a participating organization in the Google Code-in.
We need to compile the task list. I put in some high-level placeholders for now, but people should go ahead and add suggestions for tasks. Note that the final task list will be pruned down to those tasks that are approved by the core leads and that have appropriate people available to oversee them, to ensure a positive outcome for the students and that we’re not wasting anyone’s time. If you want to suggest a task, leave it in a comment here. Specify if you are also offering to mentor any student taking on that task, or if it’s just something you think should get done. As tasks are agreed upon and have mentors assigned to them, I’ll add them to the codex page.
Ryan McCue 7:21 am on October 29, 2010 Permalink |
I’ll see if I can think up some to add to Code.
Peter Westwood 7:47 am on October 29, 2010 Permalink |
[Code Documentation] – Document each of the XMLRPC functions which isn’t phpDocumented with details of the arguments it accepts. Similar to what has been done in r16046 for the new functions in 3.1
Will happily mentor this task
Ryan McCue 8:11 am on October 29, 2010 Permalink |
If I get in, I’ll also happily take this task. Should be fairly easy.
Ryan McCue 7:55 am on October 29, 2010 Permalink |
Here’s some non-code ones. Haven’t added to the codex yet, since I’d prefer someone to look over it first.
[Documentation] – Document api.wordpress.org’s methods and usage of them.
I’ve been meaning to do this for a while (even have Dion’s original code for this), but haven’t had the time.
[Research] – Investigate whether WordPress can use Git/GitHub more effectively. Possibly things like being able to take patches via Git forks, etc.
[Research] – Investigate existing solutions for bug tracking using WordPress. I’ve heard rumours of replacing Trac at some point, so it’d be a good idea to look at what already exists out there.
Andrew Nacin 4:04 pm on October 29, 2010 Permalink |
I like the api.wordpress.org idea. I’m sure a lot has changed since then; I can provide the relevant current code to the student(s) on this.
PJ Hyett 6:47 pm on October 29, 2010 Permalink |
I saw this comment appear in my backtype feed. If anyone would like to chat about Git/GitHub integration, we’re here to help.
Andrew Nacin 3:58 pm on October 29, 2010 Permalink |
I intend to curate a list of bug reports and needed UI patches (CSS3 gradients plz), and head up mentoring for that.
Alex Hempton-Smith 7:34 am on November 1, 2010 Permalink |
I’d happily take these tasks if I got in. Been meaning to make a patch to replace all the gradient images for ages anyway.
duck_ 8:51 am on November 3, 2010 Permalink |
Some task suggestions:
[Documentation] Still a load of Multisite documentation missing (see #14953 if not finished for 3.1) and a large number of doctags marked (pretty uselessly) as unknown (e.g. @since unknown)
[Quality Assurance] Do a theme review (or more). I’m sure the theme reviewers would appreciate some help.
[Translation] Translate a very popular plugin which is currently available in few languages (would probably want cooperation of the plugin developer). Might include patching to actually allow for translatability, depends on the plugin.
Also mentioned to nacin the possibility of a task for the still upcoming API docs (maybe more UI?), but not too sure.
Also offering my time and help as a mentor.
Gautam 7:43 am on November 4, 2010 Permalink |
I had a chat with jjj, and here are some tasks which we discussed:
[Code]
User Profile/edit page
Anonymous posting
Widgets (latest/popular/etc topics/replies/forums)
Email subscriptions
User favorites
Topic status – closed/open/sticky/etc
Forum is category option
John James Jacoby 7:45 am on November 4, 2010 Permalink |
Looks good. (These are for the bbPress plugin by the way.)