Re: apache package naming convention

2015-08-07 Thread Russell Jurney
I think we should actually file JIRAs in all the projects with org.apache namespaces and ask them to adopt our convention. On Friday, August 7, 2015, Sam Shah wrote: > +1. Pig scripts are written by hand, mostly by data scientists with modest > software skills, so asking them to change all their

Re: apache package naming convention

2015-08-07 Thread Sam Shah
+1. Pig scripts are written by hand, mostly by data scientists with modest software skills, so asking them to change all their scripts is both painful and annoying with no real benefit. On Fri, Aug 7, 2015 at 3:55 PM, Russell Jurney wrote: > Leave it datafu. The normal way of doing Java namespac

Re: apache package naming convention

2015-08-07 Thread Russell Jurney
Leave it datafu. The normal way of doing Java namespaces is terrible bloat, and the change would be breaking. On Friday, August 7, 2015, Luciano Resende wrote: > On Fri, Aug 7, 2015 at 3:16 PM, Matthew Hayes < > matthew.terence.ha...@gmail.com > wrote: > > > Hi all, > > > > Roman Shaposhnik sugg

Re: apache package naming convention

2015-08-07 Thread Luciano Resende
On Fri, Aug 7, 2015 at 3:16 PM, Matthew Hayes < matthew.terence.ha...@gmail.com> wrote: > Hi all, > > Roman Shaposhnik suggested I open a discussion on the following topic: > > For Apache DataFu, all of the Java classes are declared in a datafu.* > namespace. This has been the naming convention s

apache package naming convention

2015-08-07 Thread Matthew Hayes
Hi all, Roman Shaposhnik suggested I open a discussion on the following topic: For Apache DataFu, all of the Java classes are declared in a datafu.* namespace. This has been the naming convention since the DataFu project started in 2010. Since DataFu became part of the Apache incubation process