how about org.apache.bahir? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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 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 6/1/16, 10:41 AM, "Luciano Resende" <luckbr1...@gmail.com> wrote: >Sorry for the misuse of the word "artifacts", I meant to be source, sample >source, and md for docs all under one extension umbrella. > > > >Now, a point Steve brought up on the other thread is related to extensions, >are we going to continue to use the org.apache.spark package or should we >use something different for the extensions we are importing from Apache >Spark ? > >Thoughts ? > > >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/ >> > > >> > >> > > > >-- >Luciano Resende >http://twitter.com/lresende1975 >http://lresende.blogspot.com/