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
Standardize pandas distribution lists #27903
Comments
Agreed it'd be nice to simplify the pandas-dev / pydata@googlegroups split across two systems. On the subject of discourse, there's been talk of creating a discourse for NumFOCUS projects (so that not every project has to create their own). I suspect we could have pandas-users & pandas-contributors boards on that. |
@Dr-G do you know if the NumFOCUS discourse is something we can expect in the short-term? Thanks! |
I should have been clearer. By "there's been talk" I meant very early suggestions of "this is a thing we could do". cc @jcrist if you've reached out to anyone at NumFOCUS or discourse about this. |
FWIW, we used to have a NumFOCUS Discourse instance. No one used it, but I think that's because there was no "reason" for people to use it. I imagine that if projects moved their discussion groups there, it would be different. Let us know if this is something you want to pursue for pandas in future. |
I have not yet, I was hoping to collect potential buy-in from a few projects before bothering them. The general idea here is that projects like CPython, Jupyter, etc... have been having success curating conversation on Discourse. Dask is looking at using Discourse for non-user-issue discussion (instead of gitter, which isn't searchable). Instead of having a Discourse-per-pydata-project, we figured it might be nicer for users to have a big Discourse instance shared among common projects (each project getting a sub-channel). We though NumFOCUS would be a potentially good org to host this under.
@Dr-G, would this be something we could restart? Who at NumFOCUS should we talk to about this? |
@jcrist yes, we could definitely restart it. Please reach out to leah@numfocus-dot-org and andy@numfocus-dot-org to discuss. |
As the project and the community grows, I think it'd be good to keep some consistency among the different channels to communicate. Currently we have:
I don't have a preference on the platform (google groups, mailman, discourse if it's free for open source projects,...), but I think it'd make things simpler and better if we had:
And same channels in Gitter. The pandas-maintainers ones should be private for the active maintainers (both the list and the gitter channel).
I think the names would make it clear what's expected to be discussed, and should help keep each of them focused (I'd avoid pandas-dev, since I think for beginners it can be ambiguous if a pandas dev is a person working with pandas or on pandas).
CC: @pandas-dev/pandas-core
The text was updated successfully, but these errors were encountered: