Following Steve's second suggestion I created an initial Bahir repository from a Spark snapshot (8301fad) and purged the unwanted code using git filter-branch magic to preserve commit history for files like examples that needed to be moved. Adding build configuration, license file, etc would need to be done in a first commit on top of this.
Regarding Luciano's question about possible folder structure, I prepared 3 alternatives but better suggestions are welcome. OPTION 1 (https://github.com/ckadner/bahir_from_spark_8301fad) has the examples folder and src folder at module root level, i.e.: - streaming-akka - examples/src/main/... - src/main/... - streaming-mqtt - examples/src/main/... - src/main/... - python/.. - ... OPTION 2 (https://github.com/ckadner/bahir_with_folders_core_examples_test) has core, examples, test folder at module root level, i.e.: - streaming-akka: - core - src - examples - src - test - src OPTION 3 (https://github.com/ckadner/bahir_with_single_src_folder) has one src folder at module root, containing examples, main, test sources, i.e.: - streaming-akka - src - examples/java/... - main/scala/... - test/scala/... Any other suggestions or comments ...please comment on issue https://issues.apache.org/jira/browse/BAHIR-1 Thanks! ~ Regards, Christian ~ On Wed, Jun 1, 2016 at 2:21 AM, Steve Loughran <ste...@apache.org> wrote: > (first post, hope the apache@org email gets in) > > two opts spring to mind > > -pure source, making a note of origin repo & commit > -snapshot spark repo, purge most and then move to folders you want > > Now, what kind of code layout do we want, so as to encourage a contrib/ > tree? > > > > On 1 June 2016 at 07:27, Mridul Muralidharan <mri...@gmail.com> wrote: > > > I agree with importing just the source .... > > > > Regards > > Mridul > > > > On Tuesday, May 31, 2016, Mattmann, Chris A (3980) < > > chris.a.mattm...@jpl.nasa.gov> wrote: > > > > > I think source is fine by me for the first import - is there > > > a specific reason to have all the artifacts? > > > > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > Chris Mattmann, Ph.D. > > > Chief Architect > > > Instrument Software and Science Data Systems Section (398) > > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > > Office: 168-519, Mailstop: 168-527 > > > Email: chris.a.mattm...@nasa.gov <javascript:;> > > > WWW: http://sunset.usc.edu/~mattmann/ > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > Director, Information Retrieval and Data Science Group (IRDS) > > > Adjunct Associate Professor, Computer Science Department > > > University of Southern California, Los Angeles, CA 90089 USA > > > WWW: http://irds.usc.edu/ > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 5/31/16, 5:42 PM, "Luciano Resende" <luckbr1...@gmail.com > > > <javascript:;>> wrote: > > > > > > >I was thinking about how to import the initial extensions from spark > and > > > >had some initial thoughts : > > > > > > > >- Import history as much as possible > > > >- Create a folder structure where all artifacts for a given extension > > > would > > > >be in that folder, including source, example, doc, etc > > > > > > > >Thoughts ? > > > > > > > >Any suggestions for the folder structure ? > > > > > > > >-- > > > >Luciano Resende > > > >http://twitter.com/lresende1975 > > > >http://lresende.blogspot.com/ > > > > > >
