Skip to content

GSoC 2014 Ideas

Jump to bottom Edit New page
Lauren McCarthy edited this page Feb 5, 2014 · 45 revisions

This page to collects ideas for suggested openFrameworks student projects for participation in Google Summer of Code 2014

If you're active in the openFrameworks community: If you have an idea that you would feel comfortable mentoring, feel free to add it. If you have an idea but need to find a suitable mentor, please bring it up on the oF mailing list; others can help you develop the idea and may volunteer to mentor.

If you're a prospective GSoC student: Read through the ideas and see if any interest you. But note that these are ideas, not project proposals; they may need details filled in or expanded to make a good project. Find an area that interests you and start a discussion on the oF mailing list, even if it's just by asking more about the topic. Also, keep in mind that this list is just a starting point - some of the best projects are those that greatly expand on a proposed idea or are blue-sky proposals not mentioned on the ideas list at all.

A good proposal will be clear about the problem to be solved, the history of work in that area, and the specifics of the approach that the GSoC project will take. You can find some of those answers by reading the code and the issue tracker and searching the list archives, but discussing the idea with interested developers is a great way for both the student and mentor to reach an understanding of exactly what is to be accomplished. (Content adapted from git's excellent GSoC 2013 list)

Ideas:

ofxaddons.com

Brief Description: Updates to ofxaddons.com, the directory of extensions and libraries for the OpenFrameworks creative coding toolkit. This would involve discussion, conceptualization, design, and implementation of improved functionality and interface.

Prerequisites: Web development, frontend is built with HTML/CSS/JavaScript, backend is written in Ruby.

openFrameworks project generator

Brief Description: A redesign for the OF Project Generator was recently proposed that simplifies the process, handles more use cases, and is more informative about what the process of preprocessing, compiling, and linking actually involves. This project would involve reviewing and tweaking the proposed design and implementing the functionality. It would be composed of two parts, a back-end app (with command line control) and a GUI app.

Apothecary: library dependency potion handler

Dan Wilcox created an OpenFrameworks library apothecary that mixes formulas and potions to build and update the C/C++ lib dependencies. It could use some updating and extending of functionality.

https://github.com/danomatika/apothecary

Testing framework for openFrameworks

Brief Description: Come up with and implement a good and comprehensive automated testing system for oF. This is an effort which would greatly help OF development (as we could continually check PRs for breakage), but is of sufficient size and complexity to not be done in a week or so.

The challenge lies in both that OF, running on 5+ OSes, is heavily cross-platform (so it's tricky to get good coverage), and that much of the output of OF (sound, images, videos, network communication) is not easily testable with traditional (unit) tests. See issue #1068 for some discussion and some preliminary work with cpptest on the topic.

Expected results:

  • An automated testing script/program (preferable using an established testing framework) which can be run either manually on multiple platforms or during a run of the build server, and is easily extensible.
  • Written tests for a significant/meaningful portion of the OF codebase.

Prerequisites: Knowledge of software testing will certainly be useful. Language will probably be C++, or maybe Python?

Skill level: medium/high?

Proposed by: Christoph Buchner (bilderbuchi)

Mentor: N.N.

OF 1.0 Roadmap

Last summer, a roadmap for working toward OF 1.0 release was created, spanning all areas from core functionality, extensions, to community. It contains many more ideas, big and small, that could be fashioned into a project proposal. https://docs.google.com/document/d/1GjgjQZCHTcOD3cT9OFSl0AZ1nhfYwwvxTl5L4OJE6qA/pub

Mentors:

If you're interested in being a mentor, add your name here. If there is a specific project you'd like to mentor, add the project in the ideas section. Otherwise, list any general areas of projects you'd be interested in mentoring.

  • Christopher Baker @bakercp ofSketch, Typography, Networking, Raspberry Pi, Internationalization, etc.
  • Zach Lieberman
  • Also: of-dev list at large.

#Application questions

  1. Describe your organization.
  2. Why is your organization applying to participate in Google Summer of Code 2014? What do you hope to gain by participating?
  3. Has your organization participated in past Google Summer of Codes? (yes/no)
    • no
  4. 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
  5. If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?
    • no
  6. What Open Source Initiative approved license(s) does your project use?
  7. What is the URL for your Ideas list? This is the most important part of your proposal. Please make sure we can access it and it is complete when you submit this proposal. “Placeholder” or inaccessible ideas pages will be grounds for an automatic rejection for participation in Google Summer of Code 2014.
  8. What is the main development mailing list for your organization?
  9. What is the main IRC channel for your organization?
    • #openframeworks (freenode)
  10. Who will be your organization administrators?
    • Lauren McCarthy
    • Caitlin Morris
    • Christopher Baker
  11. What criteria did you use to select the mentors? Please be as specific as possible.
  12. What is your plan for dealing with disappearing students? Please be as specific as possible.
  13. What is your plan for dealing with disappearing mentors? Please be as specific as possible.
  14. What steps will you take to encourage students to interact with your project's community before, during and after the program?
    • Students will not work on their projects in isolation. Ideally, they will already be a part of the OF community and thus have reason to see the project through to a shareable result. They will also be integrated into the smaller of-dev community via the mailing list, IRC, meetups, etc. They will share regular progress updates with the of-dev mailing list and receive discussion and feedback from the group.
  15. Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
    • Processing Foundation will vouch
  16. 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
  17. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
    • As mentioned above, students will be fully integrated into the of-dev and larger OF community during the period of their projects. It is our hope that this experience will encourage them to continue participating and contributing, whether this is by continuing to develop the same project or working on some other aspect of OF development and outreach. We also play to feature the results of their projects very publicly on the OF blog and social media, building support and recognition for their efforts.
Add a custom footer
Add a custom sidebar
Clone this wiki locally