Skip to content
François Beaune edited this page Feb 25, 2014 · 27 revisions

You are a student, and you would like to participate to this year's Google Summer of Code by working on appleseed. Here is an outline of how to proceed from here.

1. Get in touch

Join appleseed-dev, the mailing list dedicated to the development of appleseed. This is the central place for all discussions related to the development of appleseed at large. We also occasionally discuss more general rendering topics such as new techniques, other renderers, etc. Everyone is pretty relaxed, but we all act in a civilized, professional manner (and we expect the same from everyone, including you).

We have put two measures in place to prevent spam: you will need to apply for membership (which we will grant unconditionally), and your first post will be moderated. After that you'll be free to post.

2. Introduce yourself

Use your first post on appleseed-dev to introduce yourself. Here are some things we would love to know:

About yourself:

  • What is your first name?
  • Where are you from?
  • What are you studying?
  • Where are your interests in general? In programming?

About open source:

  • What open source projects did you contribute to, if any?
  • Are you following closely the development of one or several open source projects?
  • Have you or are you leading an open source project (of any kind)?
  • Is there code of yours we could peek at on GitHub, SourceForge, etc.?

About rendering:

  • Did you ever use a commercial renderer? An open source renderer?
  • Did you ever contribute to an open source renderer, even if it wasn't by coding?
  • Have you ever wanted to start writing a renderer yourself?

About appleseed:

  • Did you know of appleseed before this year's GSoC? If so, where did you first hear about it?
  • Have you ever used appleseed?

About coding:

  • Which language(s) are you proficient with?
  • How would you rate your proficiency with C++? With the STL?
  • Did you ever have to follow coding guidelines that weren't yours?
  • Did you ever have to work on a large code base that wasn't yours? How did that feel?

3. Tell us about your project

Clone this wiki locally