Difference between revisions of "GSoC2011/OrgApplication"
(→What steps will you take to encourage students to interact with your project's community before, during and after the program?) |
(→What is your plan for dealing with disappearing students?) |
||
| Line 86: | Line 86: | ||
''### TBD ###'' | ''### TBD ###'' | ||
=== What is your plan for dealing with disappearing students? === | === What is your plan for dealing with disappearing students? === | ||
| − | + | We believe that prevention is better than cure! We plan to follow a 4-point approach to prevent them from disappearing: | |
| + | #Rapport: In our experience, student-mentor rapport is key to such remote collaboration efforts. So, mentors will make an effort to build early rapport with the students. | ||
| + | #Close coordination in the early stages of the project: Once the student-mentor team develops a rhythm, we expect things to run more smoothly. However, until that happens, our mentors will maintain closer coordination. | ||
| + | #Ask for feedback: As the project progresses, we plan to ask for feedback and address any issues so that we can avoid any build-up of frustrations. | ||
| + | #Establish ground rules: We will establish ground rules regarding frequency of communications, primary/secondary communication channels and mutually agreed project milestones. | ||
| + | |||
=== What is your plan for dealing with disappearing mentors? === | === What is your plan for dealing with disappearing mentors? === | ||
All mentors are committed developers of the project and they have volunteered to do this. So we don’t expect them to disappear. However, it is possible that they run into personal emergencies that may prevent them from delivering on their mentoring obligations. We received responses from more than the four mentors finally listed. We have requested others to be on stand-by in case they have to step-in in such a contingency. | All mentors are committed developers of the project and they have volunteered to do this. So we don’t expect them to disappear. However, it is possible that they run into personal emergencies that may prevent them from delivering on their mentoring obligations. We received responses from more than the four mentors finally listed. We have requested others to be on stand-by in case they have to step-in in such a contingency. | ||
Revision as of 03:06, 10 March 2011
Our organization application for GSoC2011.
Direct link for the admin and backup admin: http://www.google-melange.com/gsoc/org_app/take/gsoc_program/google/gsoc2011/orgapp?id=6292202
There is a bunch of homework that our organization must complete before we have a chance to be accepted: http://www.booki.cc/gsoc-mentoring/_v/1.0/
In particular, we need come up with a good "ideas" page and also have good answers to the following questions.
Note: The text formatting in our answers seems to get messed up completely, so don't bother with the line breaks here. It will be just plain text with arbitrary line breaks.
Contents
- 1 Describe your organization.
- 2 Why is your organization applying to participate in Google Summer of Code 2011? What do you hope to gain by participating?
- 3 Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.
- 4 If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
- 5 What license(s) does your project use?
- 6 What is the URL for your Ideas page?
- 7 What is the main development mailing list for your organization?
- 8 What is the main IRC channel for your organization?
- 9 Does your organization have an application template you would like to see students use? If so, please provide it now.
- 10 Who will be your backup organization administrator?
- 11 What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible.
- 12 What is your plan for dealing with disappearing students?
- 13 What is your plan for dealing with disappearing mentors?
- 14 What steps will you take to encourage students to interact with your project's community before, during and after the program?
Describe your organization.
GnuCash is personal and small-business financial-accounting software, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows.
Designed to be easy to use, yet powerful and flexible, GnuCash allows you to track bank accounts, stocks, income and expenses. As quick and intuitive to use as a checkbook register, it is based on professional accounting principles to ensure balanced books and accurate reports.
Why is your organization applying to participate in Google Summer of Code 2011? What do you hope to gain by participating?
### TBD ###
Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.
In 2007, we participated and four students started to work with our project. However, the communication between the mentors and students didn't start too well, so some of the students disappeared relatively quickly. Two of the students got involved very well and they implemented interesting and useful new features of gnucash. In that case, the frequent reporting from the student to the mentor and a quick feedback from the mentor ensured a good progress of the report. This time, we will make sure all of the mentors allocate enough time on the mentoring task, especially in the beginning, so that the communication channels are set up on a good level.
If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
2007: 2/4
What license(s) does your project use?
GPLv2
What is the URL for your Ideas page?
http://wiki.gnucash.org/wiki/GSoC2011
What is the main development mailing list for your organization?
The main development mailing list is "gnucash-devel". The archive and subscription information of this list and of the other project lists is shown on http://wiki.gnucash.org/wiki/Mailing_Lists .
What is the main IRC channel for your organization?
- gnucash on irc.gimp.org
Does your organization have an application template you would like to see students use? If so, please provide it now.
Basic Information
Student name: Location (Home town, state, country):
Contact Information
Email: Instant messaging contact details (Skype or similar): Phone number (our mentors will ask for a few phone conversations, especially in the beginning):
Background/Programming Information
What programming experience do you have so far (languages, operating systems, compilers)? Have you worked on programming project(s) before, and which one(s)? What project in GnuCash would you like to work on? How do you propose to solve the problem(s) posed in the project you'd like to work on? Have you ever built an open source package from source? Have you ever built GnuCash from source?
Who will be your backup organization administrator?
Geert Janssens
What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible.
### TBD ###
What is your plan for dealing with disappearing students?
We believe that prevention is better than cure! We plan to follow a 4-point approach to prevent them from disappearing:
- Rapport: In our experience, student-mentor rapport is key to such remote collaboration efforts. So, mentors will make an effort to build early rapport with the students.
- Close coordination in the early stages of the project: Once the student-mentor team develops a rhythm, we expect things to run more smoothly. However, until that happens, our mentors will maintain closer coordination.
- Ask for feedback: As the project progresses, we plan to ask for feedback and address any issues so that we can avoid any build-up of frustrations.
- Establish ground rules: We will establish ground rules regarding frequency of communications, primary/secondary communication channels and mutually agreed project milestones.
What is your plan for dealing with disappearing mentors?
All mentors are committed developers of the project and they have volunteered to do this. So we don’t expect them to disappear. However, it is possible that they run into personal emergencies that may prevent them from delivering on their mentoring obligations. We received responses from more than the four mentors finally listed. We have requested others to be on stand-by in case they have to step-in in such a contingency.
What steps will you take to encourage students to interact with your project's community before, during and after the program?
We will require our students to get familiar with the community, through our mailing list and IRC, before the program starts. During the program, we will ask the students to announce directly to the community major milestones reached. Towards the end of the project, based on an assessment of their aptitude and capability, mentors will have a conversation with them and ask for their feedback on what could be a potential next project.
