GSoC: Mentoring organization application
Bert Wesarg
bert.wesarg at googlemail.com
Tue Mar 4 01:00:24 CET 2008
Thanks Randy,
On Tue, Mar 4, 2008 at 12:39 AM, Randy Kramer <rhkramer at gmail.com> wrote:
> I found the application at http://code.google.com/soc/2008/org_signup.html.
> I've copied it here with my first attempt at filling it in.
>
> Notes:
>
> 1. We can't edit the application after starting it, so I want to try to get it
> right the first time. We can re-submit up to five times if we do have to
> correct something.
>
> 2. Google will treat the person who fills out the application as the
> adminstrator, so if someone else wants to or is willing to be the
> adminstrator, speak up. (I have no great desire to be the administrator, in
> fact, I'm continuing to worry that we may be rushing into this too late for
> this year, but, I'm not giving up yet.) To be the administrator, you must
> have a Google id--I presume that my gmail id will do the job.
>
> 3. The application must be complete by sometime (maybe noon, some timezone) on
> March 12.
>
> The questions and my attempts at answers--some of my answers are pretty lame,
> so feel free to make or suggest changes:
>
> <quote plus first draft answers>
> Please note that you will be considered the administrator/main contact for
> this organization.
>
> Also note that all fields are required unless otherwise indicated.
>
> You have 5 Organization Application(s) left.
>
> About Your Organization ^ back to top
>
> 1. What is your Organization's Name?
>
> NEdit
>
> 2. What is your Organization's Homepage?
>
> http://nedit.org
>
> 3. Describe your organization.
>
> The organization is the informal association of NEdit developers (not a
> formal / legal organization).
>
> 4. Why is your organization applying to participate in GSoC 2008? What do
> you hope to gain by participating?
>
> We hope to take advantage of the GSoC to:
> * get programming done to advance NEdit
> * interest new developers in NEdit
>
> 5. Did your organization participate in previous GSoC years? If so, please
> summarize your involvement and the successes and failures of your student
> projects. (optional)
>
> No.
>
> 6. If your organization has not previously participated in GSoC, have you
> applied in the past? If so, for what year(s)? (optional)
>
> No.
>
> 7. What license does your project use?
>
> The GPL, version 2 or later, with a special exception for linking to Motif or
> Open Motif libraries. From http://www.nedit.org/news.php#20040806:
>
> "
> This program is free software; you can redistribute it and/or modify it under
> the terms of the GNU General Public License as published by the Free Software
> Foundation; either version 2 of the License, or (at your option) any later
> version.
>
> In addition, as a special exception to the GNU GPL, the copyright holders give
> permission to link the code of this program with the Motif and Open Motif
> libraries (or with modified versions of these that use the same license), and
> distribute linked combinations including the two. You must obey the GNU
> General Public License in all respects for all of the code used other than
> linking with Motif/Open Motif. If you modify this file, you may extend this
> exception to your version of the file, but you are not obligated to do so. If
> you do not wish to do so, delete this exception statement from your version.
> "
>
> 8. URL for your ideas page
>
> We don't have one yet. I can volunteer one on wikilearn (at twiki.org), but
> something on nedit.org would be better--I would favor a wiki, but I should
> check and see if the FAQ comments on that in any way.
>
> 9. What is the main development mailing list for your organization?
>
> develop at nedit.org--subscribe at http://www.nedit.org/mailman/listinfo/develop
> or via email to develop-request at nedit.org with the following in the body:
> subscribe [password] [digest|nodigest] [address=your at address.here]
>
> 10. Where is the main IRC channel for your organization?
>
> AFAICT, we don't have one--I Googled [site:nedit.org irc] and found nothing
> promising.
>
> 11. Does your organization have an application template you would like to
> see students use? If so, please provide it now. (optional)
>
> Optional--if anyone has a recommendation here, speak up.
>
> 12. Who will be your backup organization administrator? Please enter their
> Google Account address. We will email them to confirm, your organization will
> not become active until they respond. (optional)
>
> anyone?
>
> About Your Mentors ^ back to top
>
> 1. What criteria did you use to select these individuals as mentors? Please
> be as specific as possible.
>
> Volunteers who participate on the development list and have a record of making
> patches and commits to the code. (I'm anticipating a little.)
>
> 2. Who will your mentors be? Please enter their Google Account address
> separated by commas. If your organization is accepted we will email each
> mentor to invite them to take part. (optional)
>
> Bert Wesarg,
If they just need my email, here it is: bert.wesarg at googlemail.com
>
> About The Program ^ back to top
>
> 1. What is your plan for dealing with disappearing students?
>
> As recommended by the Google FAQ (??), we will ask them for some sort of
> report every two weeks. If we don't hear from them, we will make two
> followup attempts at contacting them. If we can't reach them, but they later
> get in touch again, we will consider the situation on a case-by-case basis.
>
> 2. What is your plan for dealing with disappearing mentors?
>
> So far we have only one volunteer mentor. In any case, if there is a backup,
> the backup would take over. (All email correspondence between the student
> and mentor would include the backup mentor and be archived somewhere for at
> least the duration of the 2008 GSoC.) If both the mentor and the backup
> mentor become unavailable, and no other volunteer is available, the
> administrator or backup administrator would step in and attempt to mentor,
> including by asking questions of the develop mailing list at large.
>
> 3. What steps will you take to encourage students to interact with your
> project's community before, during and after the program?
>
> The first step will be to attempt to accept only students who express an
> interest in NEdit that seems genuine. We will require that he join both the
> develop and discuss mail lists and introduce himself on those mail lists at
> least at the time of his application.
>
> We would like him to communicate with his mentor on the develop mail list,
> although we recognize he may be reluctant to do at first. We won't force
> him, but we know he will be welcomed and hope he feels welcome there.
>
> 4. What will you do to ensure that your accepted students stick with the
> project after GSoC concludes?
>
> The big project I'd like to do for NEdit is to implement "real folding". This
> is probably too big a project for one GSoC project. We would hope to find a
> student who is interested in such a big project even if he can only undertake
> part of the project in the 2008 GSoC, and that his interest in the overall
> folding effort will keep him interested in NEdit.
> <quote plus first draft answers>
>
> Randy Kramer
>
> --
> NEdit Develop mailing list - Develop at nedit.org
> http://www.nedit.org/mailman/listinfo/develop
>
More information about the Develop
mailing list