On Jan 28, 2012, at 10:15 PM, Rj redoc wrote:
> hello! i know c++ and basic python. i want to work for this organisation and
> in the process gain knowledge and experience. could you please help me where
> to start...
The first step is to get to a point where you can easily say:
"I use OIIO to _______, but I wish that it _______."
Until you can fill in the blanks, it's going to be hard to find a way to fit in.
I know that looks a little cryptic and maybe unhelpful, but I think, honestly,
that the place to start is by being a user. If you don't find a way to use
OIIO in some way, not only will you not be very motivated to make good
contributions, but in fact you just won't have the mental context to know what
things need to be improved, why, and how. The best contributions are made by
people who have a vested interest in using those very changes in their own use
of OIIO.
Have you ever written a program that had to read, write, or manipulate image
files? If so, dust it off, rip out the existing image file code, and replace
it with OIIO calls. That will get you up to speed quickly and maybe give you
some ideas for where we could stand to improve -- maybe we don't have good
support for a file format you are fond of, or don't build well on your favorite
platform, or you think the documentation is particularly unclear in some area,
or you identify some missing feature. That how contributions are born.
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
