(Fernando, I would say just go ahead and put your patch up against core for now and we'll work this out. This discussion shouldn't derail you from putting up a reasonable first patch based on the current structure -- i.e. put the model where all the other impl. models are for now)
On May 18, 2011, at 6:34 AM, Ted Dunning wrote: > Plausible. > > On Wed, May 18, 2011 at 3:31 AM, Sean Owen <[email protected]> wrote: > >> It happens that this, and the one thing that lives in taste-webapp, concern >> one part of Mahout. There are many other things that can live in such a >> module, and I don't see why we'd restrict it? For example, think about >> integration points with Lucene from examples. They really aren't "examples" >> but actual code to be used as integration. That's the kind of thing that >> could properly live in the misnamed integration module that we already >> have. Right now, we have taste-web, and it pretty much just contains the things necessary to build Taste as a web service. All of our models are currently in core. Are you proposing, then, to have an integration model and in it would be all the models other than the abstract definitions? And then are you also proposing to extend it to have other integration pieces? >> >> On Wed, May 18, 2011 at 11:21 AM, Ted Dunning <[email protected]> >> wrote: >> >>> But this is really totally focussed on integration of taste, isn't it? >>> What >>> other integration is there? >>
