-1 for changing the folder structure. I don't think the current setup is confusing for the end user and also agree with Matthias that our project structure does not have to be in sync with Spark. +1 for having README on user-facing folders like script or samples (which might demo JMLC/MLContext/MLPipeline/Python MLContext).
Thanks, Niketan Pansare IBM Almaden Research Center E-mail: npansar At us.ibm.com http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar From: Matthias Boehm/Almaden/IBM@IBMUS To: dev@systemml.incubator.apache.org Date: 02/09/2016 01:07 PM Subject: Re: Project folder structure -1 I don't see a compelling argument for this unnecessary change to a more complex project structure just to follow Spark which is not directly comparable - both in project size and content. For example, our algorithms are at the same time a library of algorithms as well as samples for how to write new algorithms. From my perspective, our major goal should be "simplicity via minimality" not "simplicity via common structure" because the latter would always require us to stay in sync. Regards, Matthias Luciano Resende ---02/09/2016 11:11:24 AM---I would like to propose we follow more closely the project structure Spark is using, where we clearl From: Luciano Resende <luckbr1...@gmail.com> To: dev@systemml.incubator.apache.org Date: 02/09/2016 11:11 AM Subject: Project folder structure I would like to propose we follow more closely the project structure Spark is using, where we clearly define a folder for samples, another for dev utilities, etc instead of getting everything buried inside the /scripts folder where it might be confusing/hard for users to find what they are looking for. Also, I would like to suggest creating a README.md on some of these folders (e.g. samples) that describes what the contents of the folder are. Thoughts ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
