+1 for renaming it. make it part of the main package. that way we have to commit to it. if we put it off to the side there's more "it's a side project. we don't need to maintain it."
On Fri, Dec 4, 2015 at 10:26 AM, Kessler CTR Mark J < mark.kessler....@usmc.mil> wrote: > Good point, we should keep it the same then. However if we do have to > reorganize it in the future, we can go over options then. > > -Mark > > -----Original Message----- > From: Alex Harui [mailto:aha...@adobe.com] > Sent: Friday, December 04, 2015 10:52 AM > To: dev@flex.apache.org > Subject: Re: [DISCUSS] Adopting AS3Commons > > > I'd either leave it as is: org.as3commons > Or add apache: org.apache.as3commons > Or add apache.flex: org.apache.flex.as3commons > Or hint at Apache Commons: org.apache.commons.as3 > > There is backward compatibility to be considered, so if we rename the > packages folks would have to change their source code to use it, so I'd > probably lean towards leaving it as is. > > -Alex > >
