How to claim or reserve an open scikit-image issue

Contributor & Development Discussion scikit-image
1

Hi,

I’m considering contributing to scikit-image as my first open source contribution and had a question about the usual workflow for claiming an issue.

If I find an issue that I believe I can work on, how should I indicate that I’d like to work on it? Is leaving a comment on the GitHub issue sufficient, or does scikit-image have another convention for claiming or reserving issues to avoid duplicate work?

Thanks!

2

Hi @Readyrel,

Welcome, and thank you for your interest in scikit-image!

We don’t claim or reserve issues, we just do the work and then file the resulting PR. PRs that are discussed on Community Calls have a much higher chance of getting merged.

A good start is our contributor guide, which also includes our AI policy: How to contribute to scikit-image — skimage 0.26.1rc0.dev0 documentation

3

I’m curious to understand how the perception arises that contributors feel that they need to claim an issue, or ask permission to work on something. It’s a pattern that crops up regularly across different projects.

Is it innate, taught in universities, etc, that suggest that this is the normal workflow process for open source software?