Thanks Andy - it might also make sense to wait another week or so before
merging this to allow others a chance to respond, especially given the high
likelihood of vacations this time of year

Andrew

On Tue, Jul 29, 2025 at 10:49 AM Andy Grove <andygrov...@gmail.com> wrote:

> Thanks for the feedback so far.
>
> Here is a PR to add a warning that the project is no longer maintained:
> https://github.com/apache/datafusion-ray/pull/88
>
> Once this is merged, I will archive the repo.
>
> On Tue, Jul 29, 2025 at 4:06 AM Xuanwo <xua...@apache.org> wrote:
>
> > > Since it is a subproject of DataFusion, maybe we can just archive the
> > repo
> > > with a note saying it is not undergoing active development anymore and
> > > direct questions to the mailing list / other github locations
> >
> > I completely agree with this approach.
> >
> > > Also, since all the software is Apache licensed, if someone wanted to
> > work
> > > on it for a while there is no reason they couldn't fork the project
> > (either
> > > in datafusion-contrib or elsewhere) and keep working on it.
> >
> > Yeah, one thing to add is the new project can't be called
> `datafusion-ray`
> > again.
> >
> > On Tue, Jul 29, 2025, at 18:00, Andrew Lamb wrote:
> > > Since it is a subproject of DataFusion, maybe we can just archive the
> > repo
> > > with a note saying it is not undergoing active development anymore and
> > > direct questions to the mailing list / other github locations
> > >
> > > Also, since all the software is Apache licensed, if someone wanted to
> > work
> > > on it for a while there is no reason they couldn't fork the project
> > (either
> > > in datafusion-contrib or elsewhere) and keep working on it.
> > >
> > > Andrew
> > >
> > > On Tue, Jul 29, 2025 at 2:12 AM Xuanwo <xua...@apache.org> wrote:
> > >
> > >> Hi,
> > >>
> > >> I agree that we should take steps to actively update the project
> status.
> > >>
> > >> However, this project has already been donated to the ASF, so I don't
> > >> think moving it back is an option.
> > >>
> > >> IMO, the more practical approach is to request archiving the project
> as
> > it
> > >> stands. If at least three people want to work on it in the future,
> they
> > can
> > >> reactivate it when needed.
> > >>
> > >> On Mon, Jul 28, 2025, at 23:57, Andrew Lamb wrote:
> > >> > I agree moving it back to contrib makes sense unless we can find a
> new
> > >> > champion to help drive it forward within the official repositories.
> > >> >
> > >> > On Mon, Jul 28, 2025 at 8:40 AM Andy Grove <andygrov...@gmail.com>
> > >> wrote:
> > >> >
> > >> >> The DataFusion Ray project [1] originated in datafusion-contrib and
> > was
> > >> >> donated to the Apache DataFusion project in September of last year.
> > >> >> There was a period of intense development, primarily driven by a
> > single
> > >> >> contributor, during which the project underwent a significant
> > rewrite.
> > >> >> Unfortunately, the project has now been abandoned. The last commit
> > was
> > >> >> almost four months ago, and the main contributor is now working on
> a
> > new
> > >> >> distributed DataFusion project, which will soon be available in
> > >> >> datafusion-contrib.
> > >> >>
> > >> >> My opinion is that we should move the DataFusion Ray repository
> back
> > to
> > >> >> datafusion-contrib at this time.
> > >> >>
> > >> >> I would like to hear thoughts from the community.
> > >> >>
> > >> >> Thanks,
> > >> >>
> > >> >> Andy.
> > >> >>
> > >> >> [1] https://github.com/apache/datafusion-ray
> > >> >>
> > >>
> > >> --
> > >> Xuanwo
> > >>
> > >> https://xuanwo.io/
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscr...@datafusion.apache.org
> > >> For additional commands, e-mail: dev-h...@datafusion.apache.org
> > >>
> > >>
> >
> > --
> > Xuanwo
> >
> > https://xuanwo.io/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@datafusion.apache.org
> > For additional commands, e-mail: dev-h...@datafusion.apache.org
> >
> >
>

Reply via email to