Maintenance status update, call for new maintainers #1344
Labels
meta
Concerns general dask-sql maintainence
Comments
rapids-bot bot
pushed a commit
to rapidsai/docker
that referenced
this issue
Jun 27, 2024
Since `dask-sql` does not have a lead maintainer, we are dropping it from our containers. User who wish to continue using `dask-sql` in the containers can install it manually or use the `EXTRA_CONDA_PACKAGES` environment variable to install it on startup. See: dask-contrib/dask-sql#1344 Authors: - Ray Douglass (https://github.com./raydouglass) Approvers: - Bradley Dice (https://github.com./bdice) URL: #684
This was referenced Aug 29, 2024
|
Hello. Id be interested in trying to spend some time hee |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Dask-SQL users,
Pinning this issue to put in text that this project currently does not have a dedicated maintainer. Though I and some others have been able to occasionally respond to issues and review external contributor PRs, and may continue doing this in the future, this should not be considered a guarantee.
We've unpinned the Dask dependency in the latest release, which should make it easier for users to install the package for use with newer Dask versions, but this doesn't guarantee full compatibility with the latest Dask. Additionally, we plan to simplify the GPU CI test matrix to make it easier for external contributors to submit PRs, but this may mean that some GPU-related functionality may not be fully tested.
Anyone interested in taking a more active role in maintaining this project should feel free to follow up on this issue, where we can work out what permissions and responsibilities would be appropriate.
The text was updated successfully, but these errors were encountered: