Difference between revisions of "GSoC2011/OrgApplication"

Latest revision as of 23:26, 11 March 2011

Our organization application for GSoC2011, which has been handed in before the March 11 deadline successfully.

Direct link for the admin and backup admin of the read-only application: http://www.google-melange.com/gsoc/org_app/record/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.

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?

Gnucash has recently picked up a significant momentum to implement radically new features and technologies. Some of them are already being integrated in the current code base, whereas others are still in the concepts stage. We believe that Gnucash can offer the platform for several exciting new projects that explore innovative ways of application development and use case implementation. Hence, our organization is in a phase where students with experimental projects can join easily, and are also warmly welcomed. We of course also expect to directly benefit from their full-time coding efforts, as we have from past participation in the GSoC program. We also expect to benefit from the new ideas and fresh perspectives the students bring. They, in turn, will develop rapport with key members of our team. The awareness and mindshare that we develop with the younger generation in general, and the student and academic community in particular, will surely help find future recruits. If even a small number of students continue their association with our project, that will be the icing on the cake.

Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.

We participated in 2007 but not in any other year. In 2007, 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.

We selected mentors based on the following criteria:

1. All of them are active developers and they have great knowledge of the architecture of the system, existing code base and development environment.
2. They showed good communication skills on our mailing lists and are known to help others to solve their problems and get to know the code base.
3. They have suggested projects that have a realistic chance of being completed in 12 weeks and have a number of early steps of success on the way.
4. They have volunteered to act as a mentor.
5. Some of them also have experience of successful participation in past Google Summer of Code projects.

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:

1. 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, including several voice conversations (phone, skype, or similar).
2. 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.
3. Ask for feedback: As the project progresses, we plan to ask the student for feedback and address any issues so that we can avoid any build-up of frustrations.
4. Establish ground rules: We will establish ground rules regarding frequency of communications, primary/secondary communication channels and mutually agreed project milestones. Each mentor will set up those with their respective student, and the organization admin will keep in close contact with the mentors to encourage and check that these points are indeed being set.

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. Those additional mentors and also the organization admin will be available 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 regarding how they could remain engaged and ask for their feedback on what could be a potential next project.