Make WordPress Core

Tagged: gsoc Toggle Comment Threads | Keyboard Shortcuts

  • Jen 7:15 pm on April 21, 2014 Permalink
    Tags: gsoc,   

    GSoC students announced! https://make.wordpress.org/community/2014/04/21/gsoc-students-accepted/

    (core projects are the minority this year, which is why I posted over on the community site under mentorship programs)

  • Jen 5:25 pm on March 10, 2014 Permalink
    Tags: gsoc,   

    GSoC IRC Chats 

    The application period opens today and closes on March 21. Between now and then, we’ll set up a handful of IRC chats starting this Wednesday (We’ll use #wordpress-gsoc so as not to distract from the beta work in -dev, and won’t get too close to the dev chat time-wise) to allow some real-time chatting with potential students about their project ideas.

    All mentors should sign up for at least one time slot so the students will know which chat time will have appropriate mentors in the room. Everyone is welcome to attend these chats, not just mentors.

    I’d like to pick 2 times of day and do the chats on Thursday the 13th, Saturday the 15th, Tuesday the 18th, and Thursday the 20th. 21:00 UTC seems to work well for dev chat, so I’m thinking that could be one of the times, but would like a 2nd time that we could do at least once or twice to make it easier on anyone on Australia/Russia side of the world.

    Mentors: Please leave a comment with which days/times you can be available for chats in IRC. If anyone has an idea for a good 2nd chat time, suggestions welcome.


    • Bryan Petty 6:00 pm on March 10, 2014 Permalink | Log in to Reply

      I’ll be at WC Atlanta, leaving the 13th and back on the 16th. I’m pretty sure I won’t be available for the 13th, but might still be able to fit the 15th in. I can commit to the 18th and/or 20th though.

      An Australian/Russian friendly time is certainly a good idea, since GSoC always seems to actually be hugely popular with colleges in India.

    • Ian Dunn 6:13 pm on March 10, 2014 Permalink | Log in to Reply

      21:00 UTC on the 18th works for me.

      (The 13th and 20th would also work if necessary, but the 18th would be a little better.)

    • Aaron Jorbin 6:25 pm on March 10, 2014 Permalink | Log in to Reply

      13th and 20th work best for me.

      13th – 19:00 UTC till 23:59 UTC work best

      20th – 15:00 UTC til 05:00 the next day UTC works best

      I’m not sure there is a time that is good for Russia, East Coast USA and Australia. 0500 is one idea. It’s only 1am on the US East Coast, while being 4pm in Sydney and 9am in Moscow.

    • George Stephanis 9:17 pm on March 10, 2014 Permalink | Log in to Reply

      Most anytime — I’ll be around. :)

    • Yoav Farhi 8:08 am on March 11, 2014 Permalink | Log in to Reply

      The 18th on 21:00 UTC or earlier.

    • Marko Heijnen 8:45 am on March 13, 2014 Permalink | Log in to Reply

      All other dates then today works for me.

    • Eric 4:30 pm on March 14, 2014 Permalink | Log in to Reply

      I’m game for Tuesday the 18th, and Thursday the 20th

    • Aaron Douglas 7:37 pm on March 14, 2014 Permalink | Log in to Reply

      Tuesday the 18th and Thursday the 20th are good for me

  • Jen 7:00 pm on February 24, 2014 Permalink
    Tags: gsoc,   

    We’ve been accepted as a mentoring organization for GSoC! Now comes the work of interacting with potential students on wp-hackers (let’s try to be responsive, and nice) and in #wordpress-dev and #wordpress-gsoc (I’ll set up a few scheduled chats soon, but idle in the channel if you can to field questions) during the application period. Mentors, I’ll contact you within the next couple of days to set up chat times and discuss the application review process.

    Thanks to everyone who helped get our Ideas page filled!

  • Jen 6:16 pm on February 13, 2014 Permalink
    Tags: gsoc,   

    GSoC 2014 Application Status 

    I’ve submitted our GSoC application. If anyone is interested in seeing the essay/short-answer questions they ask and how I answered them, I posted that part of the application over at https://make.wordpress.org/community/2014/02/13/gsoc-2014-application/

    If you haven’t posted an idea to the codex page https://codex.wordpress.org/GSoC2014 but have time now, go ahead and add it. More ideas = more possible students applying for something that grabs their attention. Also, Google will be reviewing applications Feb 17-21, so adding more ideas (don’t forget to use the template and provide description) between now and the 17th is especially helpful. Not having enough ideas is why we didn’t get accepted in 2012.

    Google will announce participating organizations on February 24.

  • Jen 7:01 pm on February 7, 2014 Permalink
    Tags: gsoc,   

    GSoC: Now’s the Time 

    Hey all. I created our org profile for GSoC and have started filling out the application. Before I submit it, our ideas page needs to be bursting with project ideas and potential mentors. To that end, if you are interested in mentoring (co-mentoring a specific student, or just being a casual helper-outer in our gsoc channel when the time comes), let’s get you listed and get those project ideas posted.

    Go to https://codex.wordpress.org/GSoC2014 and log in to the codex (your wordpress.org u/p). You will see that I’ve made a template for posting project ideas. Just click the Edit link next to Ideas or next to the template labeled “Project Idea (copy this section, paste below…”, and add your idea to the list below the ones that are there. I filled in one for the standard Full-throttle Trac Annihilation idea using the template so there would be at least one example there for the first poster.

    Post as many good ideas for projects as you can think of. Make sure they are substantial enough to constitute a full-time summer job for the student, but not so grand that they won’t be able to finish in 3 months. Note that we always require their working prototype by midterm, so really they should be able to do the primary coding in 6 weeks, with the 2nd 6 weeks for revision, documentation, testing, merging, etc.

    Mentors who volunteered on the last thread have been posted in the Mentors section, but you should go in and edit your description to give some info about you, your areas of interest, etc. All mentor names should link to their wordpress.org profiles, as you see with the ones I’ve already posted. If you’d like to link to your own personal site for more info, please do so in the description rather than linking your name there.

    It says please don’t edit the mentors section without talking to me first. If you have been a previous mentor for GSoC (or have been listed as mentor before but didn’t wind up with a mentee), consider yourself as having talked to me and go ahead and add yourself to the list/edit your description. If you have never gone through the GSoC process before, please ping me in irc so I can review stuff with you (expectations, etc) before officially putting you on the list.

    If folks could start adding to this page now and continue over the weekend, then by Monday we can do a review to see if there are big gaps where I need to go mentor-hunting before submitting the application.


  • Jen 6:20 pm on January 29, 2014 Permalink
    Tags: gsoc,   

    GSoC 2014 

    It’s that time of year again, when all good* core developers start thinking about whether or not they’re up for mentoring a GSoC student this year. Many in this group know the drill, but there quite a few involved core contribs active this cycle who haven’t been involved with GSoC before, so here’s the deal:

    • Google pays for a program that gives college students summer jobs creating open source code under the mentorship of an organization (like WordPress).
    • We apply to be a mentoring organization and put up a list with a bunch of potential summer project ideas and identify who the mentors might be.
    • If we’re chosen to participate, we get a certain number of slots to fill, and students submit applications to work with us.
    • All the potential mentors rate/rank the proposals, and decide if there’s someone they’d like to mentor.
    • In game of chance-meets-requests dizzy enough to rival medical school matches, we put together our wish list for mentor-student matchups. 2 mentors per student, to provide coverage and make things more collaborative.
    • We hope that none of our top picks also applied to other orgs who accepted them, and wind up with our student roster.
    • We provide volunteer mentors to work one-on-one with the kids on projects that they applied to do over a 3-month period.
    • Open source code is released into the wild.

    I’ll be putting together our application to be a mentoring organization this week, so it’s time to start thinking of project ideas we could suggest on the Ideas page that we need for the application (the more ideas the better) and who wants to be a mentor. The application deadline is February 14, so I’d like to get the Ideas list in solid shape (along with mentor bios) by Feb 10 (a week from Monday).

    If you have an idea or are interested in being a mentor, please leave a comment on this post. At the end of the dev chat after 3.9 business is out of the way, we can discuss some of the ideas and I can answer any questions people have about mentoring.

    Related: I’m also going to be posting soon about starting up a regular mentorship program, as outlined here. But that can wait for another day.

    *Where good means both skilled and kind and generous with their time.

    • Jen Mylo 6:22 pm on January 29, 2014 Permalink | Log in to Reply

      Also, will need a few people to identify tickets that no one’s working on that would be good ones to use for the “submit a patch” requirement of the application.

    • Ian Dunn 6:59 pm on January 29, 2014 Permalink | Log in to Reply

      Is it only open for Core, or can Meta, Mobile, etc also propose projects?

      • Andrew Nacin 7:10 pm on January 29, 2014 Permalink | Log in to Reply


        • Ian Dunn 7:54 pm on January 29, 2014 Permalink | Log in to Reply

          Awesome. @jenmylo, I’d be happy to mentor someone if you have any Community projects you think would be a good fit for GSoC.

          • Jen Mylo 8:41 pm on January 29, 2014 Permalink | Log in to Reply

            @iandunn: Definitely, just need to make sure that it’s something releasable, like a plugin vs building onto one of the sites. Maybe forms, finally?

            • Ian Dunn 9:04 pm on January 29, 2014 Permalink

              That could work. The idea of having the pre-defined forms for speakers/sessions/etc is specific to WordCamp.org, but we could easily put the general architecture for a pre-defined form into the plugin itself, and then define WordCamp.org’s specific forms via a filter in a custom plugin.

              The result from that approach would be the same as if the our forms were built into the plugin itself, but it would keep the core plugin independent so it could be released in the WordPress.org repo and used by anyone.

              We don’t necessarily have to release it in the wporg repo in order to open-source it, though. Most of WordCamp.org’s custom stuff is already open-sourced in the Meta repo. Not sure if the GSoC guidelines just want it open-source, or if the spirit of it is to make it easily available/useable for others.

    • Wojtek Szkutnik 7:48 pm on January 29, 2014 Permalink | Log in to Reply

      Always happy to help with mentoring if needed :)

    • Marko Heijnen 8:48 pm on January 29, 2014 Permalink | Log in to Reply

      I would love to mentor. Hopefully this time I’m more lucky then last year. I can help with core, mobile or GlotPress.

      • Jen Mylo 9:20 pm on January 29, 2014 Permalink | Log in to Reply

        If you can write up some specific project ideas that you would like to mentor, that will help with the luck. Someone who applies for your idea would likely be given to the person who proposed it, vs running into a situation like last year where a handful of people all requested the same student.

    • Justin Shreve 9:28 pm on January 29, 2014 Permalink | Log in to Reply

      I’m interested in mentoring this year (did you even have to ask? :))

      Some things I would be interested in (based on some previous ideas):

      • New User Walkthrough. Specifically meter based “you are 10% setup, etc”. Think LinkedIn style.
      • A visual way to surface visual embeds / oEmebeds etc. Instead of needing to magically know that a Spotify or Twitter URL needs to go on its line, support some kind of UI (maybe in the media explorer) that allows you to insert content
      • Anything External API Related. No specific project here. It depends on what is in core at the time (if it’s XML-RPC still or if REST is available yet)
      • General Mentoring
    • Eric 9:35 pm on January 29, 2014 Permalink | Log in to Reply

      I’m game to mentor a mobile project this year. I’ll post some project ideas after I’ve had some time to brainstorm a bit.

    • Aaron Jorbin 5:04 pm on January 31, 2014 Permalink | Log in to Reply

      I would love to mentor once again. Some ideas that I have:

      • Make the PHPUnit tests run faster
      • Increase the number of JavaScript Unit Tests
      • CSS/JS Optimization
      • Automated performance testing
      • Anything dev tools related.
      • Bryan Petty 5:31 pm on February 4, 2014 Permalink | Log in to Reply

        I think the biggest improvement we could make to the unit tests in regards to speed is to find a way to merge multisite tests into the base tests, and only run tests that are actually affected by single/multisite environment changes.

        Right now, we run every single unit test a second time during the multisite run, but in reality, probably less than 25% of them are even affected by multisite. For example, we don’t need to re-run sanitize/escape tests a second time.

        There’s certainly probably lots of places we could avoid @runTestsInSeparateProcesses, especially if we were to deprecate/remove constants.

        Another option might be to find a way to cleanly reset the DB without calling wp_install() again (do one install, dump, and reload from dump directly on the next test with @runTestsInSeparateProcesses).

        Other than that, then you just have optimizations on individual tests, which just becomes a mundane task that no-one wants to do, especially if patches are just ignored because they are so minor and not important.

        • Andrew Nacin 7:43 pm on February 4, 2014 Permalink | Log in to Reply

          Re-running the entire suite under multisite has flagged a lot of issues over the years. I think we’re along way from that point. Multisite just has too many odd side effects on core.

  • Andrew Nacin 5:43 am on May 3, 2013 Permalink
    Tags: gsoc   

    Hello everyone! Applications for Google Summer of Code are due in just 13 hours! (1900 UTC)

    I’ve been reviewing a lot of proposals and ideas. But if you’re waiting until the last minute (like I’m doing with this post), here are some random nuggets:

    • Original ideas are encouraged! We have a great ideas page but we’re not going to complain if you submit something else.
    • You don’t need to be a computer science student! We’ve had liberal arts majors and things turned out just fine.
    • Please demonstrate your abilities by making an attempt to contribute to WordPress core or by writing a plugin. Even though this may happen after applications have closed, it could help.
    • You can submit more than one proposal. This is good because we won’t accept two students for the same proposal. And because you might have two great ideas but aren’t sure which one aligns better with our interests. That’s okay — submit them!

    Finally, here are four more ideas in case nothing else appeals to you. (I’ll make sure these make it onto the ideas page next year.) If you’re still hunting, see if any of these set off bells in your head: (yes, there are WordPress plugins for everything, but innovation and new approaches are good things)

    • Activity. Activity streams, action history, notifications. Imagine what a dashboard could look like for a busy, multi-author site, and how helpful it could be to see what’s truly going on “right now” — as well as what you missed.
    • Meetups. Local WordPress communities organize a lot of meetups. A set of tools for organizers and the local community could be really helpful. (These tools could include integration with meetup.com and wordpress.org profiles.)
    • Dependencies. Allow plugins and themes to be dependent of one another. A theme could require a plugin or example, and WordPress would handle installing that plugin when you install that theme. Similar idea: Compatibility metrics. (Or: Can we be sure it is safe to upgrade everything?)
    • Bug tracker. WordPress can be a great platform for developer tools. Why not a bug tracker? (Read the 2010 ideas page for more.)

    Of course, there’s a lot of other great ideas on the 2013 page. If you haven’t looked recently, I added a few at the start of the application period, including some JavaScript-heavy stuff (editor modes, HTML5 application cache, TinyMCE views). Good luck!

  • Jen 6:53 pm on May 2, 2013 Permalink
    Tags: gsoc   

    GSoC Chat 

    Mentors: GSoC chat in #wordpress-gsoc in about an hour if you’re available.

  • Jen 9:13 pm on April 8, 2013 Permalink
    Tags: gsoc   

    GSoC 2013 Update 

    We have been accepted as a mentoring organization for GSoC 2013. I’m already being bombarded by overenthusiastic students with questions, so we need to get our act in gear re mentor list and project list more or less now. Definitely by tomorrow.

    IF you have worked on an assigned feature team in one of the last few releases, you can be a mentor, yay!
    IF you haven’t worked on an assigned feature team but you’ve had multiple patches accepted in one of the last few releases, you can be a mentor, yay!
    IF you have themes/plugins in the .org repo and the lead devs say your code is good, you can be a mentor, yay!
    IF you don’t meet either of these criteria but think you’re skilled enough and want to contribute, I need to have your code vetted by the lead devs.

    If you are in one of the “yay” categories, please add yourself to the mentor list at https://codex.wordpress.org/GSoC2013 and leave a comment here saying you did so. Then, go to http://www.google-melange.com/gsoc/org/google/gsoc2013/wordpress, scroll down, and follow the process to apply to be a mentor in the gsoc system. Note that it’s a little bit busted right now, so you might not get a confirmation back from me until they fix the existing bug there.

    If you are in the maybe category, you can ping me in irc, comment here, or email ([my username/irc nick]@wordpress.org) me to get on the list of potential mentors that will have code reviewed by the leads.

    Also, project ideas can be added to the wiki page as well IF you fall into the pre-approved to mentor category. Worth running ideas past the leads in irc for a gut-check first. Other ideas can be posted here for review.


  • Jen 6:07 pm on March 19, 2013 Permalink
    Tags: gsoc,   

    GSoC 2013 

    It’s time for us to apply for GSoC 2013 if we want to participate. I can take care of the application, but will need everyone’s help in producing the project ideas and mentor sections.

    “Why didn’t we get accepted last year?”

    We didn’t get accepted last year because our Ideas page wasn’t as good as it had been in past years, and they wanted to make room for some new orgs, so we got cut. Our ideas page wasn’t great because we were planning to embed students in regular cycle feature teams, but we didn’t write up all the potential features this might have included. This year we need to write out all the possible features.


    The more project ideas the better, so things that aren’t targeted for the next cycle but that we might want to do as a plugin to get some traction for inclusion in a later release would be great projects, too. Project ideas can include core features, plugins, themes, unit tests, etc. This includes work on .org site things like the plugin used to power WordCamp sites. The projects must be code, though, not design, documentation, etc. List your project ideas in a comment on this post. Please give it a title, and a short one-paragraph description. If there’s a ticket or relevant thread somewhere, link to it.


    Want to volunteer to be a mentor? You need to be good enough with wp coding that you currently don’t need oversight to generally get it right (though obviously we all can get better with more eyes on code), and have enough time to be available to your student for feedback and code review (at least once per week, though more often is better). The time commitment can be anywhere from one hour to ten hours per week, depending on how far along your student’s project is, and what there is for you to review (an hour or two a week is typical). You get a GSoC tshirt at the end. Want to be a mentor? Leave a comment on this post with a short/one-paragraph little bio about yourself, what kinds of projects you are interested in/qualified to mentor, and links to your website, wordpress.org profile, and twitter account.


    I know you are right smack dab in trying to get this release out, which is why I’ll take care of the application and associated materials. That said, I’m a bit out of the loop with core plans, so coming up with the potential projects list on my own would mean they might not mesh with the actual goals/plans of core team very well. I’ll be looking to you guys to give me a sense of priority/possible plans for the next dev cycle, and to tell me who is qualified to mentor a project from the final list of volunteers. Will ping you offline for this.

    Not sure how to write up a project idea or your short mentor bio? Take a look at the ideas page from 2011 for a guide.

    Note 1: This year BuddyPress will be applying as a standalone organization with WP as the vouching organization. I’ll be helping Paul Gibbs get their application going.

    Note 2: I haven’t announced it yet since it just happened, but we’ve been accepted as a mentoring organization for the Gnome Outreach Program for Women for the summer session. Unlike GSoC, where Google foots the bill, we’ll have to raise the money to cover our interns for the Gnome program, so I’ll announce it along with a fundraising drive. The Gnome program is a little broader than GSoC, and does allow non-code projects, so things like design, ux, documentation, translation, community management, etc would all be possibilities there.

    • trishasalas 6:16 pm on March 19, 2013 Permalink | Log in to Reply

      Jen, I appreciate all the work you (and others) are putting into this. I’m fairly certain I wouldn’t qualify as a mentor (at least this year) as my WordPress coding knowledge is just now starting to solidify. However, I would like to know what I can do to prepare for future involvement (if anything). I would also be interested in learning more about the Gnome Outreach Program.

    • Eric Mann 6:23 pm on March 19, 2013 Permalink | Log in to Reply

      I have a few ideas …

      Idea 1: Dashboard Widget API
      We have a great widget API for sidebar widgets, but the admin dashboard widget API is far less reusable. Certain widgets rely on the same code (i.e. feed widgets) without a clean abstraction layer to prevent changes to one from breaking another. This is one of the biggest reasons #19239 hasn’t gone anywhere yet. Merging the widgets required some hackery and the new widget in that proposed patch isn’t abstracted enough to be reusable anyway.

      The idea would be to create a basic object template for dashboard widgets that can be extended in the same way WP_Widget can be, then to revise existing dashboard widgets to use the new API.

      Idea 2: Post by Email Plugin
      Deprecating the post by email functionality has been on a list of proposals for quite a while, and despite a patch (#22942) that disables the feature (similar to how Links were recently disabled), momentum has stalled since no clear alternative exists.

      The idea would be to create a new plugin that extends post-by-email functionality in a clean manner. Host the plugin in the .org repo. Then update the existing patch on the above ticket for 3.7.

      Idea 3: UUID Abstraction
      One of the most talked-about “vulnerabilities” in WordPress is the ability to slurp down user IDs and login names programatically since user IDs are auto-incrementing integers. This could be prevented by changing the data structure to use UUIDs instead.

      Also, updating post data structures such that new posts populate the GUID field with a true UUID (rather than the current post permalink) would prevent a lot of developer confusion as to what the field is and how it’s used. (Regular post IDs should remain integers since they’re used in the default link structure.)

      Other objects in the database can be rekeyed as UUIDs as well, but my proposal is to start with user IDs and post GUIDs since changes there would solve specific problems that exist today.

    • jltallon 1:21 pm on March 20, 2013 Permalink | Log in to Reply

      Idea N+1: Plugin/Theme dependencies in core

      Work can begin from Scribu’s plugin +improvements ( Debian-style version comparisons: >=, >>, <=, <<, =), there is a proposed patch out there.

      Second step: Theme *code* dependencies: just like parent-child relationships are declared within the style.css (child themes), themes that need certain plugins to work properly (not enhacements, but hard dependencies) can declare so in a comment at the beginning of functions.php
      RATIONALE: just like plugins can declare "Depends" and "Provides" within their meta information in the plugin's header comment, themes can depend on certain functionality from plugins.

      BENEFIT: ability to "mix and match" code and allow for more modular code. Individual, granular updates to functionality via plugins, where all other components benefit from the upgrade without intervention.


      • Plugin needs certain other(s) plugin(s) to be active before this one can be activated (or at the same time, think “bulk activate”) + feedback in the plugin screen (Depends: plugin1, plugin2) with colors.

      (thisi is basically the functionality present in Scribu’s plugin right now)

      • Plugin needs certain other plugin and version (equal, newer, older) to work.
      • Theme needs certain plugin(s) (and particular versions, while at that) to be activated. Clearly show it at the theme selection screen (just like “theme tags”, maybe?)
      • When a dependency is deactivated/removed, all dependent items (plugins, themes) SHALL be deactivated in turn (for a theme, fallback to “default”)

      I’m proposing this for a GSoC project since I guess it would need quite some more work over what we currently have, and It would need a close eye before it can go in core (where it belongs, IMHO)

    • petarpetrovic 9:22 pm on March 20, 2013 Permalink | Log in to Reply


      I have been using WordPress for a long time, but, sadly, I’ve never contributed any code to it. The main reason for that is that WordPress’ codebase is not fully object – oriented. I know that someone will say “don’t fix what isn’t broken”, but I really think that rewriting the codebase would be extremely beneficial for everyone. It would make a much cleaner API for plugin developers and it would be easier to maintain the codebase. I’d like to work on this through my GSoC participation. For the beginning, we would have two API interfaces – the current one which will become deprecated after the rewrite has been done, and a new one which will allow all plugin developers to gradually switch to new API as the time progresses. Then, say, in WordPress 4 the deprecated API would disappear (or we can provide some sort of plugin for the deprecated API) and a new, OOP – way API will be in place. I know, rewriting the whole codebase can break many things, but no one said that the transition won’t hurt.

      • Jen Mylo 4:51 pm on March 21, 2013 Permalink | Log in to Reply

        Rewriting the entire WordPress codebase is completely outside the scope of a GSoC project, which should be discrete, easily tested, reviewed, and launched.

    • Justin Shreve 1:17 pm on March 21, 2013 Permalink | Log in to Reply

      I’m interested in mentoring this year!

      For those of you who don’t know I’m Justin Shreve. I’m a former GSoC student (2009, 2010) and co-mentored Summer 2011(with Aaron as lead mentor) the HTML Emails project. I also work on social projects over @ Automattic.com

      I’d be interested in mentoring any general projects but specifically: API projects (XML-RPC, REST/JSON API in Core, etc), Projects around things like Post Formats, Multi-site improvements, and any social projects (if there happens to be any plugin proposals, etc).

      Website: http://justin.gs/
      .org profile: https://profiles.wordpress.org/jshreve/
      twitter: https://twitter.com/justinshreve/

    • Marko Heijnen 2:41 pm on March 21, 2013 Permalink | Log in to Reply

      I would love to be a mentor on one of the projects. I’m can work on Media (no backbone yet), mobile projects and on the API. Maybe a RESTfull API. But any other related project is fine.
      I’m @markoheijnen on Twitter, WordPress.org, and just about everywhere else. My site is http://www.markoheijnen.com and I speak at WordCamps and WordPress meetups.

      • Jen Mylo 6:03 pm on March 21, 2013 Permalink | Log in to Reply

        Can you write up a couple of specific project ideas with short descriptions, as shown on the codex page from 2011? That would be a big help.

    • Prasath Nadarajah 3:52 am on March 22, 2013 Permalink | Log in to Reply

      I am interested in mentoring this year!

      My name is Prasath Nadarajah and i did GSoC with WordPress back in 2011 working on the new XMLRPC API. I work at Automattic as a code wrangler.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar