Some tips for those of you trying to make your GSoC qualifying patch. (And most of this advice will apply to your real projects as well.)
* You are pre-qualified if you successfully submitted code to OIIO in the past (e.g., if you applied to be in GSoC for us last year, even if not accepted). Also, in case we actually need to say it, participants from previous years are strongly encouraged to apply again, if you are still a full-time student. * Please adhere to the style guide: http://sites.google.com/site/openimageio/coding-style-guide Also, look at the surrounding code and try to match its tabbing, spacing and brace conventions, etc. * We only want to see submissions as GitHub pull requests. (Figuring out enough git and GitHub to do this is part of the "test.") Don't send us raw code or tar files, please. * An obvious one- or two-line fix can just be accepted without fear, but anything that could possibly contain any real IP content (let's say, over 10 lines of new code) will not be merged until I receive a signed CLA. So you may as well send it around the same time as your patch, or I'll just have to sit on your merge and delay its inclusion in the source tree. * Please try to keep all communication on the oiio-dev mail list. It's ok to mail me for "private" reasons (like sending your signed CLA, which should obviously not be sent to a public mail list). You will be required to fully participate on the public list for your GSoC, so you may as well get used to doing so and demonstrate that you can during the application process. * Please try to keep reviews short. If you are implementing multiple "features" that could be merged independently, then please send separate pull requests. As you become a more senior developer, it's fine to batch up a bunch of related, even though technically independent, changes. But the first few reviews should be as short and simple as possible. Make it easy for us to review, and easy for you to fix -- if we have requested changes or notice some deviation from the style guide, it's going to be less painful if you only have a little code to edit and resubmit. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
