Re: Should core decide the name?

It likely will not happen without a decision from core, imho. This
would be a good thing for the core to do. What would be helpful is at
the very least, for core to come out in favor of or against, as a
group. Otherwise we're going to go in circles, chasing our tails on
this subject. Nether side of the divide in the community are likely
to change their minds and as such, we won't achieve any sort of
meaningful consensus.

Gavin

On 8/30/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Dawid Kuroczko wrote:
> > On 8/31/07, Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com> wrote:
> > > I'm going to repost the question I posed in my last email as the start
> > > of what I'm hoping might be a thread to end this discussion.
> > >
> > > Are you willing to accept the resolution of the naming question as a
> > > pronouncement from core, who can decide the matter amongst themselves
> > > however they see fit?
> > >
> > > +1 for me.
> >
> > Personally I feel that it goes without saying. They [the core] do most
> > of the work, and they do excellent work, so I feel confident that whatever
> > they choose will be for the best. They should be the ones to decide
> > such important matters -- it is their blood and sweat in the source code. :)
> >
> > I don't want to say that community has no voice in it -- it has, and it
> > is important, just as the community is important for our favourite RDBMS,
> > but I would hate to usurp power over Core. :)
>
> Uh, really the community puts in as much work or more than the core
> people. The idea that core is doing most of the work is something I
> hope is never true. Core are just figureheads when leadership is needed
> in non-technical cases. Of course, this naming thing might be such a
> case (break ties).
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://www.enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>