Andrew Dunstan writes:
> Your suggestion elsewhere of "pick your second favourite app" is likely
> to result in a more scattergun approach. Also, if it had the imprimatur
> of the PostgreSQL community to some extent appraoches to projects might
> be more welcome - "Dear open-source-project-manager, on behalf of the
> PostgrSQL community we would like to offer you assistance in making sure
> your application works with PostgrSQL, the world's most advanced
> open-source database system...."
The only way someone is going to get work done on a sustained basis is if
he's got a personal interest, the so-called "itch". You're not going to
achieve anything, except possibly being ridiculed, if you start sending
out form letters "on behalf of the PostgreSQL community".
If people already support PostgreSQL to some extent, go there and test it
and send in patches with improvements. If people don't support PostgreSQL
yet, get a good sense for what the feeling of the project maintainers
toward database abstraction layers is, then throw out a design plan. But
the key is to show results, not intentions. That is how open-source
development works.
--
Peter Eisentraut peter_e@gmx.net
