WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Tagged: google Toggle Comment Threads | Keyboard Shortcuts

  • Jen Mylo 5:39 pm on October 22, 2012 Permalink
    Tags: , google   

    Hello, strangers!

    Google is now taking applications for Google code-In, the winter holiday contest for high school kids. http://code.google.com/gci

    I’m not interested in being the administrator for it, so if someone else is….
    For the record, all the reasons I thought we shouldn’t participate last year still stand.

     
  • Jen Mylo 11:35 am on November 22, 2010 Permalink
    Tags: , google,   

    Unexpectedly, Google’s Melange site (the app used to maange GSoC and Code-in) has removed all the mentor information from GSoC. Can anyone willing to mentor on a code-in task or two please give me their google ID in the comments? Also, I’ve been hitting repeated server errors trying to get tasks into the system, so it’s taking forever. Hope to have a first round of tasks available for students today (contest opened a couple of hours ago), but in meantime, we can hang out in #wordpress-gsoc to just kids direction if they are ready to start sooner.

     
  • Jen Mylo 5:20 pm on November 5, 2010 Permalink
    Tags: , google, ,   

    We have been accepted as a participating organization for the Google Code-in. This coming week we need to firm up a task list so students can check it out before the contest begins.

     
  • Jen Mylo 1:01 pm on October 10, 2010 Permalink
    Tags: , google, , high school, ,   

    We’ll probably apply to be a participating organization for the Google Code-in coming up next month. It’s a student program a la GSoC, but for pre-university students age 13-18. Instead of one long one-on-one project, Code-in is a “contest” rather a dedicated mentorship. The way it works is that the organizations (like us) make a list of tasks that students could work on during the 6-week contest period, falling into a variety of categories:

    Code: Tasks related to writing or refactoring code
    Documentation: Tasks related to creating/editing documents
    Outreach: Tasks related to community management and outreach/marketing
    Quality Assurance: Tasks related to testing and ensuring code is of high quality
    Research: Tasks related to studying a problem and recommending solutions
    Training: Tasks related to helping others learn more
    Translation: Tasks related to localization
    User Interface: Tasks related to user experience research or user interface design and interaction

    Unlike GSoC, where students proposed projects based on our suggestions, for Code-in students do not suggest projects, but work from our pre-defined task list. Students sign up to work on one task at a time (we can accept for reject the assignment). They can complete up to 15 tasks, and will be awarded $100 for every three completed tasks. Since prizes are based on # of tasks, we will need to make sure that the task list we come up with is even — that is, we need to break things down so that each task should take about the same amount of time/effort.

    Students can ask questions (though they are expected to look for answers themselves first), and can collaborate with community members on their tasks as appropriate. This format makes mentorship a much easier thing to commit to than with GSoC, as the amount of time you mentor is flexible and on an as-needed basis.

    If we are chosen to participate, then we’ll likely use the #wordpress-gsoc channel for the code-in students to seek help/guidance, and could set up a group blog as well if it seems like it would be useful.

    In the comments, feel free to make some preliminary suggestions for tasks that middle/high school students between the ages of 13 and 18 would be able to do. The application for organization participation is in a week or so, and the students get involved later in November.

     
    • Aaron D. Campbell 4:52 pm on October 10, 2010 Permalink | Log in to Reply

      It’s definitely harder to come up with coding projects for this group (especially when we need to keep them all roughly the same size). My first thought was coding standards cleanup. It might be hard to divide that into evenly sized tasks, but it would be nice. Especially if we clean up our coding standards some by then.

      Also, since the contest goes from November (to January?), the code will be going in post PHP 5 change. Maybe they could identify places where PHP 5.2+ would be most beneficial? For example, we use is_email() all over the place, but with PHP 5.2 we could use filter_var($user_email, FILTER_VALIDATE_EMAIL);. That same function has FILTER_SANITIZE_EMAIL that could replace sanitize_email(), FILTER_SANITIZE_URL that could replace esc_url(), etc. All this assumes that server configurations have those functions, so there’d be some research involved first.

      • Denis 7:57 am on October 12, 2010 Permalink | Log in to Reply

        There is a slight issue in using built-in security features, however, according to security junkies. In short it goes something along the lines of: if you rely on them and they’re broken, they’ll remain broken until PHP gets updated; and even then, you can’t count on PHP to be up to date on your end users’ platforms.

        Thus, if we actually get to the point of using filter_var(), we should also do our homework and keep an eye on PHP security issues that might relate to them — in order to work around them using WP code.

    • arena 4:54 pm on October 10, 2010 Permalink | Log in to Reply

      Next will be a Google Senior of Code for 50+ !

    • Gautam 6:12 pm on October 10, 2010 Permalink | Log in to Reply

      Hey, I’ll definitely participate in this! I’ll be 15 on 20 October. I’d like if there are some bbPress-related projects too.. maybe related to the new plugin.. (I’m working on a standalone fork, as the standalone version would no longer be supported).

    • Paul Gibbs 6:55 pm on October 10, 2010 Permalink | Log in to Reply

      I would be interested in working with students on BuddyPress projects. I will give some thoughts as to tasks.

    • Aaron Jorbin 8:11 pm on October 10, 2010 Permalink | Log in to Reply

      Many of the files in wp-admin/includes/ could use some documentation help. I would happily mentor a student that wanted to take on the task of documenting the undocumented (and under-documented) functions and classes in that directory. I think we should divide the functions up into groups and each group could then be a task in order to keep it even. We would just have to figure out how many hours a task is equal to and I could try to divide them up accordingly. Since it’s 3 tasks to a pay check, perhaps we could divide them up so that each task was about 1.5 – 2 hours?

      • Jane Wells 8:43 pm on October 10, 2010 Permalink | Log in to Reply

        As a point of reference: If a task is 1.5 hours, then a 13 year old would be getting $100 for 4.5 hours of work, or over $22/hr. Maybe something that would be 1.5 hours for one of our regulars, but would take longer for a student? I’ll talk to other orgs and see about how much time they are estimating for each task.

        • Aaron Jorbin 8:58 pm on October 10, 2010 Permalink | Log in to Reply

          Perhaps I didn’t think about the fact that it is 13 year olds. I like your idea of talking with some other orgs and estimating based on commonly agreed about figures.

        • Aaron D. Campbell 9:03 pm on October 10, 2010 Permalink | Log in to Reply

          To be fair, it’s going to be 13 – 18, and there’s not going to be any fair way to adjust the pay along that scale. I really like Aaron’s suggestion:

          Base the tasks on what one of our developers (documenters, translators, etc) could do in a given amount of time. Then if it takes them twice as long they make half as much per hour, and if it takes them 10x as long they make 1/10th as much per hour.

          It seems not only fair, but also as close the “real world” as possible (people that are better at what they do are faster and make more per hour…in a perfect world at least).

        • Ryan McCue 11:54 am on October 20, 2010 Permalink | Log in to Reply

          As a note, I’ve been charging $35/hr since around the age of 14.

    • Wojtek Szkutnik 10:06 am on October 12, 2010 Permalink | Log in to Reply

      It’s not exactly true, that students can complete up to 15 tasks. They are paid for the first 15 tasks, that’s all. My high score from GHOP (which was the first edition of Google Code-In) was 29 tasks, so we can probably expect a few students to complete about 20 or more.

      About mentorship – as far as I know, every task has an assigned reviewer, who is obligated to take care of the student and evaluate his work on this particular work.

    • Ryan McCue 11:52 am on October 20, 2010 Permalink | Log in to Reply

      If I have time, I’m in. I don’t agree that the tasks necessarily need to be easier or given a longer time. I’m very confident that I could complete a task in the same time as another developer. (Having programmed for several years)

      • Ryan McCue 11:56 am on October 20, 2010 Permalink | Log in to Reply

        Forgot to mention: one task I’d love to undertake is to actually document api.wordpress.org instead of leaving it with Dion’s little “note”.

        I’d think of more tasks, but even just going through bugs would be fun enough for me. :)

      • Gautam 11:56 am on October 20, 2010 Permalink | Log in to Reply

        Same here.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel