Decide on the GitHub Projects

[soupault]

Description:

There are currently 9 GitHub projects associated with this repo. I have just noticed a warning saying that Projects (classic) will be shut down on August 24:

It should be straightforward to migrate the projects to the new format. However, I am not sure whether they have been used recently (except maybe for skimage 2 API) and whether we still need that feature enabled for the repo. I believe GitHub labels are much more convenient to navigate the issues and organize them into categories.

[stefanv]

Projects need to be very actively managed. If someone wants to use them because they want to do the meta-work of curating work, that's all good. But, without such care it quickly degenerates into an unruly garden, in which you can't find anything.

[soupault]

Due to the upcoming deadline, I have taken a liberty to remove the stale projects (with latest update in 2022 or before) and the ones with mere 1-4 issues. There are only 2 projects left, and they are now migrated to the new system - available from https://github.com/scikit-image/scikit-image/projects?query=is%3Aopen .

I will keep this issue open until a conclusive decision is made regarding the use of the functionality.

[lagru]

Thanks for taking the initative @soupault!

Personally I'd love it if I could use a private project to keep track of stalled issues, ones to prioritize and the like (without noise on everyone else's part).

I can also imagine very focused projects working as long as we have a single person ultimately responsible. E.g. I might look into it for EOSS5 related stuff for which me and @mkcor have responsibility.

[lagru]

I'm curious. For a test I added this issue to a personal project on my account.

Did that (and removing it) generate notifications or noise for you?

[soupault]

Did that (and removing it) generate notifications or noise for you?

Nothing. Even when I removed the projects from the this repo, GitHub was silent.

[github-actions[bot]]

Hello scikit-image core devs! There hasn't been any activity on this issue for more than 180 days. I have marked it as "dormant" to make it easy to find.

To our contributors, thank you for your contribution and apologies if this issue fell through the cracks! Hopefully this ping will help bring some fresh attention to the issue. If you need help, you can always reach out on our forum

If you think that this issue is no longer relevant, you may close it, or we may do it at some point (either way, it will be done manually).

[jni]

Let's just close this? If people want to use projects, they should use them, and if not, they can be ignored?

[lagru]

Closing in line with Juan's sentiment. For now, we — as a team — don't have a development workflow based on projects. But if someone wants to integrate them in their workflow, they are welcome to.