Summer of Code 2008 Application
From Habari Project
About Your Organization
1. What is your Organization's Name?
2. What is your Organization's Homepage?
3. Describe your organization.
Habari is a state-of-the-art blogging solution, being written specifically for modern web hosting environments, and using modern object-oriented programming techniques. Habari employs the Model-View-Controller design to separate code from presentation, allowing coders and designers to each focus on their respective specialties. It makes use of PHP Data Objects (PDO) for database independence, as well as enhanced protection against SQL injection attacks through use of prepared SQL statements. The Habari core software provides a robust architecture to support additional functionality through third-party plugins.
One of the core philosophies of the Habari project is that "Community is more important than Code." The concept that a great application requires the efforts of designers, documentation writers, testers, and users in addition to coders is fundamental to this project. The Habari community is a friendly, goal-oriented one with a strong and visible commitment to collaboration and support.
4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?
The Habari project is participating in GSoC 2008 for a variety of reasons, both altruistic and selfish. We are firmly committed to open source development, and welcome the opportunity to guide would-be developers with our collective experience in licensing and transparency. We're also extremely eager to engender useful object-oriented design and programming methods in up-and-coming coders.
Selfishly, we hope to accomplish two primary functions. First, we want the Habari community to grow and flourish, so that this year's students can become next year's mentors. Secondly, we hope that our code and documentation benefits from the passion and energy of the students.
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)
Sadly, we did not participate last year.
6. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)
We did not apply last year.
7. What license does your project use?
Apache Software License 2.0
8. URL for your ideas page
9. What is the main development mailing list for your organization?
10. Where is the main IRC channel for your organization?
11. Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)
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)
Christian Mohn (firstname.lastname@example.org)
About Your Mentors
1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
Volunteers self-identified based on their own interest and availability. The Project Management Committee unanimously approved these volunteers based on their technical and social skills.
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)
epithet, chrisjdavis, moeffju, morydd, smerrill
About The Program
1. What is your plan for dealing with disappearing students?
We plan to require bi-weekly status updates from students detailing work done to date as well as a rough timeline for future work. In this way, we can keep a fairly good eye on where their work stands, as well as what loose threads might exist if they disappear permanently.
2. What is your plan for dealing with disappearing mentors?
The mentors who have volunteered are all core members of the Project Management Committee, and have been regular participants with Habari development since its inception. As such, it is highly unlikely that any of them will disappear.
However, we all recognize that emergencies and Real Life(tm) can have an unexpected influence over even the best of plans. To remedy this, we plan to have multiple mentors engaged with each student, both to provide additional "coverage" as well as to cross-pollinate skills and interests between mentors and students.
Finally, we fully expect that all students will participate in our public development mailing list, as would any other interested community contributor. It is our firm belief that the larger Habari community will help provide feedback and guidance to student-led development.
3. What steps will you take to encourage students to interact with your project's community before, during and after the program?
Each student will be welcomed individually by private email. This introduction will include a brief history of the project along with links to salient blog posts that illuminate our motivations. Additionally, this message will include links to the code, wiki, and mailing lists. At the mentor's discretion, telephone numbers may be provided for one-on-one conversation.
The Habari Project Management Committee strongly believes in the value of transparency. There exists only one mailing list for the discussion of development issues, and our students should use this list to ask implementation questions. Based on suggestions from the GSoC documentation, the students will be assigned branches within our Subversion repository, and all their work will be exposed to public review, comment, and patches.
It is our belief that our use of multiple mentors for students, each with unqiue perspectives on Habari's code and community, will help foster a feeling of respect and integration in our students as early as possible. All of the mentors live and breathe Habari's "Community > Code" philosophy, and will be excellent role models on how to navigate the sometimes emotional waters of difficult technical implementations.
4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
We hope to integrate our students into the larger Habari community as early as possible. Based on our experience to date, we are hopeful that the students will find the community welcoming, and see it as a valuable resource for technology (and social!) issues outside of those strictly related to Habari development.
It is our desire that students develop honest friendships with their mentors -- and others within the Habari community -- and will want to remain involved after the successful completion of their project. We hope to be able to build long-term mutually beneficial relationships with our students, such that they can rely on the collective experience and wisdom of our community as they face new challenges in their lives.