Re: [PATCHES] WIP Patch - Updateable Cursors

From: "FAST PostgreSQL" <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "John Bartlett" <johnb(at)fast(dot)fujitsu(dot)com(dot)au>, <pgsql-patches(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] WIP Patch - Updateable Cursors
Date: 2007-03-02 23:13:10
Message-ID: 13067.12301172790761.fast.fujitsu.com.au@MHS
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, 2 Mar 2007 01:20, Simon Riggs wrote:
> On Thu, 2007-03-01 at 15:17 +1100, FAST PostgreSQL wrote:

Hi Simon,

> > We are happy to provide that. If and when it comes to the final patch
> > being accepted, we can send a copyright waiver mail which will put our
> > source code contribution under the BSD license.
>
> This approach is not practically workable and is a terrible shame.

I already made a clarification on this subject yesterday.

http://archives.postgresql.org/pgsql-patches/2007-02/msg00579.php

It is for every patch we submit. Not just the final one.

I also sent a contribution statement yesterday regarding one of my patch
which is already pending.

http://archives.postgresql.org/pgsql-patches/2007-02/msg00581.php

> What would happen if everybody said, "Well, since Fujitsu want to act
> like that, we won't grant a BSD licence on our material until they grant
> a BSD licence on theirs." Deadlock.
>
> How do we know that you'll ever give that waiver? What would stop you
> from making contributions right up to the last minute, receiving lots of
> useful feedback, then at the last minute pulling the patch, once you
> think its got no problems in it? If you do this, how will any of us fend
> off *our* corporate lawyers who would like to do the same (probably)? Or
> did you think the various companies on this list don't have any?
>
> I provided my detailed implementation thoughts on the initial proposal.
> Should I ignore posts from Fujitsu in the future because of this issue?
>
> Open source requires trust, not legal brinkmanship. If you're even
> thinking of submitting patches here, then it should already be clear
> that the people on this list are better friends to you than people from
> other companies who provide non-PostgreSQL-based services and products.
> If you don't believe that, it seems better not to post at all.
>
> I'll trust you, and hope that you'll grow to trust others back.

Of course it is. If we didn't trust the community, why would we even want to
contribute the source code in the first place.?

Rgds,
Arul Shaji

This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN 27 003 693 481. It is confidential to the ordinary user of the email address to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you.

If you do not wish to receive commercial email messages from Fujitsu Australia Software Technology Pty Ltd, please email unsubscribe(at)fast(dot)fujitsu(dot)com(dot)au

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-03-02 23:34:33 Re: broken doc
Previous Message Jeff Davis 2007-03-02 23:03:50 Re: Synchronized Scan update

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-03-02 23:38:54 Re: [HACKERS] Deadlock with pg_dump?
Previous Message Bruce Momjian 2007-03-02 22:46:40 Re: [HACKERS] Deadlock with pg_dump?