Hi folks, changing package names : +1 changing project name : no opinion about - "Commons Sanselan" or "Commons Image (Sanselan)" is fine for my
Cheers, Siegfried Goeschl Charles Matthew Chen wrote: > +1 To changing package names. It will be an easy update for Sanselan > and the project's users. > > +1 to keeping the name Sanselan. The name is of no particular > significance, but users have known the project by that name for a few > years. > > Charles Matthew Chen > > > > > On Tue, Apr 28, 2009 at 8:43 AM, <luc.maison...@free.fr> wrote: > >> ----- "sebb" <seb...@gmail.com> a écrit : >> >> >>> On 28/04/2009, luc.maison...@free.fr <luc.maison...@free.fr> wrote: >>> >>>> ----- "Phil Steitz" <phil.ste...@gmail.com> a écrit : >>>> >>>> >>>> > We have voted to accept sanselan as a commons component [1]. >>>> > Welcome! >>>> > >>>> >>>> >>>>> We now need to settle the administrative questions raised in [2]: >>>>> >>>> > >>>> > 2. Most commons components have a "functional" name instead of a >>>> >>> "fun" >>> >>>> > >>>> > name. Would Sanselan need to be renamed, e.g. Commons Image, or >>>> >>> would >>> >>>> > it >>>> > be ok to have the sub-project called Sanselan, or Commons >>>> >>> Sanselan? >>> >>>> > >>>> >>>> >>>>> My preference would be to adopt a functional name. We used to >>>>> >>> have >>> >>>> > this >>>> > documented as a policy, but that seems to vanished from the web >>>> >>> pages, >>> >>>> > >>>> > so it is possible that we made a conscious decision that I just >>>> > personally forgot about to eliminate this policy. If others - >>>> >>> most >>> >>>> > importantly, the Sanselan community - feel strongly about not >>>> >>> changing >>> >>>> > >>>> > the name, I am OK with it. It makes it easier for people to >>>> >>> find >>> >>>> > their >>>> > way through our components, however, if their names are >>>> >>> descriptive. >>> >>>> -1 to changing names. Names are part of the social link that build >>>> >>> communities, changing them would appear to me as if we were stealing >>> the project from both its promoters and users. All the work done on >>> having a brand known would be lost. >>> >>> How about >>> >>> Commons Image (Sanselan) >>> >> That would be fine. >> >> Luc >> >> >>> or >>> >>> Commons Sanselan Imaging >>> >>> I'm not keen on "Commons Sanselan". >>> >>> >>>> > >>>> > Personally, I feel the same way about TLPs, but that is a >>>> >>> separate >>> >>>> > topic. >>>> > >>>> > 3. Would any changes be required from the existing packaging of >>>> > Sanselan? For example, packages are named org.apache.sanselan. >>>> >>> Would >>> >>>> > these need to be renamed to org.apache.commons.sanselan (or less >>>> >>> fun >>> >>>> > name as above)? >>>> > >>>> > My preference would be o.a.c.x, where x is the new functional >>>> >>> name. >>> >>>> > Repackaging provides an opportunity to revise the name. >>>> >>>> >>>> +1 to repackaging, this is only technical and makes sense. Given my >>>> >>> preference from previous item, this would mean >>> org.apache.commons.sanselan >>> >>>> Luc >>>> >>>> >>>> > >>>> > I have separately kicked off a vote on private@ (per our custom) >>>> >>> on >>> >>>> > commitership. Once that closes, we will need volunteers to help >>>> >>> with >>> >>>> > >>>> > the svn move and component setup. >>>> > >>>> > Thanks! >>>> > >>>> > Phil >>>> > >>>> > [1] http://markmail.org/message/cwngahpm2aieop6c >>>> > [2] http://markmail.org/message/4oum556w4wqubnvm >>>> > >>>> > >>>> > >>>> >>> --------------------------------------------------------------------- >>> >>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>>> >>>> > For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
