search

AcademySoftwareFoundation / openexr

The OpenEXR project provides the specification and reference implementation of the EXR file format, the professional-grade image storage format of the motion picture industry.
http://www.openexr.com/
BSD 3-Clause "New" or "Revised" License
1.6k stars 606 forks source link

nuget documentation #345

Open ghost opened 5 years ago

ghost commented 5 years ago

Requires clear information in Readme for nuget usage with Visual Studio and MSbuild. Also requires continuous integration usage instructions.

ghost commented 5 years ago

Greetings @cary-ilm I developed this nuget because its simple for windows users already familiar with visual studio to explore the opportunities of openexr. For example we use this nuget on the development team of mandelbulber2 for continuous integration, check out this sample in 8K omnistereo: https://doi.org/10.6084/m9.figshare.8796446 . On a different note, I am curious if the ILM steering committee criteria consider any interest in nurturing a collaboration with academia?

meshula commented 5 years ago

On the question of nuget documentation, I'm wondering if you might be able to propose an amendment to the readme?

On the collaboration thought, I'd suggest taking the question to the developer discussion mailing list: openexr-dev@lists.aswf.io

Thanks!

cary-ilm commented 5 years ago

Regarding nuget, any help you could offer would be appreciated. With the exception of @meshula, the project doesn't have a lot of Windows expertise.

Regarding academic collaboration, did you you mean the OpenEXR project steering committee, or ILM itself? Since the project is now a part of the Academy Software Foundation, the steering committee is no longer exclusively ILM.

On Mon, Jul 8, 2019 at 10:51 AM Nick Porcino notifications@github.com wrote:

On the question of nuget documentation, I'm wondering if you might be able to propose an amendment to the readme?

On the collaboration thought, I'd suggest taking the question to the developer discussion mailing list: openexr-dev@lists.aswf.io

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openexr/openexr/issues/345?email_source=notifications&email_token=AFC3DGIKBTGYU3YD2VKTSYLP6N5BNA5CNFSM4FZIPYZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZN3KKI#issuecomment-509326633, or mute the thread https://github.com/notifications/unsubscribe-auth/AFC3DGMRMYHI5BXPPAWOTLLP6N5BNANCNFSM4FZIPYZA .

-- Cary Phillips | R&D Supervisor | ILM | San Francisco

ghost commented 4 years ago

Greetings @meshula and @cary-ilm Sorry for delay, life has been busy! I will make the PR today for documentation updates. Are we OK with screenshots in the repo? What folder do I put screenshots?

Regarding the academic collaboration, if it’s OK I would prefer to participate in the weekly synchronous voice meeting and discuss some opportunities for synergy that I think might benefit us all. Do you allow the public to share voice in the steering committee meetings?

cary-ilm commented 4 years ago

Thank you for this. Two prerequisites now that the project is a part of the ASWF - we’ll need a Contributor’s License Agreement from you, and any incoming files should contain the license identifier indicating you have permission to contribute the code under then BSD-3-Clause license. Check the CONTRIBUTING doc for the details and let us know if you have any questions.

On Sat, Jul 27, 2019 at 5:43 AM coast77777777777 notifications@github.com wrote:

Greetings @meshula https://github.com/meshula and @cary-ilm https://github.com/cary-ilm Sorry for delay, life has been busy! I will make the PR today for documentation updates. Are we OK with screenshots in the repo? What folder do I put screenshots?

Regarding the academic collaboration, if it’s OK I would prefer to participate in the weekly synchronous voice meeting and discuss some opportunities for synergy that I think might benefit us all. Do you allow the public to share voice in the steering committee meetings?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openexr/openexr/issues/345?email_source=notifications&email_token=AFC3DGIB4FFHG7JGUJKX2GTQBQ7HNA5CNFSM4FZIPYZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26KYZQ#issuecomment-515681382, or mute the thread https://github.com/notifications/unsubscribe-auth/AFC3DGJVF2BUJEJCA6BHDS3QBQ7HNANCNFSM4FZIPYZA .

-- Cary Phillips | R&D Supervisor | ILM | San Francisco

ghost commented 4 years ago

Greetings @meshula @cary-ilm https://github.com/openexr/openexr/pull/505 is ready for code review. I hope I'm not being too noisy here 👍 Thanks, Coast

meshula commented 3 years ago

The steps outlined in #505 should be validated, and documented. As the OP's github account has been closed are there any nuget users able to validate the nuget build steps?