Kevin Anderson

> if you are required to do a number of contributions Please also keep in mind that open-source software projects are not obligated to facilitate such assignments, and that their...

I am in favor of adding REST2. Having a best-in-class model available and easy to use would be useful in a lot of applications. The "easy to use" part will...

I confess this is the first I've heard of zoneinfo, but it seems like the python community at large is agreed that switching from pytz to zoneinfo is a good...

Taking a closer look at the references now, I'm having trouble understanding the calculations. I think my main source of confusion is that the references use `temp_module_front` and `temp_module_back` as...

> quite a long time ago @kandersolar told me he would generally be up for it if I want to make it a project for myself to bring pvlib up...

Closing, as the above comments show that someone needs to champion a discussion before changes like these can be merged. And if that consensus is reached, I think it would...

@adriesse could you email me a copy? I don't have access to the proceedings. Thanks!

The docs build complains: > /home/docs/checkouts/readthedocs.org/user_builds/pvlib-python/checkouts/2485/docs/sphinx/source/user_guide/extras/nomenclature.rst:158: WARNING: term not in glossary: 'solar_elevation'

I plan to make the release tomorrow, after merging: - #2491 - #2623 I suppose this release will be 0.14.0 given that we're calling the PSM3 removals "breaking changes": https://github.com/pvlib/pvlib-python/blob/9e267ca1b7996ca083c0f96efefbb6bf957cc954/docs/sphinx/source/whatsnew/v0.13.2.rst?plain=1#L7-L11

One more thing to include that I wish I had considered earlier: since this will be v0.14.0 (see above comment), I think we should get #2529 in. As a reminder,...