GSoC And WordPress No Go For 2012

For the first time that I can remember, WordPress has been rejected from the Google Summer Of Code mentor ship program. This was an unexpected move, especially considering how WordPress has been a part of the program for the past few years. As you read through the comments of the post, quite a few people have expressed disappointment. However, if the experimental approach to WordPress development that is currently taking place with 3.4 via the aspect of teams is successful, WordPress could conduct a mini Summer Of Code event with each major release of the software, minus the big paycheck. It would also eliminate the age restriction that is currently part of the Google Summer Of Code. It’s unclear as to why WordPress was rejected but the reason is expected to be given at a meeting within the next week or so.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.

1 Comment

  1. I think “unexpected” is probably the wrong word to use, unless directly quoting Jane.

    1) Maybe GSoC remember the BBXF fiasco.
    Created, never used, then website and software it was built for were deleted.

    2) The new management style.
    It’s truly chaotic. It’s not Agile in any way. More over it stops any form of medium to long term planning. It took less than 30 days for the plan ( to be totally derailed.

    BETA 1 was planned for last Wednesday. The Code Freeze was meant to happen 31 days ago. Somehow it slipped by at least 31 days in under 30 days! Chaos.

    But even to quote Jane herself:

    * Good GSoC mentoring takes time. Time is hard to come by at the best of times, even harder for many during the summer.
    * Many of our previous GSoC mentors have held the position for several years and could use a break from trying to mentor while simultaneously working on features for a regular release.
    * Almost none of our GSoC projects have actually made it into core. A few because they were plugins, but most because once GSoC is over there hasn’t been a concerted effort to follow up on these projects.
    * We often run late on dev cycles.

    To me, “unexpected” is the diametrically opposite word.


Comments are closed.