-1 for removal. 0 for relocation imho, TC resources and module size aren't good arguments for removal/moving. ML tests could be run nightly. ML module contains few integrations (with TensorFlow and other), these optional integrations are wighty and could be moved to extension, but core functionality still can be left untouched if it is highly coupled with core Ignite and moving to extension is hard.
On Wed, Aug 9, 2023 at 3:22 PM Anton Vinogradov <a...@apache.org> wrote: > +1 to relocation > > On Wed, Aug 9, 2023 at 3:09 PM Alex Plehanov <plehanov.a...@gmail.com> > wrote: > > > Pavel, do you know anyone who uses it? > > > > Looks like it isn't used at all (no questions on mail lists, no > > tickets), but we spend developers time to build module with every > > Ignite rebuild, we spend users traffic to download module (ML with > > dependencies takes about 1/4 of our binary release package size) and > > we spend team-city resources to test module. > > > > +1 for removing or moving to extensions. > > > > ср, 9 авг. 2023 г. в 14:19, Pavel Tupitsyn <ptupit...@apache.org>: > > > > > > Does it have any outstanding issues? A stable and useful module should > > not > > > be removed just because it does not evolve. > > > > > > On Wed, Aug 9, 2023 at 1:46 PM Ivan Daschinsky <ivanda...@apache.org> > > wrote: > > > > > > > Igniters, seems that this module is completely abandoned for more > than > > 2 > > > > years. But it is enormous and it seems that nobody wants to take care > > of > > > > it. I suggest just removing it or moving it to extensions (as > option). > > > > WDYT? > > > > > > > -- Best regards, Andrey V. Mashenkov