GSoC Application
Work in progress, to be validated once the application questions for 2016 are known. Content based on the phpMyAdmin GSoC application page.
This is a draft of the application that the sigrok project will send to Google to apply as a mentoring organization. Students probably want to look at our GSoC overview.
Organization description
The sigrok project aims at creating a portable, cross-platform, Free/Libre/Open-Source signal analysis software suite that supports various device types (e.g. logic analyzers, oscilloscopes, and many more).
Organization home page url
Main organization license
GNU GPL v3 or later
Veteran/New
New
If you chose "veteran" in the dropdown above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.
If you chose "new" in the dropdown above, have you applied in the past? If so, for what year(s)?
We haven't applied before.
Why is your organization applying to participate in Google Summer of Code 2016? What do you hope to gain by participating?
TBD
What is the URL for your Ideas list?
What is the main development mailing list for your organization?
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
What is the main IRC channel for your organization?
- sigrok on FreeNode
How many potential mentors do you have for this year's program? What criteria did you use to select them?
We have one potential mentor.
He has been a GSoC participant twice before and wants to make use of GSoC to help sigrok grow.
What is your plan for dealing with disappearing students?
We want to see any applying student hang out with us on #sigrok and engange in discussion before choosing. That way, we hope to select someone who shows the dedication that we wish to see. If, for whatever reason, a student should disappear then we believe he/she has good reasons to do so. We will however still try to reach out and see if we can help.
What is your plan for dealing with disappearing mentors?
The mentor is a long time developer of the project and thus has a high motivation not to disappear. In case this cannot be avoided, several other project developers are prepared to take over.
What steps will you take to encourage students to interact with your project's community before and during the program?
We require students to be active before the program starts. Ideally, they submit a patch solving a bug or implementing a small new feature, as part of their application. That way, they'll become familiar with parts of the code and interact with the community. The current developers review the submitted patches and comment on them, providing constructive feedback.
It is assumed that students stay on IRC during their entire time they're participating in the GSoC. That way, we can check back with the students on a regular basis. We also expect their code changes to be pushed to a public repository (e.g. on github) so we can give feedback and/or check that the work is progressing in the right direction.
What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
TBD
Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
None
Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.
None