-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
dask-histogram as part of dask-contrib #154
Comments
+1 from me. I think As a side note, if the goal of |
Also +1 from me |
I'm sure we have enough votes. @douglasdavis , are you ready to make the move, or are there still conversations elsewhere you wish to clear up first? |
Agreed I think the other question is, how we do the transfer? IOW who has permissions on dask-contrib to facilitate this and what does Doug need to do to make the move |
@jrbourbeau , can you make me an admin on dask-contrib so I can do the move? I assume all dask admins should be dask-contrib admins for this kind of thing. |
Agreed would be good to add all admins over there |
Just mentioning here that I had a quick chat with Martin confirming I'm ready for it to be moved to dask-contrib, I passed ownership to him in prep for making the move. |
I've invited John, Martin, Julia, Ben, and Matt to be admins for |
Thanks all! 😄 |
I've been working on dask-histogram for a little while now and it's "complete" w.r.t. the initial goal (make boost-histogram Dask collection compatible). It's something I'm happy to continue developing, maintaining, and releasing. @jrbourbeau and I had a quick chat about it potentially being a good project for dask-contrib and I'd be happy for it to live there if there are no objections.
The text was updated successfully, but these errors were encountered: