RE: Google Summer of Code chat

[Kridner, Jason]

Copying the entire public GSoC mailing list on the meeting minutes, as I don't think anything too controversial/committal was said.  I've only made the tiniest of edits.

 

Also, here is the link and copy of the timeline:

http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

 

January 24:	Program announced.
February 28: 19:00 UTC	Mentoring organizations can begin submitting applications to Google.
March 11: 23:00 UTC	Mentoring organization application deadline.
March 14-17:	Google program administrators review organization applications.
March 18: 19:00 UTC	List of accepted mentoring organizations published on the Google Summer of Code 2011 site.
March 18-27:	Would-be student participants discuss application ideas with mentoring organizations.
March 28: 19:00 UTC	Student application period opens.
April 8: 19:00 UTC	Student application deadline.
Interim Period:	Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
April 22:	All mentors must be signed up and all student proposals matched with a mentor - 07:00 UTC Student ranking/scoring deadline. Please do not add private comments with a nonzero score or mark students as ineligible (unless doing so as part of resolving duplicate accepted students) after this deadline - 17:00 UTC IRC meeting to resolve any outstanding duplicate accepted students - 19:00 UTC #gsoc
April 25: 19:00 UTC	Accepted student proposals announced on the Google Summer of Code 2011 site.
Community Bonding Period:	Students get to know mentors, read documentation, get up to speed to begin working on their projects.
May 23:	Students begin coding for their GSoC projects; Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.
Interim Period:	Mentors give students a helping hand and guidance on their projects.
July 11: 19:00 UTC	Mentors and students can begin submitting mid-term evaluations.
July 15: 19:00 UTC	Mid-term evaluations deadline; Google begins issuing mid-term student payments provided passing student survey is on file.
Interim Period:	Mentors give students a helping hand and guidance on their projects.
August 15:	Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
August 22: 19:00 UTC	Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google.
August 26: 19:00 UTC	Final evaluation deadline Google begins issuing student and mentoring organization payments provided forms and evaluations are on file.
August 29:	Final results of GSoC 2011 announced
August 30:	Students can begin submitting required code samples to Google
October 22 & 23:	Mentor Summit at Google: Representatives from each successfully participating organization are invited to Google to greet, collaborate and code. Our mission for the weekend: make the program even better, have fun and make new friends.

 

 

 

_____________________________________________
From: Kridner, Jason
Sent: Friday, January 28, 2011 11:20 AM
To: Kridner, Jason; Wicks, Cathy; Kooi, Koen; 'Måns Rullgård'; 'Vladmir Pantelic'; Roberts-Hoffman, Katie; 'Jeff Osier-Mixon'; Syed Mohammed, Khasim; Estevez, Leonardo; 'Hunyue Yau'; Hilman, Kevin; 'lir...@pucp.edu.pe'; 'Michael Zucchi'; 'Philip Balister'; 'laine walker-avina'; 'soren'; 'Søren Steen Christensen'; Mark Yoder; 'Robert Nelson'; Walzer, Frank; 'cristina murillo'; Joel Sherrill
Subject: RE: Google Summer of Code chat

 

 

Attendees

• Robert Nelson
• Joel Sherrill
• Koen Kooi
• Cathy Wicks
• Katie Roberts-Hoffman
• Jason Kridner
• Mans Rullgård
• Frank Walzer

 

What went wrong?

• International shipment of hardware

• Goodie shipments
• VAT added to the students

• Want to personalize interactions with the students and have more interaction points

• Can TI pay for student travel?
• Can we communicate to the local offices?

• Invite them into the local office

• Find companies and sponsor a meet-up locally
• Plan meeting early
• Have knowledgeable TIers show up to University talks and GSoC in general

• There is a mailing list that announces meet-ups/talks

• Screen students in terms of ability to commit (no conflicting commitments, such as a thesis)
• Not all projects really impacted upstream and code that touched BeagleBoard users

