ci: Send discussions to [email protected] #5201
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
releases-note/ci
yuchanns
approved these changes
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed at https://lists.apache.org/thread/d9nz51qvy59y2vnqcrrr1skgomhcl11f
Hello, everyone
I'm initiating this thread to explore the feasibility of integrating GitHub discussions into [email protected].
There is a growing number of discussions1 regarding whether the ASF should continue to rely on mailing lists. Provided that all our discussions remain public, searchable, and archivable, it might be worthwhile to consider adopting new methods.
Personally, I would like to establish a discourse for OpenDAL, but we currently lack the necessary resources. Therefore, I am considering the use of GitHub discussions as an alternative.
Currently, we are utilizing GitHub discussions. The primary difference is that we do not yet recognize it as our official main channel. By redirecting GitHub discussions to [email protected], we would officially adopt it.
The mailing list will remain available and active; it simply won't be the preferred method within our community. Should this new approach not meet our expectations, we may revert to the previous system. Moreover, integrating GitHub discussions with [email protected] ensures that, even in less favorable outcomes, all discussions are preserved here.
What are your thoughts on this?