+1
On Sat, Dec 15, 2012 at 7:37 AM, Thiago Veronezi <thi...@veronezi.org>wrote: > +1 > > I like both names. But if it helps people to identify the application > server I agree on having TomEE as TPL. > > []s, > Thiago. > > > On Fri, Dec 14, 2012 at 3:36 PM, David Blevins <david.blev...@gmail.com> > wrote: > > > > On Dec 14, 2012, at 11:00 AM, David Blevins <david.blev...@gmail.com> > wrote: > > > >> > >> On Dec 14, 2012, at 12:34 AM, Mohammad Nour El-Din < > nour.moham...@gmail.com> wrote: > >> > >>> +1 on the renaming based on the discussion we had before > >>> > >>> But about the purpose/responsibilities of the project won't that > contradict > >>> w/ Apache Geronimo ? > >> > >> No. Apache doesn't have the concept of a project or group of people > owning a space to the exclusion of others. > > > > Coming back to this (got very saddened and distracted by the Connecticut > news...) > > > > We can certainly pause and hammer out a different description. It's > primary purpose is not to restrict or obligate, but in more practical terms > is really to let the board know what we do. It's included at the top of > each board report. > > > > With 100+ projects and growing, we just need to put on a pretend board > member hat and think "what description is going to help me understand the > report I'm about to read." > > > > We can of course go off and innovate in all sorts of directions. If one > of those directions becomes a major focus of the project and starts to > monopolize the bulk of our reports, we just need to course correct (what > we're doing now) and make sure our project description matches what we > produce and users consume. > > > > > > -David > > > -- Karan Singh Malhi twitter.com/KaranSinghMalhi
