Thanks Ross. That sounds like the best way to approach the challenge of have such a wide range of students and skill sets.
Best Regards, Cameron On Sun, Feb 17, 2013 at 3:18 PM, Ross Laidlaw <[email protected]>wrote: > Hi Cameron, > > I forgot to mention (apologies if you already know this) that GSoC is > open to many types of student including undergraduates, postgraduates, > mature students, full-time and part-time students, etc. Consequently, > it might be difficult to devise a project that presents the same level > of challenge to every GSoC student. The approach Chris took last year > as my mentor was to have many interesting extensions lined up for me > if I finished the original project. I really liked this approach and > I believe it's a good model for other GSoC projects to follow. > > Hope this is useful feedback, > > Ross > > > > On 14 February 2013 20:51, Cameron Goodale <[email protected]> wrote: > > Ross, > > > > Thanks for the feedback and I am glad to hear that your GSoC experience > was > > good enough that you are considering doing it again. Is there anything we > > can do differently to improve this summer? (don't worry you won't hurt > my > > feelings) > > > > Cheers, > > > > > > Cameron > > > > > > On Wed, Feb 13, 2013 at 11:23 PM, Ross Laidlaw <[email protected] > >wrote: > > > >> Hi Chris & Cam, > >> > >> I'm listening in on the OODT and SIS lists and I've been following > >> along with great interest. My GSoC experience last summer was very > >> positive. I found OODT to be highly accessible because of its > >> component-based structure. This allowed me to focus on one area (File > >> Manager) and start working on my project without having to learn > >> everything upfront about each part of OODT. The approach for my > >> project was to break it down into smaller deliverable steps. I liked > >> this idea as it helped me to gain momentum. I found the OODT and SIS > >> communities to be very knowledgable, welcoming and encouraging. All > >> of these aspects gave me a lot of enthusiasm to contribute and to > >> complete GSoC. > >> > >> I've tried to spread the word about GSoC to my classmates and > >> colleagues. Every year there are tons of applicants and there should > >> be lots of healthy competition again this year for places. I'm still > >> a student and I'm very keen to apply this year if the OODT/SIS > >> communities would be happy for me to contribute again via GSoC. > >> > >> Ross > >> > >> > >> > >> On 13 February 2013 22:09, Cameron Goodale <[email protected]> wrote: > >> > Chris, > >> > > >> > I think it would be a good idea to check in with Ross who was our GSoC > >> > student last summer, and ask him for feedback on his experience with > >> OODT. > >> > I hope he is listening to the dev list still, but if not we should > >> > check-in and see what he is doing now. > >> > > >> > My hope is that if Ross gives us feedback (good or bad or both) we can > >> work > >> > to improve this summer for our next GSoC student. My apologies in > >> advance > >> > if you already did this when the GSoC last year was closed out. > >> > > >> > Just a few questions to get the feedback pump primed would be: > >> > > >> > Was the mini-project challenging enough? > >> > Did the OODT Devs provide enough information and support? > >> > Did you encounter anything that was frustrating or unnecessarily > >> difficult? > >> > > >> > Any thoughts? > >> > > >> > > >> > -Cam chee > >> > > >> > > >> > > >> > On Mon, Feb 11, 2013 at 12:24 PM, Mattmann, Chris A (388J) < > >> > [email protected]> wrote: > >> > > >> >> [Sorry for cross posting] > >> >> > >> >> Guys, > >> >> > >> >> FYI please note that you can participate as a mentor from a PMC via > >> Apache > >> >> as they are a GSoC org. ComDev will coordinate our participation but > >> start > >> >> thinking about what projects we may want to do. > >> >> > >> >> Cheers, > >> >> Chris > >> >> > >> >> From: Carol Smith <[email protected]<mailto:[email protected]>> > >> >> Date: Monday, February 11, 2013 11:02 AM > >> >> To: Google Summer of Code Mentors List < > >> >> [email protected]<mailto: > >> >> [email protected]>> > >> >> Subject: [GSoC Mentors] Google Summer of Code 2013 > >> >> > >> >> Hi GSoC mentors and org admins, > >> >> > >> >> We've announced that we're doing Google Summer of Code 2013 [1]. Yay! > >> >> > >> >> If you would like to help spread the word about GSoC, we have > >> >> presentations [2], logos [3], and flyers [4] for you to use. Please > host > >> >> meetups, tell your friends and colleagues about the program, go to > >> >> conferences, talk to people about the program, and just generally do > all > >> >> the awesome word-of-mouth stuff you do every year to promote the > >> program. > >> >> > >> >> The GSoC calendar, FAQ, and events timeline have all been updated > with > >> >> this year's important dates, so please refer to those for the > milestones > >> >> for this year's program. NB: the normal timeline for the program has > >> been > >> >> modified for this year. You'll probably want to examine the dates > >> closely > >> >> to make sure you know when important things are happening. > >> >> > >> >> Please consider translating the presentations and/or flyers into your > >> >> native language and submitting them directly to me to post on the > wiki. > >> >> Localization for our material is integral to reaching the widest > >> possible > >> >> audience around the world. If you decide to translate a flyer, please > >> fill > >> >> out our form to request a thank you gift for your effort. [5] > >> >> > >> >> If you decide to host a meetup, please email me to let me know the > date, > >> >> time, and location so I can put it on the GSoC calendar. Also, > remember > >> to > >> >> take pictures at your meetup and write up a blog post for our blog > using > >> >> our provided template for formatting [6]. If you need promotional > items > >> for > >> >> your attendees, please fill out our form [7] to request some; we're > >> happy > >> >> to send some along. We can provide up to about 25 pens, notebooks, or > >> >> stickers and/or a few t-shirts. Please keep in mind, though, that > >> shipping > >> >> restrictions and timeline vary country-to-country; request items > early > >> to > >> >> make sure they get there on time! If you have questions about hosting > >> >> meetups, please see the section in our FAQ [8]. > >> >> > >> >> Please consider applying to participate as an organization again this > >> year > >> >> or maybe joining as a mentor for your favorite organization if they > are > >> >> selected this year. > >> >> > >> >> We rely on you for your help for the success of this program, so > thank > >> you > >> >> in advance for all the work you do! > >> >> > >> >> [1] - > >> >> > >> > http://google-opensource.blogspot.com/2013/02/flip-bits-not-burgers-google-summer-of.html > >> >> [2] - > >> >> > >> > http://code.google.com/p/google-summer-of-code/wiki/ProgramPresentations > >> >> [3] - http://code.google.com/p/google-summer-of-code/wiki/GsocLogos > >> >> [4] - http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers > >> >> [5] - http://goo.gl/gEHDO > >> >> [6] - http://goo.gl/wbZrt > >> >> [7] - http://goo.gl/0BsR8 > >> >> [8] - http://goo.gl/2NGfp > >> >> > >> >> Cheers, > >> >> Carol > >> >> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> Groups > >> >> "Google Summer of Code Mentors List" group. > >> >> To unsubscribe from this group and stop receiving emails from it, > send > >> an > >> >> email to > >> [email protected] > >> >> <mailto: > [email protected] > >> >. > >> >> To post to this group, send email to > >> >> [email protected]<mailto: > >> >> [email protected]>. > >> >> Visit this group at > >> >> > >> > http://groups.google.com/group/google-summer-of-code-mentors-list?hl=en-US > >> >> . > >> >> For more options, visit https://groups.google.com/groups/opt_out. > >> >> > >> >> > >> >> > >> >
