Across the various communications channels (GH issues, oiio-dev mail list, and now the #openimageio channel on the ASWF Slack), there are a lot of messages that request answers, fixes, or enhancements, and I'm trying hard to wean myself off of the temptation to handle them all myself, and instead I want to say the following:
*I could handle this request, but so could other people. I swear I don't have any special knowledge or skills that make me the only one, or even the best one. Individually it might make sense for me to quickly answer/fix/implement this, but I certainly don't have the time to handle all such requests, and even if I did, it would displace other tasks for which I really am the only appropriate person. Furthermore, my doing it would rob somebody else of the chance to grow into a more knowledgeable contributor to OpenImageIO, and that's bad for the project. You all know the adage about giving someone a fish versus teaching them to fish.* *So please, somebody, stretch a little, and try to catch this fish. People on the TSC, people who would like to expand their contributions, people who are first-timers. I'm still here to coach you and answer questions, to review code, and to bounce ideas off of. It will help the project and its users immensely to spread the knowledge and the responsibility around.* But boy, that's a mouthful. It's tedious to write that constantly, and you don't want to read it. So I wanted to find a playful shorthand that we'll all understand, and here it is: 🎣 Mackerel! By the way, it *doesn't* mean the person filing the issue or asking the question should fix it themselves. It means, hey, you other onlooker who has OIIO knowledge, I'm talking to you! Think to yourself, "I know the answer" or "I could figure out how to solve this," and be the hero we need today! -- Larry Gritz l...@imageworks.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
