Hi Josh,
I think you are absolutely right. If there would be a name change, then
there would first need to be a plan of what needs to be done. It does
not make sense to start with looking volunteers, before it is known what
needs to be done, since the people who would like to help, would also
need to be able to do it.
But I do disagree with the 150-250 hours amount of work. That would be
about 6 weeks full time. I don't think it will happen that easily. I bet
150 hours is already spent on this thread. Of course, if you meant that
you would need to use that time on it, yes, that might be true. Though I
am not sure, even if that would be enough. From marketing perspective,
changing the name is probably one of the biggest tasks around.
Let's say you would have 10 interviews about the name change. You would
use 1 hour for preparing to them and 1 hour on them. That would already
be 20 hours. Then let's say that you are in 2 public events talking
about the topic. Travelling 15 hours per event, talking 1 hour each.
Together that would be already over 50 hours of your time, and I think
that you would need to do something else too.
Rgs,
Jussi
Josh Berkus wrote:
> All,
>
> >From my perspective, this whole discussion ... and the EDB survey, and the
> headcount on this thread, etc., is pretty much entirely moot. 40+ people are
> arguing about what color to paint the bike shed, and not one person has
> picked up a brush.
>
> When someone steps forward with a concrete proposal, some market research (and
> no, unscientific surveys of the existing community is not market research),
> and allocations of volunteer time to do the work necessary for a name change
> (something I'd peg at 150 to 250 hours combined work over the next year),
> this whole discussion is pretty darned pointless.
>
> I'll point out, for example, that despite identifying needs to work on both
> the PostgreSQL "about" pages and the 8.3 press release, it's still the 5-6
> old regulars doing 100% of the actual writing and development. And the old
> regulars do NOT have the spare time to even think about a name change.
>
> So Ron, Andy, others who are hot to change to Postgres: let's see a concrete
> proposal, and one that comes up with new resources to do the new work.
> Otherwise, let's terminate these threads and move on to some actual promoting
> PostgreSQL.
>
>