• Need student to communicate plan to push upstream and get project out, including things like talks/videos/etc. and how to hand-off
• Perhaps pushing upstream is too much to ask?
• Can we communicate the value to the student of getting the code upstream?

• Screen students better for the requisite knowledge

• Even if they have good DSP experience, BeagleBoard requires quite a bit of ARM/Linux/git experience
• Request specific references to a public version control library containing some of their code

 

What went right?

• Mentor to student ratio should be maintained with a single primary mentor (3:1 or 4:1)

• Make sure students clearly understand the mentors areas of expertise

• Weekly IRC meetings with required attendance and weekly report

• The videos were really nice to promote the project were really helpful
• Schedule 2 rounds of lightning talks and get involvement in eTech Days

• Need to provide hardware and software to smooth out this process

• Consider having students present a poster session at shows like LinuxTag

• Schedule meet-ups
• Collect ARM Hello World applications and provide them with a virtual machine

• Include your name in it
• Perform a cross-compile
• Allow them to use QEMU to test it themselves
• Do we want them to capture a video of it?

 

Announcement plans:

• In new announcement, include description of the projects we had last year.

 

Application plans:

• The requested number students will be decided later based on the number and quality of mentors.
• Make sure we say what is cool about working on BeagleBoard.

• Getting hardware is cool.
• CPU is in a lot of Android phones.
• Mention some robotics and space projects on-going.

• Continue to screen one-offs.

 

Money:

• Do we want to buy BeagleBoard.org GSoC banner space with the money?
• Can we make BeagleBoard.org GSoC flyers for FOSDEM?
• We need to make sure we spend the money for the betterment of participants in the BeagleBoard community

 

Other questions

• What are the pieces required to enable students to quickly build robots?

• See http://www.studentrobotics.org

 

Actions:

• Communicates the timing of everything (Jason)
• Find money for travel (Cathy)
• Look for announcements and push TIers going to universities to talk about GSoC (Cathy)

• Jason to help with GSoC slide deck
• TI to announce our visits
• Cathy to watch list closely

• Find software solution for presentations (Jason)
• Provide an Ubuntu VM machine with OE tools setup and a method for recording a presentation (Koen + Jason)
• Schedule additional follow-up discussions bi-weekly (Jason)
• Generate BeagleBoard.org GSoC flyer for FOSDEM (Jason + Cathy)

 

 

-----Original Appointment-----
From: Kridner, Jason
Sent: Tuesday, January 25, 2011 7:33 PM
To: Kridner, Jason; Wicks, Cathy; Kooi, Koen; 'Måns Rullgård'; 'Vladmir Pantelic'; Roberts-Hoffman, Katie; 'Jeff Osier-Mixon'; Syed Mohammed, Khasim; Estevez, Leonardo; 'Hunyue Yau'; Hilman, Kevin; 'lir...@pucp.edu.pe'; 'Michael Zucchi'; 'Philip Balister'; 'laine walker-avina'; 'soren'; 'yo...@rose-hulman.edu'; 'Robert Nelson'; Walzer, Frank; 'cristina murillo'; 'joel.s...@gmail.com'
Cc: 'Søren Steen Christensen'
Subject: Google Summer of Code chat
When: Friday, January 28, 2011 10:00 AM-11:00 AM (GMT-05:00) Eastern Time (US & Canada).
Where: 877-561-6828x47385307#

 

 

Sorry for sending the conference code # so late.

 

Looking to find a viable time.  I know this doesn't really work for Asia-Pacific, so please complain if you really wanted to attend and are in a time zone where this doesn't work.

 

Agenda:

• Discuss lessons learned from 2010
• Discuss plans

• Announcement of intention and request for ideas
• Application

• How many spots do we want?
• Any updates?

• Remaining funds from participating last year

 

 

[Jeff Osier-Mixon]

I am also sorry I missed it - was working into the wee hours and just couldn't cope with 7am PST.  Next time we'll work on being more controversial.  :)