GSoC 2014 Organization Application

In order to apply to the Google Summer of Code as a mentoring organization we need to be able to answer the following questions.

Questionair

Describe your organization.

The STE||AR group (which stands for Systems Technologies, Emergent Parallelism, and Algorithms Research) is a group of students, researchers, and faculty members focusing on developing tools supporting future execution models for tomorrows computer architectures. Many of those ideas are applicable to solving some of today's problems we face when writing parallel applications for modern multi-core machines. For this reason we center our effort around HPX (High Performance ParalleX), a general purpose C++ runtime system for parallel and distributed applications of any scale, which implements many of those ideas.

The goal for HPX is to create a high quality, freely available, open source implementation of the ParalleX model for conventional systems, such as classic Linux based Beowulf clusters or multi-socket highly parallel SMP nodes. At the same time, we want to have a very modular and well designed runtime system architecture which would allow us to port our implementation onto new computer system architectures. We use real world applications to drive the development of the runtime system, coining out required functionalities and converging onto an stable API which will provide a smooth migration path for developers. The API exposed by HPX is modelled after the interfaces defined by the C++11 ISO standard and adheres to the programming guidelines used by the Boost collection of C++ libraries.

HPX has an active development team that has increased non-stop since 2007 (ref: http://www.ohloh.net/p/stellar-hpx) thanks to a modular design that enables features to be added easily.

Why is your organization applying to participate in Google Summer of Code 2014? What do you hope to gain by participating?

From previous experiences with the Google Summer of Code program (we have several mentors and students participating in earlier years with the Boost organization), we've found that this is an effective way to get students involved in the project, by coding on a specific task with a finite timeline.

We hope it to be beneficial for the project, as we expect it to give a huge boost to the project. Additionally it will be beneficial for the students, who will get the chance to write code for an open source project (and get paid for it). We intend to involve students actively, encouraging them to stay after GSoC.

Has your organization participated in past Google Summer of Codes? (yes/no)

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.

n/a

If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?

Yes, we applied in 2013 but didn't get accepted.

Does your organization have an application template you would like to see students use? If so, please provide it now.

Please see https://github.com/STEllAR-GROUP/hpx/wiki/GSoC-Submission-Template.

What Open Source Initiative approved license(s) does your project use?

Boost Software License (BSL)

What is the URL for your Ideas list?

Please see https://github.com/STEllAR-GROUP/hpx/wiki/GSoC-2014-Project-Ideas

What is the main development mailing list for your organization?

mailto:[email protected]

What is the main IRC channel for your organization?

#ste||ar at freenode.org

Who will be your backup organization administrator?

Thomas Heller (username: sithhell)

What criteria did you use to select the mentors? Please be as specific as possible.

Previous GSoC experience or new hackers mentoring is an important factor. Otherwise, the mentors are selected according to their involvement in the community and technical skills. We will assign two mentors to each student. This ensures the student to always have someone to guide him even when a mentor is on holidays.

What is your plan for dealing with disappearing students? Please be as specific as possible.

If a scheduled meeting is missed, we will begin daily attempts to reach them through multiple forms of communication. We will require a physical address and phone number, and we will confirm the phone number at the start of the program. If we cannot get in touch for 1 week without any advance notice from the student, they will be sent a final warning. If we hear nothing by the following day, they will be failed. Students will be informed of this policy when the program starts and will agree to follow it.

What is your plan for dealing with disappearing mentors? Please be as specific as possible.

We have available backup mentors so that students will never be without mentorship, even if the original mentor disappears. We will pursue the same communication methods as with students, and failures will be dealt with by blocking them from any future mentoring.

What steps will you take to encourage students to interact with your project's community before, during and after the program?

We will strongly encourage applicants to interact with the community using our standard communication methods (mailing lists and IRC) before and during the application and evaluation periods. In fact, this is part of our custom application template. If a student does not learn to do it during application and evaluation period, we can't expect that they will learn to do so during the next few months. That will count against them in the ranking of their application. Since communication will be one of the requirements for a successful application, we expect that problems during and after the program will be much rarer.

We will treat students in the same way we treat other new members of our community, a significant portion of whom are college students just like the applicants. By encouraging students to communicate directly with the community instead of privately with their mentors, we will infuse them with the process of open-source development.

In the past, we've discovered that a major key to sticky contributors is close personal ties with the community. Requiring students to become full members of the development community instead of segregating them with their mentors as conduits to the community will naturally result in a higher stickiness.

Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.

Boost is going to vouch for us. They are a succesful project being part of GSoC since the beginning.

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.

no

What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?

By encouraging ongoing community engagement during the student-mentor period we hope to knit the student into the project over the summer, to avoid the situation of having the student-mentor interaction happening in private and the code branch languishing without buy-in from the greater developer community.