@dhomeier I'd like your direct input on this - could you help assess what an appropriate level of effort is?

@Cadair your input might also be helpful from the management perspective.

@dhomeier I'd like your direct input on this - could you help assess what an appropriate level of effort is?

I think so far we have spent some 150 hours mainly on the regions side, which is now primarily waiting on a finalised matplotlib API. But all the more important to have the hours to adapt the regions PRs to that once finished.
@dstansby may have a better overview how much work is yet to do in matplotlib.widgets.

Scope of the documentation part is probably fairly open.

@keflavich can you remove me from this? I haven't been asked or agreed to be part of a proposal.

The remaining work in matplotlib.widgets is to rebase the PRs linked in the documentation, and then have two Matplotlib developers to review/accept the work. The blocker when I did this work previously was disagreement on the MPL side on how rectangles should be rotated, but this is now resolved: matplotlib/matplotlib#21945 (comment)

The blocker when I did this work previously was disagreement on the MPL side on how rectangles should be rotated, but this is now resolved: matplotlib/matplotlib#21945 (comment)

It was not clear to me from that comment if changing the implementation to "stay a rectangle in display coordinates" was mostly or largely done, or needed substantial coding yet. If the former, the work should hopefully be on a comparable level to what is needed in regions itself.

From memory (deinitely needs checking to verify) matplotlib/matplotlib#21945 contains all of the implementation for keeping the rectangles rectangles in display coordinates.

Because the estimated total of all the proposals is a bit higher than the amount available for allocation, we suggest that you (@keflavich ) provide a budget range - i.e., a "minimum for this project to be viable" and "maximum you could use effectively for this project".

Depending on the level of familiarity with the present matplotlib implementation I suppose the 50 h minimum should probably allow adapting that and the existing regions PRs, without any further documentation.

FWIW, Jdaviz has a plugin to edit region shapes already (caveat: limited shapes support, needs to go through glue).

https://jdaviz.readthedocs.io/en/latest/imviz/plugins.html#subset-tools

Ginga also has shape edit capability (caveat: starts out as Ginga shape object but it has translator for regions).

https://ginga.readthedocs.io/en/latest/manual/plugins_local/drawing.html

https://ginga.readthedocs.io/en/latest/dev_manual/canvas.html#support-for-astropy-regions

Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0).

Congratulations! The community has expressed support for this FR, and the Finance Committee has determined it can be funded. This FR has been approved for $20,000, to be funded from the NASA grant.

@kelle is the Finance Committee member who will be supporting this project. They will update this PR with the amount and then merge it, as well as being in contact with you to set up any necessary agreements and relevant Open Collective financial arrangements. They will also open a new issue where progress on this project can be discussed.