Heads up, core team! We’re getting ready to publish details about the plans for WordCamp this October (which includes a mini team meetup), so if you’re thinking of attending, please read the post at http://make.wordpress.org/updates/2014/06/12/wordcamp-san-francisco-travel-contributor-days/ and take the short survey linked at the end of it so I’ll know how many team members to plan for (don’t worry, this isn’t a commitment or anything, I just need to get some rough numbers for budgeting purposes). Thanks!
Updates from Jen Mylo Toggle Comment Threads | Keyboard Shortcuts
GSoC students announced! http://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)
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.
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!
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 http://make.wordpress.org/community/2014/02/13/gsoc-2014-application/
If you haven’t posted an idea to the codex page http://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.
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 http://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.
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.
There are a few days left to submit proposals to OSCON. It would be great to see the sessions there that are about WordPress actually being presented by people involved in the project, so I’d like to encourage/beg/urge some of you to submit a proposal based on your involvement in the core project and/or the cool stuff that’s come out in the past year. The submission deadline is January 30, and the event itself is in Portland, OR July 20-24, 2014. To apply to speak at OSCON, go to http://www.oscon.com/oscon2014/public/cfp/308
Hi core team! Checking in on the team rep situation — just waiting on core team to pick one for the next three months before getting all the other teams going with theirs (their new ones, I mean; everyone else already chose). It’s been a couple weeks, so would like to get this wrapped up today if possible. I asked Jaquith in -dev just now about the result of the meeting yesterday, and he said: “I believe we were going to let people volunteer themselves or others.nominate, decide, soon.”
If that’s already underway, great, and please let me know later today who you all decided on.
If it’s not really a priority bc core development is taking up all the prioritized brain activity, may I suggest @dh-shredder? When Scribu bowed out last time, we all agreed for Shredder to replace him, but though I talked to him about it at WC San Diego and then posted his name on the team reps page on the make/updates blog, I apparently forgot to post a formal announcement. So if no one is feeling an urgent desire to step up and write weekly updates and relay news back and forth, maybe Shredder would be willing to take the 3-month term, formally this time?
Anyone you guys decide is fine, but please do decide today.
Mentors: GSoC chat in #wordpress-gsoc in about an hour if you’re available.