-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate Github Discussions #5588
Comments
I think that could be useful and would be in favor of trying it out. The only downside I see is some potential redundancy in purpose between discussions and the skimage Zulip chat. Perhaps Zulip is more suitable to a quick one-off question or initial query, whereas a more extended discussion that we want to be able to reference from other issues/PRs is suited to "discussions"? |
As a follow up, do others have examples of other repositories where the "Discussions" feature is being used effectively? I haven't really spent any time using it. |
In GH Discussions doc you can find examples of repositories using it (ImageMagic for example) |
BTW, I just realized that the |
I'm in favor! 🙂 I think it would be nice to have everything centralized somewhere, actually. |
Thanks. It looks like xarray is an example scientific python project using it |
I imagine @jni would also want to weigh in here. An alternative is to use discussion.scientific-python.org and add a sub-category under contributor discussion. I would have suggested we move our user questions there as well, but we have had good interactions with the community at forum.image.sc. |
I came with this suggestion because we have a lot of |
No objections from my side, @rfezzani, if discussions can be useful in separating out issues / questions. |
OK, let us wait by the end of the week in case anyone has any objection. If no, I will activate Discussion and start issue triage next week 😉 |
@rfezzani no objection on my part; thank you! |
#5603 closes this issue 🎉 |
Thanks for doing this and spending time to migrate existing issues! Do you want to write to the mailing list and make a brief post in the general channel of https://skimage.zulipchat.com to increase awareness for non-maintainers? I think just briefly mentioning that we enabled the feature and what types of things should go which place. My current understanding is that we would use issues for: While Discussions will cover general discussions, planning/roadmap and feature requests. Image.sc will remain the best place for general usage questions. |
That's a good idea 👍
Yes exactly 😉 |
Description
@scikit-image/core, what about enabling the
Discussions
Github feature for the repository?Issues labeled
discussion
,support
orfeature request
may be converted to discussions, and the Github issues becomes more like a true bug tracker.The community calendar issue #5169 may also take place there...
The text was updated successfully, but these errors were encountered: