You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to propose enabling Discussions for the Jupyter organization on Github.
One of the use cases could be to allow the Software Steering Council a more suitable place to conduct asynchronous discussions than what is possible in regular Github issues (Discussions allow for threading, for example).
It could also be used as a way to direct people to various subprojects (since many of the subprojects have their own github organization, but users would naturally show up at this organization), as well as directing users to the discourse.
cc @jupyter/software-steering-council and @jupyter/executive-council
I want to open this up for (wait for it!) discussion (see what I did there?) to see what others think.
The text was updated successfully, but these errors were encountered:
Should we open a Discussion to discuss that idea ? :) Sorry, my day has been hard than expected, just wanted to write something not serious and stupid.
More seriously, I am reducing the channels I monitor and engage into, so personally I prefer not being in those GitHub Discussions (I also don't engage in other repo Discussions). But don't wait on me if you think it brings value.
But don't wait on me if you think it brings value.
... if you think it brings value compared to the GitHub issues. I always wonder what should be created as a Discussion or as an issue, so I create an issue by default, which has already a lot of bells and whistles to prioritize, filter, search, some of which we don't use yet (like milestones linked to a GitHub project...).
I'd like to propose enabling Discussions for the Jupyter organization on Github.
One of the use cases could be to allow the Software Steering Council a more suitable place to conduct asynchronous discussions than what is possible in regular Github issues (Discussions allow for threading, for example).
It could also be used as a way to direct people to various subprojects (since many of the subprojects have their own github organization, but users would naturally show up at this organization), as well as directing users to the discourse.
cc @jupyter/software-steering-council and @jupyter/executive-council
I want to open this up for (wait for it!) discussion (see what I did there?) to see what others think.
The text was updated successfully, but these errors were encountered: