> Although this is unavoidable, if the projects are closely associated with > SystemML it might be better to have it collocated in the project, as it > might make it simpler for users to discover and consistently use.
Thanks Luciano. I'm starting to think this may be the way we want to go, creating a research directory in the main apache repo. Our original thinking was we wanted to create one centralized repo for all data related ux research. I do love this idea, but our research to date is very specific to SystemML. We are hoping to link research findings to pull requests. Over time, this would provide context for why certain features/changes were made and make it easier for future development. If anyone has thoughts on how to best handle this, I'd love to hear. :) ........................... Jeremy Anderson https://twitter.com/ObjectAdjective http://www.linkedin.com/in/objectadjective On 7 October 2016 at 12:38, Madison Myers <madisonjmy...@gmail.com> wrote: > Also +1 Jeremy! > > On Fri, Oct 7, 2016 at 12:36 PM, Madison Myers <madisonjmy...@gmail.com> > wrote: > > > Although this is unavoidable, if the projects are closely associated with > > SystemML it might be better to have it collocated in the project, as it > > might make it simpler for users to discover and consistently use. > > > > +1 > > > > On Fri, Oct 7, 2016 at 7:37 AM, Luciano Resende <luckbr1...@gmail.com> > > wrote: > > > >> On Thu, Oct 6, 2016 at 10:33 AM, Madison Myers <madisonjmy...@gmail.com > > > >> wrote: > >> > >> > Hi all, > >> > > >> > Thought it may be a good idea to implement some measures on getting > new > >> > users to adopt SystemML. At the moment, I feel there is a big learning > >> > curve and that we could make it easier through clearer tutorials and > >> > examples, a better user experience on the website (continuing the > >> process > >> > of making it better), more articles that explain SystemML at a high > >> level > >> > and how to use it/why it's important. I also think we should get more > >> > questions and answers on Stack Overflow so that overcoming issues is a > >> bit > >> > easier for new users. Longer-term I'd also love to see a course taught > >> > online such as on Coursera as well as in university classrooms so that > >> > people in the field adopt SystemML more early-on. > >> > > >> > > >> +1 > >> > >> > >> > Also Deron and Mike had some interesting suggestions about visibility. > >> They > >> > suggested having projects using SystemML on personal Github accounts > as > >> > well as mentioning SystemML as a skill on LinkedIn. > >> > > >> > > >> Although this is unavoidable, if the projects are closely associated > with > >> SystemML it might be better to have it collocated in the project, as it > >> might make it simpler for users to discover and consistently use. > >> > >> > >> > Would love to know if others agree and/or have suggestions. > >> > > >> > Thanks! > >> > > >> > -- > >> > *Madison J. Myers* > >> > *UC Berkeley, Master of Information & Data Science '17* > >> > > >> > *King's College London, MA Political Science '14* > >> > *New York University, BA Political Science '12* > >> > > >> > - > >> > LinkedIn <http://linkedin.com/in/madisonjmyers> > >> > > >> > >> > >> > >> -- > >> Luciano Resende > >> http://twitter.com/lresende1975 > >> http://lresende.blogspot.com/ > >> > > > > > > > > -- > > *Madison J. Myers* > > *UC Berkeley, Master of Information & Data Science '17* > > > > *King's College London, MA Political Science '14* > > *New York University, BA Political Science '12* > > > > - > > LinkedIn <http://linkedin.com/in/madisonjmyers> > > > > > > > -- > *Madison J. Myers* > *UC Berkeley, Master of Information & Data Science '17* > > *King's College London, MA Political Science '14* > *New York University, BA Political Science '12* > > - > LinkedIn <http://linkedin.com/in/madisonjmyers> >
