Open Academy (
www.facebook.com/OpenAcademyProgram) is a software engineering course offered collaboratively by universities, open source project maintainers, and Facebook. Students are mentored by experienced open source software developers to contribute to an open source project as the principal part of the learning experience. This course is offered under the supervision of a local university faculty member and students will receive academic credit toward their CS degree. Facebook connects all the different constituents and notably brings all the participants together for a 3 day code sprint in Menlo Park, CA (January 30 - February 1, 2015).
Mentors should expect 2 to 3 hours weekly to interact with students. Typically half of the time/effort is spent running a once-weekly, 30 minute all team Agile meeting to celebrate accomplishments, tackle challenges and build a sense of team. The other time goes to reviewing their code & materials and providing guidance over email/IRC/etc. The one other requirement is that a mentor must represent the project at the 3 day code sprint in California. Facebook pays for transportation, hotel and food, so its a free trip to California. This form is intended to explain how to be a good mentor. Have a read through it and, if you are up for being one and have been invited to do so, then by completing this form, you are committing yourself to these obligations until the end of the program term.
To participate:
1. Complete & submit this form by December 1st, 2014.
***Please note that your project description that you provide here, will be viewed by the participating students. The students will largely use your descriptions and commentary provided in this form to create their project preferences .***
2. After you submit the form the student/project matching process will happen in early January. After that takes place, if you project has been matched, you will be introduced to your students by email.
3. While waiting to be matched, please prepare "Getting Started Information" for students and be thinking about appropriately sized project ideas for students who will have between 8-20 weeks to work on the project.
***For the "Getting Started" piece, most mentors take the following email template, modify and it and use it:
(
https://docs.google.com/document/d/1OZTyj48d53vmzFweokPir7s4sLAbFMqG581OAuEY_UE/edit?usp=sharing)
Other best practices to keep in mind:
- Be responsive to student questions via. the project's discussion list.
- Hold weekly meetings with students via. Google Hangout or the medium of your choice.
- Participate in a 3 day code sprint (January 30th - February 1st in Menlo Park, California)
- Provide a midterm progress report for each student. This is typically a few sentences about what the student has done well and what can be improved. It is to be shared with the local faculty person for that student, but mentors may choose to also share it with the students themselves (up to you).
- Provide a final performance feedback report and grade recommendation to each student's professor. Same as above. Note that you aren't on the hook for grades - ultimately the local faculty member makes that decision.
Projects must be open source.