GSoC 2016 timeline

[Jason Kridner]

https://developers.google.com/open-source/gsoc/timeline?hl=en 

Date	Event
13 October, 2015	Program announced.
8 February, 2016 19:00 UTC	Mentoring organizations can begin submitting applications to Google.
19 February 19:00 UTC	Mentoring organization application deadline.
20 February - 26 February	Google program administrators review organization applications.
29 February 19:00 UTC	List of accepted mentoring organizations published on the Google Summer of Code 2016 site.
29 February - 13 March	Would-be student participants discuss application ideas with mentoring organizations.
14 March 19:00 UTC	Student application period opens.
25 March 19:00 UTC	Student application deadline.
22 April 16:00 UTC	Accepted student proposals announced on the Google Summer of Code 2016 site.
Community Bonding Period	Students get to know mentors, read documentation, get up to speed to begin working on their projects.
23 May	Students begin coding for their Google Summer of Code projects; Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.
Work Period	Mentors give students a helping hand and guidance on their projects.
20 June 19:00 UTC	Mentors and students can begin submitting mid-term evaluations.
27 June 19:00 UTC	Mid-term evaluations deadline; Google begins issuing mid-term student payments provided passing student survey is on file.
Work Period	Mentors give students a helping hand and guidance on their projects.
15 August - 23 August 19:00 UTC	Final week: Students tidy code, write tests, improve documentation and submit their code sample. Students also submit their final mentor evaluation.
23 August - 29 August 19:00 UTC	Mentors submit final student evaluations.
30 August	Final results of Google Summer of Code 2016 announced
Late October	Mentor Summit at Google. Mentors and Organization Administrators from each participating organization are invited to Google for an unconference to collaborate on ideas to make the program better and to make new friends too!

[deepak karki]

I guess we should start adding new ideas to the list :)
Unless that has already started!

[Patryk Mężydlo]

There is no good (opensource) oscilloscope. I think it’s an interesting idea for a project. Unfortunately, a high-speed ADC is necessary. PRU would be great for communication with ADC. Trigger system, strengthening and regulating channels needs professional approach as well. It’s just a loose suggestion.

[Hunyue Yau]

For an O-scope type application, you need more the the ADC. There is a lot of
signal conditioning (scaling, AC/DC coupling, filtering) needed. Even then,
the BW is limited. Sampling at best is around 30-50MHz using the PRU. FWIW, I
have a "high speed" ADC attached to a PRU. This is the easy part.

But keep in mind GSoC is a software targeted program. If you can keep this as
a largely software project....

--
Hunyue Yau
http://www.hy-research.com/

[Jason Kridner]

Yeah, let's not even go down this path. No hardware projects. If you want to contribute software to sigrok, propose that. Using something like the Acme capes would be rather welcome and the org could buy that. Let's not make new hardware design a requirement that will stall the project.

--
You received this message because you are subscribed to the Google Groups "BeagleBoard GSoC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard-gs...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Kridner]

I completely reset the ideas page. I need volunteer mentors to register themselves and those potential mentors to add ideas.

To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard-gsoc+unsubscribe@googlegroups.com.