It's been clear for some time that I don't have the expertise, time, or access to hardware to do an adequate job of keeping up with the needs of Windows-based OIIO users. While I appreciate the ad-hoc help I get from the community, I think that this approach is not hacking it and it needs to be a particular person's responsibility to look out for these issues.
So I am sincerely seeking someone to step up to the plate and take on the role of OIIO Windows Lead. Qualifications: * Ongoing access to a computer running Windows, with the usual development tools. * Experience using and developing with MSVS, CMake, Windows shells, Appveyor, and generally some experience building a variety of open source software packages from source on Windows. * User of OIIO on Windows -- the whole scheme works because you yourself are a consumer and beneficiary of the improvements you make. * You DO NOT NEED to already be an expert on OIIO code internals. It's much more important to be somebody who has built OIIO and uses it, and generally is good at figuring things out on Windows. Responsibilities: * Be the ombudsman who keeps OIIO development steered toward making things better for Windows users. * Answer Windows-specific questions on the mail list and triage Windows-specific issues on GitHub. * Overhaul our documentation for building OIIO and its dependencies on Windows. * Own, and fix/rewrite as needed, the Windows CI (Appveyor), build system, dependency management, and any other part of the code base you think could be improved from the point of view of Windows users. * Work towards a future where Windows users can easily install working binaries/libraries of OIIO and its dependencies and only need to build from source if they intend to develop OIIO itself, not merely to use it. (Do we need to store build artifacts somewhere? Nuget/Chocolatey/VCPkg?) * Have admin/commit privileges on the project. As far as time commitment goes, I think that after a good initial investment in the 3rd & 5th bullet items above (better build docs and foolproof downloadable binaries), things will hit a reasonable steady-state pretty quickly. The vast majority of user complaints are from people who simply can't reliably get a working build from scratch, so early strides there will go a long way toward making it more of an occasional task. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
