[Soot-list] Summer of Code application

[Elena Sherman]

Eric,

I can be a backup coordinator and help with the application. I will help
to write the proposal for the project that I co-mentor with you. I have
some inline comments also.

Elena

On Thu, February 21, 2013 8:27 am, Eric Bodden wrote:
> Hello.
>
>
> I am trying to decide if we are having a critical mass of committed
> people to go through with an application to the Google Summer of Code. If
> we decide to go ahead, we will need to fill out an application as outlined
> here:
> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2
> 013/help_page#1._How_does_a_mentoring_organization
>
>
> Describe your organization.
> Why is your organization applying to participate in Google Summer of
> Code 2013? What do you hope to gain by participating?
> Has your organization participated in past Google Summer of Codes?
> (yes/no)
> If you answered “yes” to the question above, please summarize your
> involvement and the successes and challenges of your participation. Please
> also list your pass/fail rate for each year. If your organization has not
> previously participated in Google Summer of Code, have you applied in the
> past? If so, for what year(s)? What Open Source Initiative approved
> license(s) does your project use? What is the URL for your Ideas list?
> **This is the most important part
> of your proposal. Please make sure we can access it and it is complete when
> you submit this proposal. “Placeholder” or inaccessible ideas pages will
> be grounds for an automatic rejection for participation in Google Summer
> of Code 2013.** What is the main development mailing list for your
> organization? What is the main IRC channel for your organization?
> Who will be your backup organization administrator?
> What criteria did you use to select the mentors? Please be as specific
> as possible. What is your plan for dealing with disappearing students?
I will ask people at NASA Ames what they put there in the application.

> Please be as
> specific as possible. What is your plan for dealing with disappearing
> mentors?
This is standard: having mentor and co-mentor for the project.

Please be as specific as possible. What steps will you take to
> encourage students to interact with your project's community before,
> during and after the program?
SOAP workshop!

Are you a new organization who has a Googler
> or other organization to vouch for you? If so, please list their name(s)
> here.
I can ask if people at NASA Ames can vouch for us.

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. What will you do to encourage that your accepted students
> stick with the project after Google Summer of Code concludes?
Publications?

> I could submit the application but I would certainly need help
> preparing it, plus I would need a "backup organization administrator" for
> times during which I am afk. Also we will need a list of serious project
> proposals in the style of
> http://community.kde.org/GSoC/2011/Ideas#Project:_KStars:_Printing_suppor
> t Note that if you propose a project you really _must_ agree to devote
> the time to supervise a student working on this project.
>
> So to everyone: It would be great if you could let me know whether you
> are interested in (co-)mentoring a student and whether you would volunteer
> to help draft an application and/or even be a "backup organization
> administrator". This here is a writeup that can help in making this
> decision: http://en.flossmanuals.net/GSoCMentoring/
>
>
> Cheers,
> Eric
> --
> Eric Bodden, Ph.D., http://sse.ec-spride.de/ http://bodden.de/
> Head of Secure Software Engineering Group at EC SPRIDE
> Tel: +49 6151 16-75422    Fax: +49 6151 16-72051
> Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>