We can have more than one hangout to cover multiple time zones/work requirements. Each meeting should forward notes to the mailing list.
On Mon, Mar 3, 2014 at 10:09 AM, Giorgio Zoppi <giorgio.zo...@gmail.com>wrote: > So Friday afterwork_ > > > 2014-03-03 18:56 GMT+01:00 Suneel Marthi <suneel_mar...@yahoo.com>: > > > Grant had setup a Google Hangout for Mahout sometime last year before 0.8 > > release. I had one setup too for 0.9 release. I definitely wouldn't want > > to have a hangout on Saturday or weekend. > > > > > > > > > > > > On Monday, March 3, 2014 12:52 PM, Ted Dunning <ted.dunn...@gmail.com> > > wrote: > > > > Happy to organize a google hangout. That has the advantage of allowing > > more attendees and supporting YouTube archiving. > > > > Sent from my iPhone > > > > > > > On Mar 3, 2014, at 9:34, Giorgio Zoppi <giorgio.zo...@gmail.com> > wrote: > > > > > > Hello All, > > > Dr.Dunning could you set a meeting next Sat morning, so we can chat and > > > discuss by skype improvements and what to do and indentify volunteer > and > > > tasks. > > > Best Regards, > > > Giorgio > > > > > > > > > 2014-03-03 18:30 GMT+01:00 peng <pc...@uowmail.edu.au>: > > > > > >> Me three > > >> > > >> > > >>> On Sun 02 Mar 2014 11:45:33 AM EST, Ted Dunning wrote: > > >>> > > >>> Ravi, > > >>> > > >>> Good points. > > >>> > > >>> On Sun, Mar 2, 2014 at 12:38 AM, Ravi Mummulla < > > ravi.mummu...@gmail.com> > > >>> wrote: > > >>> > > >>> - Natively support Windows (guidance, etc. No documentation exists > > today, > > >>>> for instance) > > >>> There is a bit of demand for that. > > >>> > > >>> - Faster time to first application (from discovery to first > application > > >>> > > >>>> currently takes a non-trivial amount of effort; how can we lower the > > bar > > >>>> and reduce the friction for adoption?) > > >>> There is huge evidence that this is important. > > >>> > > >>> > > >>> - Better documenting use cases with working samples/examples > > >>>> (Documentation > > >>>> on https://mahout.apache.org/users/basics/algorithms.html is spread > > out > > >>>> and > > >>>> there is too much focus on algorithms as opposed to use cases - this > > is > > >>>> an > > >>>> adoption blocker) > > >>> This is also important. > > >>> > > >>> > > >>> - Uniformity of the API set across all algorithms (are we providing > the > > >>>> same experience across all APIs?) > > >>> And many people have been tripped up by this. > > >>> > > >>> > > >>> - Measuring/publishing scalability metrics of various algorithms > (why > > >>>> would > > >>>> we want users to adopt Mahout vs. other frameworks for ML at scale?) > > >>> I don't see this as important as some of your other points, but is > > still > > >>> useful. > > > > > > > > > -- > > > Quiero ser el rayo de sol que cada día te despierta > > > para hacerte respirar y vivir en me. > > > "Favola -Moda". > > > > > > -- > Quiero ser el rayo de sol que cada día te despierta > para hacerte respirar y vivir en me. > "Favola -Moda". >
